Difference between revisions of "Dev:Semantic Constraints"

From wiki.railML.org
Jump to: navigation, search
[checked revision][checked revision]
(Current Constraints: +weitere proposed)
(Current Constraints)
 
Line 14: Line 14:
 
If you see need for a ''semantic'' constraint beyond the schema, please discuss it in the {{site|https://www.railml.org/forum|forum}}. If there is consent, you may decide to add a proposal in the element documentation using [[Template:Semcon]]. Please, add the proposal to the list below! If the proposal is accepted, it will implemented in the wiki using [[Template:Semcon]].
 
If you see need for a ''semantic'' constraint beyond the schema, please discuss it in the {{site|https://www.railml.org/forum|forum}}. If there is consent, you may decide to add a proposal in the element documentation using [[Template:Semcon]]. Please, add the proposal to the list below! If the proposal is accepted, it will implemented in the wiki using [[Template:Semcon]].
 
==Current Constraints==
 
==Current Constraints==
{|class="wikitable sortable"
+
[[Dev:Semantic_Constraints/table|View/edit list on the separate source page]].
!Element
+
{{:Dev:Semantic_Constraints/table}}
!Proposal date
+
!Date of acception
+
|-
+
|{{TT:Tag|timetablePeriod}}
+
|2018-11-12
+
|2019-03-21
+
|-
+
|{{TT:Tag|specialService|operatingPeriodRef}}
+
|2018-11-12
+
|2019-03-21
+
|-
+
|{{TT:Tag|specialService|operatingPeriod}}
+
|2018-11-12
+
|2019-03-21
+
|-
+
|{{TT:Tag|operatingPeriodRef|trainPart}}
+
|2018-11-12
+
|2019-03-21
+
|-
+
|{{TT:Tag|operatingPeriod}}
+
|2018-11-12
+
|2019-03-21
+
|-
+
|{{TT:Tag|operatingDay}}
+
|2018-11-12
+
|2019-03-21
+
|-
+
|{{TT:Tag|ocpTT}} (first semantic constraint)
+
|2018-10-25
+
|
+
|-
+
|{{TT:Tag|ocpTT}} (second semantic constraint)
+
|2018-10-25
+
|
+
|-
+
|{{TT:Tag|circulation}}
+
|2018-11-12
+
|2019-03-21
+
|-
+
|{{TT:Tag|blockPart}}
+
|2018-11-12
+
|2019-03-21
+
|-
+
|{{RS:Tag|operator}}
+
|2018-11-12
+
|2019-03-21
+
|-
+
|{{IS:Tag|state}}
+
|2018-11-12
+
|2019-03-21
+
|-
+
|{{IS:Tag|state (with length)}}
+
|2018-11-12
+
|2019-03-21
+
|-
+
|{{IS:Tag|designator}}
+
|2018-11-12
+
|2019-03-21
+
|-
+
|{{IS:Tag|speedChange}}
+
|2019-04-11
+
|
+
|-
+
|{{TT:Tag|rostering}}
+
|2019-05-22
+
|
+
|-
+
|{{TT:Tag|stopDescription}}
+
|2018-09-03
+
|
+
|-
+
|{{TT:Tag|trackInfo}} (first semantic constraint)
+
|2018-08-21
+
|
+
|-
+
|{{TT:Tag|trackInfo}} (second semantic constraint)
+
|2018-08-21
+
|
+
|}
+
  
 
[[Category:GeneralDescription]]
 
[[Category:GeneralDescription]]

Latest revision as of 14:23, 9 July 2019

Semantic constraints

XSD offers a variety of possibilities to define constraints. However, in some rare exceptions it is not possible to express an important rule in XSD. Rules that do not fit into XSD have to be expressed by words, semantically.

Semantic constraints are even important as XSD constraints. If they are ignored, security issues may arise.

Elements with approved semantic constraints are listed in Category:Semantic constraints. On the element documentation pages, the semantic constraints can be found in a dedicated chapter below the syntactic constraints. Proposed semantic constraints are listed in Category:Semantic constraints_proposed. A list of the introduction date of a semantic constraint can be found in the list below.

Note.png Semantic constraints that have been proposed before the 10th of December 2018 shall be considered as approved until decided otherwise.


Every application of railML® has to be checked not only on XML conformity but also on the obedience of the semantic constraints.

How to introduce Semantic Constraints

Generally speaking, constraints should better be implemented syntactically in the schema. Please, follow the guideline for participating in the development process.

If you see need for a semantic constraint beyond the schema, please discuss it in the forum (link to the railML® website). If there is consent, you may decide to add a proposal in the element documentation using Template:Semcon. Please, add the proposal to the list below! If the proposal is accepted, it will implemented in the wiki using Template:Semcon.

Current Constraints

View/edit list on the separate source page.

Element ID Proposal date Date of acception Date of deprecation
<TT:timetablePeriod> TT:001 2018-11-12 2019-03-21
<TT:specialService> TT:001 2018-11-12 2019-03-21
<TT:specialService> TT:001 2018-11-12 2019-03-21
<TT:operatingPeriodRef> TT:001 2018-11-12 2019-03-21
<TT:operatingPeriod> TT:001 2018-11-12 2019-03-21
<TT:operatingDay> TT:001 2018-11-12 2019-03-21
<TT:ocpTT> (first semantic constraint) TT:002 2018-10-25 2019-06-20
<TT:ocpTT> (second semantic constraint) 2018-10-25 discarded
<TT:circulation> TT:001 2018-11-12 2019-03-21
<TT:blockPart> (first semantic constraint) TT:001 2018-11-12 2019-03-21
<TT:blockPart> (second semantic constraint) TT:003 2019-07-13
<TT:blockPart> (third semantic constraint) TT:004 2019-07-20
<RS:operator> TT:001 2018-11-12 2019-03-21
<IS:state> TT:001 2018-11-12 2019-03-21
<IS:state (with length)> TT:001 2018-11-12 2019-03-21
<IS:designator> TT:001 2018-11-12 2019-03-21
<IS:speedChange> IS:001 2019-04-11
<TT:rostering> TT:005 2019-05-22 2019-06-25
<TT:stopDescription> (first semantic constraint) TT:006 2018-09-03 2019-06-20
<TT:stopDescription> (second semantic constraint) TT:007 2019-06-19
<TT:trackInfo> (first semantic constraint) TT:008 2018-08-21 2019-06-20
<TT:trackInfo> (second semantic constraint) TT:009 2018-08-21 2019-06-20
<TT:times> (second semantic constraint) TT:010 2019-06-19
<IS:trackEnd> IS:002 2019-06-17
<IS:trackBegin> IS:003 2019-06-17
<IS:track> IS:004 2019-06-17
<IS:ocp> IS:005 2019-06-19
<IS:mileageChange> IS:006 2019-06-19