@@ -4,26 +4,66 @@ The goal of the proposed project is to create a the first OpenLABEL Standard bas
The OpenLABEL Standard Development Project will also be the first standard to use the OpenXOntology Domain Model, and therefore be closely couple with the OpenXOntology Project, to further improve and develop the modelling approach and the content of the domain model
The OpenLABEL Standard Development Project has the following content
The OpenLABEL Standard Development Project has the following content. The work in the project will be seperated in different workpackages and subworkpackes
[cols="5,30,65"]
|===
|*WP*|*Title*|*short description*
|*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
|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
|1.2| Writing the User guide| This sub workpackage is about writing the user guide, this will be support by a service provider
|*2.*|Specification Harmonization| The main task of this work package is to ensure the alignment of OpenLABEL with other OpenX Standards
|2.1| Aligned Terminology with OpenXOntology, OpenSCENARIO 2.0 and OpenODD| This sub working group shall create an aligned terminology for the OpenLABEL Project
|2.2| Add Terminology into the OpenXOntology Application Model of OpenLABEL| Apply the Terminology to an Application Model for OpenLABEL provided by the OpenXOntology
|*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)
|3.1| Object Labeling| This sub working group is focused on describing how single objects can be labeled
|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
|3.2.1| Condition labeling in a scene | defining the labels to represent conditions in a scene
|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
|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
|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)
|*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.
|*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)
|*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
|===
=== User guide "how to label"
In the project the different labeling methodology will be researched and the experience of the attending project members will help to create a first draft of a guide for an OpenLABEL user guide.
This guide will cover:
In the project the different labeling methodologies will be documented and the experience of the attending project members will help to create a guide for the application if OpenLABEL.
* application of the future OpenLABEL standard,
* explanations of the labeling methods (e.g 3D bounding box vs. semantic segmentation)
* guide on how to label objects in provided data (depending on the source)
* Terminology
The OpenLABEL User Guide will cover:
The format structure will be created in close interaction with the Ontology project, to achieve an interoperability between these to projects.
Also the labeling structure should be the same for objects and scenarios.
* labeling methodology
** What are different labeling methods and how shall they be applied?
** Examples for labeling methodologies are semantic segmentation or 2D Bounding boxes.
* labeling structure (including relations)
** How do the different label classes relate to each other?
** The classes are the classificators of the labels, e.g. "car", "pedestrian".
* file format and structure definitions
** How are the labels stored, with which information?
* scenario labeling
** The labeling of scenarios is special in some points due to information that might not be extractable from single frames.
** Due to their importance for ADAS and AD validation and testing, scenario labels are discussed explicitly as own topic.
** labels derived from object labels
** abstract labeling of scenarios
==== Use Case Application Group (Usage and Pragmatics)
The workpackage "User Guide" has two sub working groups
this workpackage tries to apply OpenLABEL for different use cases and perspectives, these examples and use cases will be documented in the user guide and will provide feedback to the other workpackages
. Usage and Pragmatics: This working group will be using the OpenLABEL Specification and provide feedback to the other working groups, in terms of improvement suggestion and pointing out gaps, contradictions or limitations of the specification.
. Documentation User Guide: This workpackage write the user guide, with the provided input from the OpenLABEL concept paper and the feedback from the other working group, in particular from the "Usage and Pragmatics Group"
=== Labeling Specifications Design
=== Specification Harmonization
This workpackage is responsible for the alignment of OpenLABEL with the other standards within the Simulation Domain @ ASAM.
This means in particular a close link to the OpenXOntology and the Domain Model group of the OpenSCENARIO 2.0 project.
This workpackage has to major tasks
. Create a common terminology for the OpenLABEL Project, this terminology needs to be aligned with the mentioned standards. As a basis the MVP from the OpenXOntology project will be used
. Apply the agreed terminology onto the Application model for OpenLABEL provided from the OpenXOntology.
=== Object and Scene Labeling:
Often, the frames coming from sensors such as cameras depicts complex situations going on in the surrounding of the vehicle.
Objects appearing in a scene are seldom fully visible.
...
...
@@ -44,7 +84,17 @@ truck partially occluded by a car and so on.
In the specification design the group has to consider how to label objects in the OpenLABEL standard. The requirements from this workgroup will be shared with the OpenXOntology project. In addition the project group will align the OpenLABEL Object labels with the OpenSCENARIO 2.0 Domain Model, to ensure compatibility.
==== Scenario labeling
==== Scene labeling
In the specification design the group has to consider how to label scenes (point in time) in the OpenLABEL standard. In a scene the labeled objects need to be placed and the are further entities that can be labeled. This includes:
. *Events:* An event can be triggered by an object or effect an labeled object, usually an event is present over several consecutive scenes
. *Actions/Intention:* similar a events actions can either be triggered or lead to events. usually an action can be labelled over several consecutive scenes, as it builds up.
. *Conditions:* In a scene it might be necessary to label conditions
The requirements from this workgroup will be shared with the OpenXOntology project. In addition the project group will align the OpenLABEL scene labels with the OpenSCENARIO 2.0 Domain Model, to ensure compatibility.
=== Scenario labeling
In the specification design the group has to consider how to label scenarios in the OpenLABEL standard. The requirements from this workgroup will be shared with the OpenXOntology project. In addition the project group will align the OpenLABEL Object labels with the OpenSCENARIO 2.0 Domain Model, to ensure compatibility. In the concept project the basis for the scenario labels is based on the PAS BSI 1883.
...
...
@@ -86,22 +136,5 @@ General requirements for the format and the structure are:
. Userguide [in parallel] (t.b.d + Service Provider)
.. Application Group (Usage and Pragmatics) [starting point]
. Specification [in parallel to usage and pragmatics][depends on the MVP+ Application Ontology]
. Specification Harmonization (OSC 2.0 and OpenXOntology)(t.b.d)
.. Common Terminology
. Object + Scene Labeling (u.ai)
.. Object Labeling
.. Scene Labeling (interpreted Data labeling)
... Conditions
... Events
... Scene
... Actions
. Scenario Labeling (adding metadata to scenario files)(WMG)
. Data Format [depends on specification / second half of the project](Vicomtech)
. Standard Documentation [once the service provider is selected]
