Home » railML newsgroups » railml.misc » Define requirements for processContent strictly than lax
Define requirements for processContent strictly than lax [message #2032] Fri, 07 December 2018 08:19 Go to next message
Heidrun Jost is currently offline  Heidrun Jost
Messages: 10
Registered: September 2006
Junior Member
Dear all,

Thales Germany use in railML's infrastructure schema and other schemes
the <any> element to extend the XML document with elements and attributes.

railML currently has defined: processContents="lax".

The meaning of strict and lax is the following:
- strict: the XML processor must obtain the schema for the required
namespaces and validate the elements (this is default)

- lax: same as strict but; if the schema cannot be obtained, no errors
will occur

To increase the usability, reliability and availability of railML data I
suggest to change the processContent from lax to strict.

Best regards,
--
Heidrun Jost
Software Engineer
Transportation Systems
Thales Deutschland

Phone: +49 (0) 30 688306 423
Email: heidrunjost(at)thalesgroupcom

Thales Deutschland GmbH
Schützenstr. 25 – 10117 Berlin – Germany
Re: Define requirements for processContent strictly than lax [message #2042 is a reply to message #2032] Tue, 18 December 2018 22:04 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 205
Registered: January 2016
Senior Member
Dear Heidrun,

Am 07.12.2018 um 08:19 schrieb Heidrun Jost:
> Dear all,
>
> Thales Germany use in railML's infrastructure schema and other schemes
> the <any> element to extend the XML document with elements and attributes.
>
> railML currently has defined: processContents="lax".
>
> The meaning of strict and lax is the following:
> -  strict: the XML processor must obtain the schema for the required
> namespaces and validate the elements (this is default)
>
> - lax: same as strict but; if the schema cannot be obtained, no errors
> will occur
>
> To increase the usability, reliability and availability of railML data I
> suggest to change the processContent from lax to strict.

following discussions at the last Conference in Prague and in several
working group meetings, railML.org decided to follow the suggested
approach of "strict" instead of "lax" extensions for upcoming versions
railML 3.x. This means, that all own extensions made to the railML
schema have to be specified by an appropriate extension schema file. It
shall not be possible to make use of (any) extensions to the railML
model without providing the schema of the extension.

Best regards
Christian

--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Previous Topic: Consolidated Use Cases List
Next Topic: SI units in railML 3.x
Goto Forum:
  


Current Time: Mon Feb 18 01:59:02 CET 2019