@@ -4,64 +4,66 @@ A breakdown of the project into individual work packages and the corresponding e
==== Effort
==== Draft the new Workpackage Structure
{set:WP1:1}
{set:WP11:1}
{set:WP12:1}
. WP Standard Alignment:
.. get the MVP from OpenXOntology and the current State of the domain model from OSC 2.0, OSI
.. Check compatibility ISO34503 (PAS 1883)
{set:WP2:1}
{set:WP21:1}
{set:WP22:1}
. WP Terminology
.. OpenLABEL Specific terminology based on the MVP of OpenXOntology
.. Create a Glossary for the specification and the user guide
.. start aligning terms with the other projects for common understanding
.. goal handing over to OpenXOntology during or at the end of the project
. WP Object Labels
.. Geometries, Position Volume, Temporal description
.. Documentation for User Guide
.. Documentation for Specification
.. Implementation in the Format
{set:WP3:1}
{set:WP31:1}
{set:WP32:1}
{set:WP321:1}
{set:WP322:1}
{set:WP323:1}
{set:WP324:1}
. WP Scene/Action/Events/Triggers Labels
.. Documentation for User Guide
.. Documentation for Specification
.. Implementation in the Format
{set:WP4:1}
{set:WP5:1}
{set:WP6:1}
. WP Scenario Labels
.. non derivable labels
.. derivable labels (incl. ODD labels)
.. Documentation for User Guide
.. Documentation for Specification
.. Implementation in the Format
. WP UserGuide:
.. Guidelines for GDPR compliance when using OpenLABEL (as advice)
.. Methodology for different labeling methods
... 2D/3D Bounding Boxes
... Explaining geometries
... Semantic Segmentation
.. Explaining Terms
.. Examples
.. etc.
.Breakdown by Work Packages [WPs]
[cols="1,2"]
[cols="5,25,60, 10"]
|===
| *WP Number* | 1
|*Title / Description* |
|*Deliverable* |
| *Effort (Man-days)* |
|*WP*|*Title*|*short description*|*est. days*
|*1.*|User guide | The User guide will help future users of OpenLABEL to apply the standard for their use cases. The User guide will be accompanied by examples|{WP1}
|1.1| Usage and Pragmatics group| The usage and pragmatics group will test the OpenLABEL Spec on defined examples and use cases and provide feedback to the other workpackages |{WP11}
|1.2| Writing the User guide| This sub workpackage is about writing the user guide, this will be support by a service provider |{WP12}
|*2.*|Specification Harmonization| The main task of this work package is to ensure the alignment of OpenLABEL with other OpenX Standards|{WP2}
|2.1| Aligned Terminology with OpenXOntology, OpenSCENARIO 2.0 and OpenODD| This sub working group shall create an aligned terminology for the OpenLABEL Project|{WP21}
|2.2| Add Terminology into the OpenXOntology Application Model of OpenLABEL| Apply the Terminology to an Application Model for OpenLABEL provided by the OpenXOntology|{WP22}
|*3.*| Object + Scene Labeling| The Object and Scene Labeling working group will be tasked to create the specification for the labeling of objects identified in a scene (point in time)|{WP3}
|3.1| Object Labeling| This sub working group is focused on describing how single objects can be labeled|{WP31}
|3.2| Scene Labeling| this sub working group is focused on how the labeled objects are being labeled in the context of a scene. There this workpackage has several perspectives: conditional labels, event labels, action labels, relation labels|{WP32}
|3.2.1| Condition labeling in a scene | defining the labels to represent conditions in a scene|{WP321}
|3.2.2| Event labeling in a scene | define the labels to represent events that happen in this scene, including the timeline that lead to this event|{WP322}
|3.2.3| Action labeling in a scene | define the labels to represent actions that happen in this scene, including the object that executes this action and/or is affected by this action|{WP323}
|3.2.4| Relation labeling in a scene | define how relation between any label can be expressed, e.g between two objects (bicycle and cyclist)|{WP324}
|*4.*| Scenario Labeling(adding metadata to scenario files)| The scenario labeling working group will define the scenario labels on a meta level. this will include labels that can be derived from the content of the scenario as well as labels which are non derivable.|{WP4}
|*5.*| Data Format| the working group "Data Format" will create the json format based on the input given in the concept paper and provided by the specification working group (2 - 4)|{WP5}
|*6.*| Standard Documentation| This workpackage has a close interaction with all other work package and is responsible to create the final standard document. This workpackage will be mainly executed by a service provider |{WP6}
|===
.Total effort
[options="header", cols="1,2,2,2"]
|===
| WP No. | Project member (man-days) | Service Provider (man-days) | Total (man-days)
