| Re: scheme location to be adressed via HTTPS instead of HTTP [message #2076 is a reply to message #2056] |
Mon, 07 January 2019 15:08  |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Thomas,
you are right. My example was poorly chosen: it must be 2018 instead of
2016. So, for railML 2.4, the following changes of the namespace and
schema location applied:
xmlns:rail="http://www.railml.org/schemas/2018"
has been replaced by
xmlns:rail="https://www.railml.org/schemas/2018"
and
targetNamespace="http://www.railml.org/schemas/2018"
has been replaced by
targetNamespace="https://www.railml.org/schemas/2018".
I corrected the Trac ticket #330 [1] accordingly.
[1] https://trac.railml.org/ticket/330
Best regards
Christian
Am 28.12.2018 um 18:01 schrieb Thomas Nygreen:
> Dear Christian,
>
> When this was changed, I assumed it was only from 2.4 and
> newer versions. Is the example above just poorly chosen, or
> have you indeed changed the namespaces for previous
> versions? I hope not, as this would create new namespaces
> separate from the ones used by all existing railML files up
> to and including version 2.3. There is no requirement that
> the namespace URI and schemaLocation should be identical.
> Hence, there is no reason to change http to https in the
> namespace.
>
> Best,
> Thomas
>
>
--
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
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
