Skip to content

O
OpenLABEL 1.0 Proposal
提交 5810c980 编写于 作者: Nicco Dillmann's avatar Nicco Dillmann
浏览文件
操作

adding results from first discussion

上级 6f25d26a
隐藏空白字符变更
内嵌 并排
正在显示 包含 47 行增加 和 29 行删除
subchapters/1-2_motivation.adoc
浏览文件 @ 5810c980
......@@ -6,7 +6,7 @@ From working with different customers, a significant fragmentation emerged in th
The lack of a common Labeling standard in the industry is the root cause of several different issues:
* *Hampered Vehicle2X Interaction*: the different descriptions/understandings of surroundings may cause casualties in complex situations involving two or more different ADSs OpenLABEL could support filling the existing V2X standards like ITS G5.
* *Hampered Vehicle2X Interaction*: the different descriptions/understandings of surroundings may cause casualties in complex situations involving two or more different ADS's OpenLABEL could support filling the existing V2X standards like ITS G5.
* *Precluded sharing*: It results highly difficult if not impossible to share data across organizations adopting different Labeling taxonomies and specifications
* *Lowered Annotation quality*: Each individual labeling task requires ad-hoc training and even custom software features development to be completed, that translates into a higher probability of errors and thus a threat to safety
* *Deprecation of old labels*: Long-term operation of ADS development imply changes in quantity and richness of labels to be produced, considering the evolution of the driving scenes, new sensors, and scenarios. As a consequence, a flexible descriptive language is required to absorb future extensions/modifications of labels and guarantee back-compatibility.
......
subchapters/2_technical-content.adoc
浏览文件 @ 5810c980
......@@ -37,11 +37,11 @@ truck partially occluded by a car and so on.
* Enable Quality assessments
==== Object labeling
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 ontology project. In addition the project group will align the OpenLABEL Object labels with the OpenSCENARIO 2.0 Domain Model, to ensure compatibility.
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
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 ontology project. In addition the project group will align the OpenLABEL Object labels with the OpenSCENARIO 2.0 Domain Model, to ensure compatibility.
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.
......
subchapters/3-1_required_resources.adoc
浏览文件 @ 5810c980
......@@ -4,36 +4,54 @@ A breakdown of the project into individual work packages and the corresponding e
==== Effort
.Breakdown by Work Packages [WPs]
[cols="1,2"]
|===
| *WP Number* | 1
|*Title / Description* | Annotation Format and Structure,
|*Deliverable* |Concept paper containing: +
- concept for a annotation format including a proposed structure capable to label scenarios and objects +
- The WP will consider exisiting labeling experience and format.
| *Effort (Man-days)* |Estimated work effort to be performed by the service provider.
|===
==== Draft the new Workpackage Structure
[cols="1,2"]
|===
| *WP Number* | 2
|*Title / Description* | Labeling methods for scenarios and objects, OpenLABEL UserGuide
|*Deliverable* |Concept paper containing: +
- description of indetfied labeling methods for objects and scenarios +
- draft description of how to use specific methods for different usecases
| *Effort (Man-days)* |Estimated work effort to be performed by the service provider.
|===
. 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)
. 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
. WP Scene/Action/Events/Triggers Labels
.. Documentation for User Guide
.. Documentation for Specification
.. Implementation in the Format
. 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"]
|===
| *WP Number* | 3
|*Title / Description* | Labeling taxonomy, Taxonomy Structure (shared WP with Ontology)
|*Deliverable* |Concept paper containing: +
- usage of ontologys for OpenLABEL +
- list of requirements for the ASAM ontology project +
- example list of required objects and labels +
| *Effort (Man-days)* |Estimated work effort to be performed by the service provider.
| *WP Number* | 1
|*Title / Description* |
|*Deliverable* |
| *Effort (Man-days)* |
|===
......
Markdown 格式
0% or
您添加了 0 人 到此讨论。请谨慎行事。
先完成此消息的编辑！
想要评论请 注册 或