| Problems with changed schemaLocation (http -> https) for Dublin-Core schema [message #2428] |
Tue, 05 May 2020 13:30  |
Christian Rößiger
Messages: 63
Registered: March 2015
|
Member |
|
|
Hello,
The railml-schema integrates the definitions of the Dublin Core (DC)
metadata using xs:import at various points. In a recent attempt to
validate a railML file, I had problems with exactly this imported
schema. After some research I found out that the cause of the problem
seems to be the change of the URL for the DC files from http:// to
https://. Calling the (old) http-URL with a web browser still works,
because the DC server apparently answers with a http redirect response
code (308?) and the new address, which the browser processes
automatically. However, various XML parsers / developing tools
apparently have problems processing this response code and can no longer
validate railML files.
So I think that this problem should be solved by the developers of the
XML parser / development software first, but I would still be interested
to know if other parsers have similar problems and if therefore a
subsequent adaptation of the DC-URL in the already published railML-XSD
files is an option to reduce problems with the railML validation.
Best regards
Christian Rößiger
--
iRFP e. K. · Institut für Regional- und Fernverkehrsplanung
Hochschulstr. 45, 01069 Dresden
Tel. +49 351 4706819 · Fax. +49 351 4768190 · www.irfp.de
Registergericht: Amtsgericht Dresden, HRA 9347
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Problems with HTTPS for Dublin Core schema solved [message #2465 is a reply to message #2428] |
Mon, 22 June 2020 11:18  |
Vasco Paul Kolmorgen
Messages: 61
Registered: November 2004
|
Member |
|
|
Dear all,
I contacted the governance and IT team of the DCMI (Dublin Core Metadata
Initiative; see https://www.dublincore.org/) regarding this issue.
Am 05.05.2020 um 13:30 schrieb Christian Rößiger:
> After some research I found out that the cause of the problem
> seems to be the change of the URL for the DC files from http:// to
> https://. Calling the (old) http-URL with a web browser still works,
> because the DC server apparently answers with a http redirect response
> code (308?) and the new address, which the browser processes
> automatically. However, various XML parsers / developing tools
Please find the answer of DCMI:
Am 21.06.2020 um 16:15 schrieb Paul Walk:
> I have managed to disable the global automatic redirect from HTTP to HTTPS that was configured by default in the dublincore.org kubernetes ingress controller. This means that for most URLs in the 'dublincore.org' domain, both the HTTP and the HTTPS equivalents should work.
>
> There are still many redirects configured throughout the website - this reflects the fact that site has been in continuous development and deployment for ~25 years and has been migrated between hosts several times during that period.
>
> I am still a little unclear if it was the *redirects* which were causing the problems for the tools you mentioned, or if it was that they were unable to handle SSL?
>
> In any case, I believe that this change should address the immediate problem that you raised.
I hope this will solve the problem for the old versions, for all new
versions railML.org shall use HTTPS for sure.
Best regards,
--
Vasco Paul Kolmorgen - Governance Coordinator
railML.org (Registry of Associations: VR 5750)
Phone railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
|
|
Members
Search
Help
Login
Home
