The OpenLABEL Concept project shall work on concepts for a future OpenLABEL standard, so this standard can full fil the following requirments
The OpenLABEL Concept project shall work on concepts for a future OpenLABEL standard, so this standard can full fil the following requirement
Also the following requirements are to consider:
.general requirements
[cols="20,80"]
|===
|general requirment|OpenLABEL shall describe the methodology how to label objects and scenarios, based on the defined ontology. This labeling should work on real and synthetic data.
|general requirment|OpenLABEL shall define the required informations to indetify and label objects and scnearios
|general requirment|OpenLABEL shall provide methods how to label objects
|general requirment|The data format proivded by OpenLABEL to label objects and scenarios should be independet form the data source
|general requirment|OpenLABEL shall get the object/termin/label definitions from the ontology project
|general requirment|Data format and specification should account for and enable the definiton of objects, events, relations, actions, intentions, subject/predicat/objects tiplets (SPO) and other entties or properties allowing for a machine and human readable knowledge representation.
|general requirement|OpenLABEL shall describe the methodology how to label objects and scenarios, based on the defined ontology. This labeling should work on real and synthetic data.
|general requirement|OpenLABEL shall define the required information to indetify and label objects and scenarios
|general requirement|OpenLABEL shall provide methods how to label objects
|general requirement|The data format proivded by OpenLABEL to label objects and scenarios should be independet form the data source
|general requirement|OpenLABEL shall get the object/termin/label definitions from the ontology project
|general requirement|Data format and specification should account for and enable the definiton of objects, events, relations, actions, intentions, subject/predicat/objects tiplets (SPO) and other entties or properties allowing for a machine and human readable knowledge representation.
|===
.technical requirments
.technical requirement
[cols="20,80"]
|===
| technical requirment | OpenLABEL shall have the capability to store metadata and labels for data, independent of the source
| technical requirment | OpenLABEL should support annotation of data from different source (extending and sharing data sets)
| technical requirment | The OpenLABEL annotation format must be quick to serialize
| technical requirment | OpenLABEL should provide metrics for quality assurance
| technical requirment | In the dataformat of OpenLABEL it needs to be possible to use different labeling methods and assign relations (1:n) to labels objects, also haveing the possiblity to add actions and intentions as label to an object will enhance OpenLABEL
| technical requirement | OpenLABEL shall have the capability to store metadata and labels for data, independent of the source
| technical requirement | OpenLABEL should support annotation of data from different source (extending and sharing data sets)
| technical requirement | The OpenLABEL annotation format must be quick to serialize
| technical requirement | OpenLABEL should provide metrics for quality assurance
| technical requirement | In the dataformat of OpenLABEL it needs to be possible to use different labeling methods and assign relations (1:n) to labels objects, also haveing the possiblity to add actions and intentions as label to an object will enhance OpenLABEL
@@ -6,7 +6,7 @@ The OpenLABEL Concept project has the following content
=== User guide "how to label"
In the project the different labeling methodologys will be research and the experience of the attending project members will helb to create a first draft of a guide for an OpenLABEL user guide.
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:
* application of the future OpenLABEL standard,
...
...
@@ -14,8 +14,8 @@ This guide will cover:
* guide on how to label objects in provided data (depending on the source)
* Terminology
The format structure will be created in close interaction with the Ontology project, to achive a interoperability between these to projects
also the lableing structure sdhould be the same for objects and scenarios.
The format structure will be created in close interaction with the Ontology project, to achieve a interoperability between these to projects
also the labelling structure should be the same for objects and scenarios.
=== Labeling Specifications Design
...
...
@@ -39,13 +39,13 @@ In the specifiaction design the group has to consider how to label objects in th
==== Scenario labeling
In the specifiaction design the group has to consider how to label scnearios in the OpenLABEL standard. The requirements from this workgroup will be shared with the ontology project.
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.
=== Labeling Data Format
In the OpenLABEL Concept project the group will come up with a proposal on what format to use for the OpenLABEL annotation format (e.g. json).
Independet of the format the concept paper will also contain a first version of a possbile labeling structure
In the OpenLABEL Standard Development Project the group will create the annotation format based on the proposed format from the OpenLABEL Concept Project.
Independent of the format the concept paper will also contain a first version of a possible labeling structure
e.g.:
[source]
...
...
@@ -54,7 +54,7 @@ metadata / header
frame
source
label
type = object/scneario/...
type = object/scenario/...
name (ontology link to description)
relation
label method
...
...
@@ -66,16 +66,17 @@ label
General requirements for the format and the structure are:
* make the labeled data mergeable (without converter in between) to extend exsisting datasets
* make the labeled data mergeable (without converter in between) to extend existing datasets
* make Datasets comparable
* easy to understand
* humand readable
* human readable
=== OpenLABEL Standard documentation
* The OpenLABEL Project will provide a Concept paper for the future standard covering the specification of the format and the taxonomy (the OpenLABEL Project will receive input from the ontology project and provide requirements to the ontology project).
* Userguide ("how to label") / Styleguide for OpenLABEL
* Examples for the indivudual concepts
* 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 Userguide ("how to label") / Styleguide for OpenLABEL
** incl. Examples for the individual methods and concepts of OpenLABEL
