| Define requirements for processContent strictly than lax [message #2032] |
Fri, 07 December 2018 08:19  |
Heidrun Jost
Messages: 25
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
|
|
|
|
Members
Search
Help
Login
Home
