Dev:Semantic Constraints: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(Created page with "'''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 XS...")
 
No edit summary
Line 5: Line 5:
Semantic constraints are even important as XSD constraints. If they are ignored, security issues may arise.
Semantic constraints are even important as XSD constraints. If they are ignored, security issues may arise.


Elements with semantic constraints are listed in [[:Category:Semantic constraint]]. On the element documentation pages the semantic constraints can be found in a dedicated chapter below the syntactic constraints.
Elements with 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.


Every application of {{rml}} has to be checked not only on XML conformity but also on obediance of the semantic constraints.
Every application of {{rml}} has to be checked not only on XML conformity but also on obediance of the semantic constraints.

Revision as of 17:11, 25 October 2018

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 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.

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