TT:timetableScenario/3.2: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
(Updated page TT:timetableScenario/3.2 using XSD2MediaWiki Converter 1.1.1) |
(Updated page TT:timetableScenario/3.2 using XSD2MediaWiki Converter 1.1.1) |
||
| Line 7: | Line 7: | ||
|version=3.2 | |version=3.2 | ||
|parent={{parent|subschema=TT|name=timetableScenarios}} | |parent={{parent|subschema=TT|name=timetableScenarios}} | ||
|children={{child|subschema= | |children={{child|subschema=Generic|name=name|multiplicity=0..*}}, {{child|subschema=Generic|name=timePeriodRef|multiplicity=0..*}} | ||
|attributes={{attribut|name=id|pflicht=1|typ=xs:string|documentation=unique identifier|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}\}}}}} | |attributes={{attribut|name=id|pflicht=1|typ=xs:string|documentation=unique identifier|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}\}}}}} | ||
}} | }} | ||
Latest revision as of 15:48, 17 May 2024
Automatic Schemaexport for Element timetableScenario
Autoexport from the XML-Schema for element TT:timetableScenario of railML® version 3.2 | |
| Documentation | A timetable scenario is an abstract entity used to group validities and in turn trains. By itself it only provides a name. It can be used to exchange parallel timetabling ideas at an early stage of planning or indicate later on the conceptual origin of trains. |
| Subschema | timetable |
| Parents* | |
| Children | name (0..*), timePeriodRef (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. | |