Autoexport from the XML-Schema for element IS:netConnector of railML® version 3.3 | |
| Description | netConnectors are elements that are placed at the edge of a split infrastructure. They represent points at which the infrastructure may be reconnected again in an importing system. It is important to note that a netConnector can only aggregate with other netConnectors. The |
| Subschema | infrastructure |
| Parents* | |
| Children** |
name (0..*), isValid (0..*), elementCollection (0..1), designator (0..*) |
Attributes:
| |
| *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. **Notice: To learn, how to interpret multiplicity information like (0..*) go to The W3C Recommendation on XML Schema | |
IS:netConnector
Jump to navigation
Jump to search
Introduction
Documentation
Syntax
This element does not appear in railML® 3.2 within the IS subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. for further questions.
This element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. for further questions.
Changes 3.2→3.3
There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
Introduced with version 3.3.
Semantics
Best Practice / Examples
- Split Simple example
-
-
-
-
Further explanation is available under Dev:Splitting and merging railML files .
Additional Information
|
Notes
Examples were reviewed by the coordinator (link to the railML® website) of the Infrastructure subschema on 2026-01-26.