Aligning BookingArrangements more closely with NeTEx

[ue71603]

kept the Extension

Perhaps we need to outsource this to a NeTEx_include at some time. But perhaps we should sort ENUM in NeTEx first.

Fixes: #224

[ue71603]

will do all example, when content is ok for group.

[Aurige]

Well aligned with NeTEx ... just a few comments

[trurlurl]

Documentation done - except for MultilingualString which I don't fully understand. Will MultilingualString remain in FareSupport or move to Common? Why not use InternationalText?

[Aurige]

@ue71603 what are you expecting from me here ?

[ue71603]

@Aurige If you think something needs to be dealt with within NeTEx, then I would ask you to crate an issue there. And then I can finalise things here.

[Aurige]

There are some xsd: instaed of xs: ... does not validate like this (in XMLSpy)

[Aurige]

I did a few corrections, but this version is perfectly aligned with NeTEx now .... no further need on my side.

[trurlurl]

Added documentation proposal for MultilingualString that was missing (as mentioned above).

[ue71603]

Documentation done - except for MultilingualString which I don't fully understand. Will MultilingualString remain in FareSupport or move to Common? Why not use InternationalText?

What we really have is:

<xs:complexType name="InternationalTextStructure">
xs:annotation
xs:documentation[a restricted view of ALTERNATIVE NAME in TMv6] alternative identified text to be used in specified languages.</xs:documentation>
</xs:annotation>
xs:sequence
<xs:element name="Text" type="siri:NaturalLanguageStringStructure" maxOccurs="unbounded">
xs:annotation
xs:documentationText content.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TextId" type="xs:NMTOKEN" minOccurs="0">
xs:annotation
xs:documentationId of this text. May be used for matching to pre-recorded audio files.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>

And

<xsd:complexType name="NaturalLanguageStringStructure">
xsd:annotation
xsd:documentationTyoe for a string in a specified language.</xsd:documentation>
</xsd:annotation>
xsd:simpleContent
<xsd:extension base="PopulatedStringType">
<xsd:attribute ref="xml:lang" use="optional"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>

@Aurige @skinkie If you think I should do it, I change to InternationalTextStructure. I guess this saves us one new element.

[Aurige]

Yes InternationalTextStructure looks Ok here (even if internationalisation is not harmonized across SIRI, NeTEx and OJP)

[AndreasAtSBB]

Do we need Fax? What happens or breaks if we let it away.
As i now fax really used these days.

[skinkie]

The media exists...

[AndreasAtSBB]

Changes approved.