@@ -21,6 +21,7 @@ In the end the standard and the user guide will cover:
** abstract labeling of scenarios
In the openLabel concept paper the following has been reached:
* A semantic description of the most important labeling methods.
** I.e. how to label what?
* A suggestion of a specific file format and its characteristics
...
...
@@ -30,6 +31,7 @@ In the openLabel concept paper the following has been reached:
** Specific classes and attributes that are special for labeling - and thus need to be provided by openLabel to OpenXOntology comprise for example "occlusion" (how is it labeled, what levels exist?) or "truncation" (truncation describes the cut off of objects at the edge of a frame or a scan)
A special focus of this standard project is to built upon the aforementioned points as follows:
* Review of the labeling methods and putting into context to existing labeling standards or guidelines
* Complementing the list of labeling methods and their description
* Refinement of the labeling standard with regard to market needs.
Use cases in the context of ASAM standards describe the external behavior of the standardized system, i.e. the interaction of the system with a user or with another system. The description of use cases is particularly useful for explaining the motivation for new standards, major version development projects or the addition of new features in minor version development projects.
ASAM subdivides use cases into three tiers, where each lower level is a refinement of its immediate higher level.
* Business use case: Describes an economic advantage, company need, process, method or element of a larger tool chain that involves many people of a company or multiple companies in a customer supplier relationship.
Example: ECU calibration and measurement.
* End User Use Case: Describes a need, process, method or element of a tool chain that is handled by one person while he carries out specific tasks within a company use case.
...
...
@@ -55,9 +56,9 @@ annotate data from different sensor types (e.g. Lidar, Camera, Radar, Ultrasonic
[cols="1,5"]
|===
|*Type* | End User Use Case
|*Type* | Business Use Case
|*Title* | Reduce human learning effort for Sensor Data Annotation
|*Description* | With a standardized format and standard sets of classes for sensor data annotation, the ordering process for sensor data annotation services would be easier and the risk of different understandings of annotation specifications could be reduced. With this the time a labeler needs to learn how the labeling works will be reduced.
|*Description* a| With a standardized format and standard sets of classes for sensor data annotation, the ordering process for sensor data annotation services would be easier and the risk of different understandings of annotation specifications could be reduced. With this the time a labeler needs to learn how the labeling works will be reduced.
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.
==== Use Case Application Group (Usage and Pragmatics)
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
=== Labeling Specifications Design
Often, the frames coming from sensors such as cameras depicts complex situations going on in the surrounding of the vehicle.
...
...
@@ -74,7 +78,7 @@ General requirements for the format and the structure are:
* easy to understand
* human readable
=== OpenLABEL Standard documentation
=== OpenLABEL Standard documentation (Service Provider)
* The OpenLABEL Standard development project will provide a standard document based on the concept paper from the OpenLABEL Concept Project
* In the Standard Development Project the group will also create a user guide ("how to label") / style guide for OpenLABEL
...
...
@@ -83,3 +87,21 @@ 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]
