-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change main namespace of OJP from SIRI to OJP #347
Conversation
@Aurige doesn't compile in OJP.xsd. Pls check why this is... |
We are back at the QName problem (which blocked the change last time, as far as I know): |
It looks Ok on my side ... what should I check ? |
It works, but I had to fix SIRI. Created an issue, because doing a PR would break a lot of things there: I suggest we work with it and do the PR in SIRI, if necessary. |
added to SIRI SIRI-CEN/SIRI#108 |
8dd6641
to
c230fe5
Compare
We did change the default namespace of TRIAS once, and got complaints because some clients were expecting them in a specific way and could not handle any other way. But a change with version 2.0 should be fine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We did change the default namespace of TRIAS once, and got complaints because some clients were expecting them in a specific way and could not handle any other way. But a change with version 2.0 should be fine.
For some reason, the main OJP namespace was "siri", and SIRI was included and OJP imported... This PR just put the things back in the proper order.
Following the proposal of namespace updated in OJP, as pointed by Matthias, this has consequences in all example. Having a look arround them, the use of namespace is a bit of a mess in OJP. Basically, headers should move to something like this in examples: <OJP xmlns="http://www.vdv.de/ojp" xmlns:ojp="http://www.vdv.de/ojp" xmlns:siri="http://www.siri.org.uk/siri" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.1-dev" xsi:schemaLocation="http://www.vdv.de/ojp ../../OJP.xsd"> But you can see that there is 2 different uses of "http://www.vdv.de/ojp" because the examples don't make a consistent use of the "ojp" prefix. Also, once "ojp" becomes the default namespace, then you need to use the "siri" one when you use somethnig from SIRI (that was kind of reverse up to now because SIRI wans made default. By the way, that's one of the good side of tools like XML Spy that prevent that kind of mistake when you use it yo create examples ;-)
fc82e03
to
16d6e17
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll push an improvement soon adding comments to the changed SIRI files
always use * schemaLocation="../ifopt/ifopt_allStopPlace.xsd" for import of namespace="http://www.ifopt.org.uk/ifopt" * schemaLocation="../acsb/acsb_all.xsd" for import of namespace="http://www.ifopt.org.uk/acsb" because several XML tools fail to validate the XSD if different files are defined to provide the same namespace Added comments at the changed locations to make the OJP changes to siri sources visible. There is a pull request in SIRI to fix this: SIRI-CEN/SIRI#108
https://github.com/VDVde/OJP/pull/339/files
but not in a different repository.