IS:opEquipment/3.2: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
(Created page IS:opEquipment/3.2 using XSD2MediaWiki Converter 1.0.6) |
(Updated page IS:opEquipment/3.2 using XSD2MediaWiki Converter 1.1.1) |
||
| Line 7: | Line 7: | ||
|version=3.2 | |version=3.2 | ||
|parent={{parent|subschema=IS|name=operationalPoint}} | |parent={{parent|subschema=IS|name=operationalPoint}} | ||
|children={{child|subschema= | |children={{child|subschema=generic|name=ownsInfrastructureElement|multiplicity=0..*}}, {{child|subschema=generic|name=ownsPlatform|multiplicity=0..*}}, {{child|subschema=generic|name=ownsServiceSection|multiplicity=0..*}}, {{child|subschema=generic|name=ownsSignal|multiplicity=0..*}}, {{child|subschema=generic|name=ownsStoppingPlace|multiplicity=0..*}}, {{child|subschema=generic|name=ownsTrack|multiplicity=0..*}} | ||
|attributes={{attribut|name=numberOfStationTracks|pflicht=0|typ=xs:positiveInteger|documentation=number of tracks that are available for operation within the operational point}} | |attributes={{attribut|name=numberOfStationTracks|pflicht=0|typ=xs:positiveInteger|documentation=number of tracks that are available for operation within the operational point}} | ||
}} | }} | ||
Revision as of 12:40, 8 February 2024
Automatic Schemaexport for Element opEquipment
Autoexport from the XML-Schema for element IS:opEquipment of railML® version 3.2 | |
| Documentation | child element summarizing the equipment of the operational point |
| Subschema | infrastructure |
| Parents* | operationalPoint |
| Children | ownsInfrastructureElement (0..*), ownsPlatform (0..*), ownsServiceSection (0..*), ownsSignal (0..*), ownsStoppingPlace (0..*), ownsTrack (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. | |