Search results

-[0-9a-fA-F]{12}}); compare: Dev:Identities *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts

been changed. In The RailTopoModel® wiki <RTM:linearPositioningSystem> elements are the instances of a localization expressed in a linear reference system

element is part of GML, version 3.2 that is referenced by railML® version 3.2. Within railML®, the railML® version is significant for the handling of this element

a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts

a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts

a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts

a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}) *Notice: Elements may have different parent elements. As a consequence they may be used in different contexts

system. A list of Common railML® elements can be found here. A list of Generic railML® elements can be found here.

Conclusion: The use of railML® <balise> elements is optional. But if railML® <balise> elements are used, then the railML® <baliseGroup> elements are mandatory.

There is no difference in handling between elements, attributes, enumeration values, occurence changes... In railML® 3, the template will generally not be

first approach basically simply extends the original railml elements track and operationalPoint of railML 3.2 and adds a new sub element “priceCategory” that

within the railML® schemas. On the other hand, software tools may refer to certain railML® elements, that are not referred to within the railML® file. The

XML-Schema for element XS:any of railML® version 3.2   Documentation provide an extension point for non-railML elements in foreign namespace Subschema xmlschema

This element does not appear in railML® 3.1 within the generic subschema. It is available only in railML® 3.2. There exists an element <CO:designator>

This element does not appear in railML® 3.2 within the CO subschema. It is available only in railML® 3.1. There exists an element <generic:designator>

This element does not appear in railML® 3.1 within the generic subschema. It is available only in railML® 3.2. There exists an element <CO:name> that might

This element does not appear in railML® 3.2 within the CO subschema. It is available only in railML® 3.1. There exists an element <generic:name> that might

This element does not appear in railML® 3.1 within the generic subschema. It is available only in railML® 3.2. There exists an element <CO:external> that

three letters. Extensions in railML® base elements (with id, code...) have to be inserted before the other railML® child elements. In all other cases do the