|
|
| Line 8: |
Line 8: |
| {{robot|subschema=IS|element=netRelation|parent=}} | | {{robot|subschema=IS|element=netRelation|parent=}} |
| ==={{semantics}}=== | | ==={{semantics}}=== |
| | {{semcon| There must be no "inverse" net relations in the topology, i.e. if "nr1 elemeneA ne1", "nr1 elementB ne2" and "nr2 elemeneA ne2", "nr2 elementB ne1" then topology is not valid. See invalid code below. |
| | |
| | Compare {{ticket|xxx}} |
| | |status=proposed|proposed=2021-04-22|forum={{ticket|xxx}} |
| | |id=IS:015}} |
| {{importComment}} | | {{importComment}} |
| =={{examples}}== | | =={{examples}}== |
| Line 13: |
Line 18: |
| =={{Additional Information}}== | | =={{Additional Information}}== |
| ==={{Notes}}=== | | ==={{Notes}}=== |
| | <syntaxhighlight lang=xml> |
| | <netRelations> |
| | <!-- invalid topology --> |
| | <netRelation id="nr1"> |
| | <elementA ref="ne1"/> |
| | <elementB ref="ne2"/> |
| | </netRelation> |
| | <netRelation id="nr2"> |
| | <elementA ref="ne2"/> |
| | <elementB ref="ne1"/> |
| | </netRelation> |
| | </netRelations> |
| | </syntaxhighlight> |
| ==={{Open issues}}=== | | ==={{Open issues}}=== |
Latest revision as of 10:51, 22 April 2024
Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IS:netRelation of railML ® version 3.2 |
| Documentation
|
The NetRelation type is derived from the RailTopoModel class PositionedRelation.
|
| Subschema
|
infrastructure
|
| Parents*
|
netRelations
|
| Children
|
elementA (1..1), elementB (1..1), isValid (0..*), name (0..*)
|
Attributes:
- navigability: This attribute is not documented in the schema! (optional;
xs:string)
- Possible values:
- positionOnA: This attribute is not documented in the schema! (optional;
xs:integer)
- Possible values:
- positionOnB: This attribute is not documented in the schema! (optional;
xs:integer)
- Possible values:
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[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.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
Autoexport from the XML-Schema for element IS:netRelation of railML ® version 3.1 |
| Documentation
|
The NetRelation type is derived from the RailTopoModel class PositionedRelation.
|
| Subschema
|
infrastructure
|
| Parents*
|
netRelations
|
| Children
|
elementA (1..1), elementB (1..1), isValid (0..*), name (0..*)
|
Attributes:
- navigability: This attribute is not documented in the schema! (optional;
xs:string)
- Possible values:
- positionOnA: This attribute is not documented in the schema! (optional;
xs:integer)
- Possible values:
- positionOnB: This attribute is not documented in the schema! (optional;
xs:integer)
- Possible values:
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:ID; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[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.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
Changes 3.1→3.2
The children have changed.
The attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
<netRelations>
<!-- invalid topology -->
<netRelation id="nr1">
<elementA ref="ne1"/>
<elementB ref="ne2"/>
</netRelation>
<netRelation id="nr2">
<elementA ref="ne2"/>
<elementB ref="ne1"/>
</netRelation>
</netRelations>
Open Issues
