IS:networkLocation/3.1: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
(Created page with "<noinclude>Automatic Schemaexport for Element '''networkLocation'''</noinclude> {{Schemaexport |element=networkLocation |subschema=infrastructure |subschema_slug=IS |version=3...") |
No edit summary |
||
| Line 35: | Line 35: | ||
{{parent|subschema=IS|name=underCrossing}}, | {{parent|subschema=IS|name=underCrossing}}, | ||
{{parent|subschema=IS|name=weightLimit}} | {{parent|subschema=IS|name=weightLimit}} | ||
|attributes={{attribut|name=networkRef|pflicht=0|typ=xs:IDREF|documentation=reference to a railway topology <network> element|patterns={{pattern|(urn:uuid:)?[0-9a-fA-F] | |attributes={{attribut|name=networkRef|pflicht=0|typ=xs:IDREF|documentation=reference to a railway topology <network> element|patterns={{pattern|(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}\}}}}} | ||
}} | }} | ||
Revision as of 18:16, 23 December 2019
Automatic Schemaexport for Element networkLocation
Autoexport from the XML-Schema for element IS:networkLocation of railML® version 3.1 | |
| Documentation | This element is not documented in the schema! |
| Subschema | infrastructure |
| Parents* | horizontalCurve, gradientCurve, geometryPoint, balise, border, bufferStop, crossing, derailerIS, electrificationSection, keyLockIS, levelCrossingIS, line, loadingGauge, operationalPoint, overCrossing, platform, restrictionArea, serviceSection, signalIS, speedSection, stoppingPlace, switchIS, track, trackBed, trackGauge, trainDetectionElement, trainProtectionElement, trainRadio, underCrossing, weightLimit |
| Children | None |
| 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. | |