Autoexport from the XML-Schema for element IS:levelCrossingsIS of railML® version 3.3 | |
| Description | container element for all levelCrossing elements |
| Subschema | infrastructure |
| Parents* | |
| Children** |
levelCrossingIS (1..*) |
| Attributes:None | |
| *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:levelCrossingsIS
Jump to navigation
Jump to search
Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IS:levelCrossingsIS of railML® version 3.2 | |
| Description | container element for all levelCrossing elements |
| Subschema | infrastructure |
| Parents* | |
| Children** |
levelCrossingIS (1..*) |
| Attributes:None | |
| *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 | |
Autoexport from the XML-Schema for element IS:levelCrossingsIS of railML® version 3.1 | |
| Description | container element for all levelCrossing elements |
| Subschema | infrastructure |
| Parents* | |
| Children** |
levelCrossingIS (1..*) |
| Attributes:None | |
| *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 | |