Update the OpenX-Examples to rDNS.

Signed-off-by: Georg Seifert <georg.seifert@carissma.eu>

Author: DerBaertige

osi_lane.proto

@@ -56,10 +56,10 @@ message Lane
     // from one or more objects or external references. An example here is the 
     // reference to the lane defined in a OpenDRIVE map.
     //
-    // For OpenDRIVE 1.6 the items should be set as following:
+    // For OpenDRIVE the items should be set as following:
     // * reference = URI to map, can remain empty if identical with definiton
     //               in \c GroundTruth::map_reference
-    // * type = "OpenDRIVE 1.6"
+    // * type = "net.asam.opendrive"
     // * identifier[0] = id of t_road
     // * identifier[1] = s of t_road_lanes_laneSection
     // * identifier[2] = id of t_road_lanes_laneSection_left_lane,
@@ -752,7 +752,7 @@ message LaneBoundary
 
     // Optional external Reference to the Lane Boundary Source
     //
-    // \note For OpenDRIVE 1.6 there is no direct possibility to reference the
+    // \note For OpenDRIVE there is no direct possibility to reference the
     //       RoadMark, as there is no unique identifier in this sub-object.
     //
     // \note For non-ASAM Standards, it is implementation-specific how

osi_object.proto

@@ -45,18 +45,18 @@ message StationaryObject
     // The ExternalReference point to the source of an stationary object, if it
     // is derived from an external sources like OpenDRIVE or OpenSCENARIO.
     //
-    // For OpenDRIVE 1.6 the objects should be set as following:
+    // For OpenDRIVE the objects should be set as following:
     // * reference = URI to map, can remain empty if identical with definiton
     //               in \c GroundTruth::map_reference
-    // * type = "OpenDRIVE 1.6"
+    // * type = "net.asam.opendrive"
     // * identifier[0] = "object" for t_road_objects_object and
     //                   "bridge" for t_road_objects_bridge
     // * identifier[1] = id of t_road_objects_object or t_road_objects_bridge
     //
-    // For OpenSCENARIO 1.0 the entities of the type MiscObject, which describes
+    // For OpenSCENARIO the entities of the type MiscObject, which describes
     // partly stationary objects should be set as following:
     // * reference = URI to the OpenSCENARIO File
-    // * type = "OpenSCENARIO 1.0"
+    // * type = "net.asam.openscenario"
     // * identifier[0] = Entity-Type ("MiscObject")
     // * identifier[1] = name of MiscObject in Entity
     //
@@ -397,14 +397,14 @@ message MovingObject
     // The ExternalReference point to the source of an moving object, if it
     // is derived from an external sources like OpenSCENARIO.
     //
-    // For OpenSCENARIO 1.0 the entities of the type Vehicle or Pedestrian,
+    // For OpenSCENARIO the entities of the type Vehicle or Pedestrian,
     // which describes moving objecs should be set as following:
     // * reference = URI to the OpenSCENARIO File
-    // * type = "OpenSCENARIO 1.0"
+    // * type = "net.asam.openscenario"
     // * identifier[0] = Entity-Type ("Vehicle" or "Pedestrian")
     // * identifier[1] = name of Vehicle/Pedestrian in Entity
     //
-    // \todo OpenSCENARIO 1.0 currently does not provide an animal type.
+    // \todo OpenSCENARIO currently does not provide an animal type.
     // 
     // \note For non-ASAM Standards, it is implementation-specific how
     //       source_reference is resolved.

osi_roadmarking.proto

@@ -61,13 +61,13 @@ message RoadMarking
     // is derived from one or more objects or external references. An example
     // here is the reference to the signal defined in a OpenDRIVE map.
     //
-    // For OpenDRIVE 1.6 the items should be set as following:
+    // For OpenDRIVE the items should be set as following:
     // * reference = URI to map, can remain empty if identical with definiton
     //               in \c GroundTruth::map_reference
-    // * type = "OpenDRIVE 1.6"
+    // * type = "net.asam.opendrive"
     // * identifier[0] = id of t_road_signals_signal
     //
-    // \note In OpenDRIVE 1.6 there is also the possibility to define surface
+    // \note In OpenDRIVE there is also the possibility to define surface
     //       markings as an object. In this case, the associated object is
     //       usually referenced within OpenDRIVE using the reference
     //       t_road_signals_signal_reference, which allows it to be

osi_trafficlight.proto

@@ -48,10 +48,10 @@ message TrafficLight
     // derived from one or more objects or external references. An example here
     // is the reference to the signal defined in a OpenDRIVE map.
     //
-    // For OpenDRIVE 1.6 the items should be set as following:
+    // For OpenDRIVE the items should be set as following:
     // * reference = URI to map, can remain empty if identical with definiton
     //               in \c GroundTruth::map_reference
-    // * type = "OpenDRIVE 1.6"
+    // * type = "net.asam.opendrive"
     // * identifier[0] = id of t_road_signals_signal
     //
     // \note For non-ASAM Standards, it is implementation-specific how

osi_trafficsign.proto

@@ -163,10 +163,10 @@ message TrafficSign
     // derived from one or more objects or external references. An example here
     // is the reference to the signal defined in a OpenDRIVE map.
     //
-    // For OpenDRIVE 1.6 the items should be set as following:
-    // * reference = URI to map, can remain empty if identical with definiton
+    // For OpenDRIVE the items should be set as following:
+    // * reference = URI to map, can remain empty if identical with definition
     //               in \c GroundTruth::map_reference
-    // * type = "OpenDRIVE 1.6"
+    // * type = "net.asam.opendrive"
     // * identifier[0] = id of t_road_signals_signal
     //
     // \note For non-ASAM Standards, it is implementation-specific how