Search results

numbers and in Template:Railml IDs are XML IDs (which, according to the specification, must not start with numbers), the UUIDs in Template:Railml had to

"graph" where the track is an "edge".   Please, be aware of the semantic constraint(s)! id: XML-file-wide unique, machine-interpretable identity, required

syntactic constraints. Proposed semantic constraints are listed in Category:Semantic constraints_proposed. A list of the semantic constraints by introduction

stick to our common templates to allow for a standardized documentation. Some essential templates are explained on railML® markup templates. Especially, employ

connection   Parent: <trackEnd> Children: None [1..1] A <connection> is an element to determine which branches of a track are connected at a certain position

connection   Parent: <trackBegin> Children: None [1..1] A <connection> is an element to determine which branches of a track are connected at a certain

folloging templates: Template:Site for links to railml.org pages outside our wikis. template:external for external links. For Gitlab commits, use Template:Commit

does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed. Please, apply Dev:usingAny

does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed. Please, apply Dev:usingAny

textToSpeechTemplate   Parent: <audioFragment> Children: None [0..1] The element <textToSpeechTemplate> Allows to provide a text that is used by TTS (Text-To-Speech)

textToSpeechTemplate   Parent: <audioFragment> Children: None [0..1] The element <textToSpeechTemplate> Allows to provide a text that is used by TTS (Text-To-Speech)

Defaults Optional attributes may have defaults. Please, employ Template:Constraint, wherever defaults are employed. All pages where defaults are defined

in additionalName The following templates may be used at every wiki page for refering to a certain simple type constraint. It shows a link to the basic W3C

