Open ue71603 opened 11 months ago
I am open to it, but a JSON implementation would be defined by a JSON Schema and not a XSD. So we should think about creating a JSON Schema.
I am open to it, but a JSON implementation would be defined by a JSON Schema and not a XSD. So we should think about creating a JSON Schema.
That is already done by undersigned for OSDM. An automatic process is still something that may be interesting.
The wrapping was not done in SIRI either. So, we would break it there.
For OJP about 150 cases need to be addressed:
C:\Users\ue71603\MG_Daten\github\OJP4\OJP\OJP_Availability.xsd
(Ln 26, Char 64)
@Aurige : What do you think?
We will do this, when Siri has done before.
In NeTEx 0:n or 1:n are usually wrapped in an element. This is not done in SIRI and OJP.
Perhaps they should be. This would make a conversion to JSON a lot easier:
For possible JSON implementation having groups around everything that can exist n times would be great. Currently ServiceSection is just 1:n
We have about 40-50 instances in OJP. Should we do it? We have some, where we did it.