In continuation of Pull Request #194, an open discussion has risen about this specific part in SIRI-CA introduced in the PR. The question is about authorizing a choice in the XSD of SIRI-CA.
As of today, the choice reflect different implementations. Parties can either:
- change points (move one or several points),
- create a full new link
This is the extract from the XSD:
<xsd:choice>
<xsd:element name="ChangedPoints" type="ChangedPoints">
<xsd:annotation>
<xsd:documentation>List of modified points</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="UpdatedServiceLinks" type="ServiceLinkViewsStructure">
<xsd:annotation>
<xsd:documentation>List of SERVICE LINKs having updated shapes in that journey. This is only to provide updated the shapes of the journey (as gml:linestring), not to provide additional SERVICE LINK (provided through the sequence of CALLS)</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
So, the question is: should the choice be removed and only one path chosen?
In continuation of Pull Request #194, an open discussion has risen about this specific part in SIRI-CA introduced in the PR. The question is about authorizing a
choicein the XSD of SIRI-CA.As of today, the choice reflect different implementations. Parties can either:
This is the extract from the XSD:
So, the question is: should the choice be removed and only one path chosen?