childRule   Parent: <operatingRule> Children: None [0..∞] Reference to any another rule included here as part of the main rule.(introduced with version

providing its semantics with an "Intro"-Template of the next proposed version Add or change the attribute to "constraints" providing its type If needed, declare

visualized by <trackElementVis> or <objectVis> by finding its position in the Template:Eml hierarchy. Every child of a <track> element is visualized by <trackElementVis>

pages in The railML® 2 wiki are being created with template Template:ElementDocu. Employing this template grants for a standardized design. The templat specifies

audioFragment   Parent: <audioFragments> Children: <textToSpeechTemplate> [1..∞] An <audioFragment> specifies audio resources in an importing system to

<ocpTT>.(introduced with version 2.5)   Please, be aware of the semantic constraint(s)! track: Designation of the track. Bezeichnung des Bahnhofsgleises.

<additionalName>, <xs:any>, <trainPartSequence> [0..1] A pattern train is a template for other trains. It is not itself a train that is supposed to run. A pattern

audioFragment   Parent: <audioFragments> Children: <textToSpeechTemplate> [1..∞] An <audioFragment> specifies audio resources in an importing system to

verboseness <audioFragments> <audioFragment> code, rail:lang <textToSpeechTemplate> xsi:type <serviceSections> <serviceSection> absPos, absPosOffset, cleaning

REDIRECT Template:Table/Dev:Semantic Constraints

How to deal with Semantic Constraints Guidelines to enhance the wiki documentation How to join the railML® wiki Wiki-Templates Access statistics Feel free

editors Guide, guide on how to edit Wiki contents Dev:Special Wiki Markup templates for referring to a certain railML® element documentation page All Experienced

influence="decreasing" verbalConstraint="Desiro" description="speed profile for trains fulfilling a certain verbal constraint"/> <speedProfile id="sp7" name="Tilting"

what are no semcons? Questions Definition Suggestion: A semantic constraint is a constraint that cannot be implemented in an XSD. What is obviously a semcon

Category for templates around semantic constraints

employing a template. Please, expand the template before editing the page: replace “docBase” by “subst:docBase”.! After expanding template docBase, please

Category:MarkupTemplate Template:! Template:Wiki2 Template:Wiki3 Template:Head Template:Mirror Template:Flag Template:Proposal Template:Timestamp Template:Rb Template:Fixme

preview of page TT:announcements as to circumvent Template:Unlock. The preview is made with Template:Frame. Is anymething missing? purge this page. purge

the traction vehicle to the track.   Please, be aware of the semantic constraint(s)! id: XML-file-wide unique, machine-interpretable identity, required

(distant between the rails) changes.   Please, be aware of the semantic constraint(s)! id: XML-file-wide unique, machine-interpretable identity, required

an infrastructure element changes.   Please, be aware of the semantic constraint(s)! id: XML-file-wide unique, machine-interpretable identity, required

identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code

this is a preview of page TT:text as to circumvent Template:Unlock. The preview is made with Template:Frame. Is anymething missing? purge this page. purge

child <clearanceGauge>, comp. #Notes.   Please, be aware of the semantic constraint(s)! id: XML-file-wide unique, machine-interpretable identity, required

allowed axle weight on a track changes.   Please, be aware of the semantic constraint(s)! id: XML-file-wide unique, machine-interpretable identity, required

attribute of the associated <operatingPeriod> element. This operatingPeriod constraints the dates the referenced annotation is valid. If this is absent the referenced

identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code

identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code

at the end of the electrification.   Please, be aware of the semantic constraint(s)! id: XML-file-wide unique, machine-interpretable identity, required

identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code

infrastructure element and its attributes.   Please, be aware of the semantic constraint(s)! id: XML-file-wide unique, machine-interpretable identity, required

identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code

identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code

identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code

and and/or superelevation on a track.   Please, be aware of the semantic constraint(s)! id: XML-file-wide unique, machine-interpretable identity, required

identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code

identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code

preview of page IS:trainProtection as to circumvent Template:Unlock. The preview is made with Template:Frame. Is anymething missing? purge this page. purge

identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code

identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code

identification of the object across exchange partners, usecase specific uniqueness constraints may apply. Please see our description of the differences between id, code

FIXME

value: tLengthMM (xs:decimal, 6 fraction digits, length value measured in millimeter); default: 1435; optional

type: tPowerTransmissionType (union of (restriction of xs:string, tOtherEnumerationValue); tOtherEnumerationValue is an arbitrary string starting with

at semantic constraints with template:semconHint! The template has one unnamed obligatory argument and four named arguments: 1: The constraint. status: The

type: tElectrificationType (union of (restriction of xs:string, tOtherEnumerationValue)); default: none; optional voltage: tVoltageVolt (xs:decimal, 1

and Examples have been merged The template depends on Template:Deu. There is abig number of templates building on Template:ElementDocu. {{ElementDocu|Ele

xml:lang: xs:language, language identification, optional

FIXME xs:anyURI, optional FIXME xs:anyURI, optional

ocpStationRef xs:IDREF, optional controllerRef xs:IDREF, optional

softwareVersion xs:string, optional onBoardUnitID xs:string, optional

count xs:nonNegativeInteger, mandatory assemblyName xs:string, mandatory

modeLegislative xs:string, mandatory modeExecutive xs:string, mandatory clearanceManaging optional

version: optional, two or three part version numbers, e.g. 1.0 up to 99.99, or 1.0.1 up to 99.99.99

dir: xs:string, generic type for more constrained direction statements: enumeration up, down, unknown; derived from tLaxDirection; optional

id: xs:ID, required a string, starting with a letter (a..zA..Z) or an underscore (_), followed by a non-colonized and non-spaced string consisting of letters

type: union of (restriction of xs:string, tOtherEnumerationValue); tOtherEnumerationValue is an arbitrary string starting with 'other:' followed by at

pos: tLengthM (xs:decimal, 6 fraction digits, length value measured in meter); required; must be greater than or equal to zero, less than or equal to the

ocpStationRef xs:IDREF, optional controllerRef xs:IDREF, optional trackContinueCourse optional trackContinueRadius optional normalPosition optional model

pos: tLengthM (xs:decimal, 6 fraction digits, length value measured in meter); required; must be greater than or equal to zero, less than or equal to the

value xs:decimal, 3 fraction digits, weight value measured in metric tons; mandatory meterload xs:decimal, generic type for load per meter values measured

trainCategory xs:string, optional status xs:string, optional vMax tSpeedKmPerHour: xs:decimal, 5 digits and 1 fraction digit with minimum value 0, speed

This template displays constraints to selected attributes analogously to Template:InheritIdName. nocode: Suppress code constraints if nocode=1 nolang:

brakeType: xs:rf-enumeration, mandatory airBrakeApplicationPosition: xs:rf-enumeration, optional regularBrakeMass: xs:decimal, 3 fraction digits, weight

adjustable to different needs, the template is often employed. It is related to and based on Template:Enum. The template has two optional arguments: notes_en

to chapter Semantic constraints. This template is called automatically by Template:ElementDocu, if the argument semcon of Template:ElementDocu exists.

This template standardizes the declaration of constraints. It became necessary to process the default values. The template has 4 unnamed Parameters and

nolang: suppress @lang This template depends on Template:InheritId, Template:Attr, Template:AddAnn, Template:InheritLang and Template:InheritAnyAttribute. There

on length The template depends on Template:InheritOcpRef, Template:InheritCourse, Template:Attr and Template:AddAnn. No other templates build on it. {

forget to hint at semantic constraints with template:semconHint! The template has two unnamed obligatory arguments: 1: The constraint. 2: The introduction date

This template standardizes Proposals for change referring to the wiki itself – not to railML®! The proposals will be listed in the maintenance category

notes_de: a German comment The template depends on Template:Attr, Template:Enum, Template:OtherEnum and Template:AddAnn. Template:InheritSwitchCrossing builds

This template is supposed to collect attribute defaults via Extension:Cargo. It gets called in template:constraint. This template defines the table "Defaults"

This template is supposed to collect information on Semantic Constraints. It is called by Template:Semcon. Die Darstellung wird durch template:semconDisplay

Template for linking semantic constraints by their number. Provisorily, also the element page must be stated as a second argument. 1: The semcon number

Please, employ Template:Ticket. commit: a list of related svn commits. Please, employ template:commit, or, for vintage tickets, Template:SVN. example: An

This template is used in the background for semantic constraints. It presents them in a standardized way. 1: The constraint. 2: Some organisatorial info

Category:Semantic constraints proposed. Please, don't forget to hint at semantic constraints with template:semconHint! The template has two unnamed obligatory arguments

Category:Semantic constraints. For proposed semantic constraints use Template:SemconProposal. Please, don't forget to hint at semantic constraints with template:semconHint

Category:Semantic constraints deprecated. For proposed semantic constraints use Template:Semcon with status=proposed. Please, don't forget to hint at semantic constraints

Depicts a semantic constraint that refers to all elements calling Template:InheritIdName none {{LangSemcon}} delivers

Template for semantic constraints of <stopDescription> None {{StopDescription}} produces The following table summarises the semantical constraints between

This template depicts a semantic constraint. None Uses template:note {{StartEndCon}} delivers {{StartEndCon|See also https://wiki2.railml.org/wiki/Dev

This template depicts a semantic constraint. None Uses template:note {{StartEndConNoOverlap}} delivers {{StartEndConNoOverlap|Additional Comment}} delivers

This template depicts a semantic constraint. None Uses template:note {{StartEndConWithContext|FocusElement|Container|Additional Comment}} delivers {{S

IS:routes   Parent: <infrastructure> Children: <route> [0..1] Container to define routes within the infrastructure. None None Not yet described. / Noch