nick-knowles / netex-xml Goto Github PK

Direction object is not allowed in a GeneralFrame tag; can refers it by element but adding a Direction in tag causes Xerces error :

cvc-complex-type.2.4.a: Invalid content was found starting with element '{"http://www.netex.org.uk/netex":Direction}'. One of '{"http://www.netex.org.uk/netex":GeneralFrameMember, "http://www.netex.org.uk/netex":DataManagedObject, "http://www.netex.org.uk/netex":Entity_Entity}' is expected.

See the netex_facilityUic_support-v1.0.xsd enumeration UicProductCharacteristicEnumeration value allIInclusivePrice should be allInclusivePrice

Unlike the Call and datedPassingTimes model the ServiceJourney lacks the ability to define a DayOffset. Is this something missing in the standard, or how should it be modelled instead?

https://github.com/nick-knowles/NeTEx-XML/blob/master/schema/1.03/xsd/netex_part_2/part2_journeyTimes/netex_serviceJourney_version-v1.0.xsd#L223

Use case: I want to communicate a trip operating from 24:00:01 to 24:30:00 on the previous operating day.

As requested to Christophe Duquesne the current GPLv3 suggests that software build from the XSD files (for example derivative code generated from the XSDs) will fall under the GPLv3, thus any AVL system supporting NeTEx will be GPLv3.

Our suggestion would be to relicense the XSDs as LGPLv3. https://www.gnu.org/licenses/lgpl.html

One part of the NeTEx specification are useful definitions of specific terms within the NeTEx context. The European ISA² initiative supports European organizations to become more interoperable, and promotes the use of Linked Data and the Resource Description Format (RDF) for raising the semantic interoperability.

Making NeTEx available for use within Linked Data technologies is straightforward: a base URI needs to be added to every term. Then, when visiting this URI in the browser, an RDF representation needs to be returned, describing the term this URI identifies.

An example of other Linked Data vocabularies in the transport domain:

• http://vocab.gtfs.org
• http://vocab.datex.org
• http://semweb.mmlab.be/ns/linkedconnections

Would you be interested in doing this as part of this repository?

I notice that the examples of tap_tsi contain a huge set of SalesPackages. But none of them actually show what the fare is to acquire this SalesPackage (discount) itself. I would expect something like a FareProductPrice.

Is this the correct route?
FareTable > pricesFor > SalesPackage which has cells with Amount in it.

One of the things that currently seem to lack in the xml schema is the validation of the semantics of a NeTEx document. What I mean here is that a certain object types may refer to another (strict) object type which should fail in the XSD validation, when incorrect. An example of such reference can be found below.

The PointProjectionRef refers to a RoutePoint, there isn't any logic that nameOfRefClass would limit the reference made from this entity to the foreign entity. One would expect that the nameOfRefClass should be defined in the scope of this object. Hence a PointProjectionRef must only refer to object of class of Point. xs:keyref should facilitate this effort. http://docstore.mik.ua/orelly/xml/schema/ch09_03.htm

Secondary the reference itself is not to be present in the document and/or to be unique. If we consider the parent type of all ObjectIds we end up with an xsd:normalizedString. This would lead to the use of xs:ID upon definition and xs:IDREF upon reference.
http://docstore.mik.ua/orelly/xml/schema/ch09_01.htm

The XML Source.

<PointProjectionRef nameOfRefClass="RoutePoint" ref="NDOV:RP:NL:Q:36002156"/>

And the XML Schema's:

    <xsd:simpleType name="PointProjectionIdType">
        <xsd:annotation>
            <xsd:documentation>Type for identifier of a POINT PROJECTION.</xsd:documentation>
        </xsd:annotation>
        <xsd:restriction base="ProjectionIdType"/>
    </xsd:simpleType>
    <xsd:element name="PointProjectionRef" type="PointProjectionRefStructure" substitutionGroup="ProjectionRef">
        <xsd:annotation>
            <xsd:documentation>Reference to a PROJECTION.</xsd:documentation>
        </xsd:annotation>
    </xsd:element>
    <xsd:complexType name="PointProjectionRefStructure">
        <xsd:annotation>
            <xsd:documentation>Type for a reference to a POINT PROJECTION.</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleContent>
            <xsd:restriction base="ProjectionRefStructure">
                <xsd:attribute name="ref" type="PointProjectionIdType" use="required">
                    <xsd:annotation>
                        <xsd:documentation>Identifier of a POINT PROJECTION.</xsd:documentation>
                    </xsd:annotation>
                </xsd:attribute>
            </xsd:restriction>
        </xsd:simpleContent>
    </xsd:complexType>

    <xsd:element name="VersionOfObjectRef" type="VersionOfObjectRefStructure">
        <xsd:annotation>
            <xsd:documentation>Reference to a NeTEx Object .  i.e. concrete instance of an ENTITY  may include a version. Implements a one to one relationship by reference.</xsd:documentation>
        </xsd:annotation>
    </xsd:element>
    <xsd:complexType name="VersionOfObjectRefStructure">
        <xsd:annotation>
            <xsd:documentation>Type for a versioned reference to a NeTEx Object.</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleContent>
            <xsd:extension base="ObjectIdType">
                <xsd:attribute name="nameOfRefClass" type="NameOfClass" use="optional">
                    <xsd:annotation>
                        <xsd:documentation>Name of Class of the referenced entity. Allows reflection. Fixed for each entity type.</xsd:documentation>
                    </xsd:annotation>
                </xsd:attribute>
                <xsd:attributeGroup ref="ReferenceModificationDetailsGroup"/>
                <xsd:attribute name="ref" type="ObjectIdType" use="required">
                    <xsd:annotation>
                        <xsd:documentation>Identifier of referenced entity.</xsd:documentation>
                    </xsd:annotation>
                </xsd:attribute>
            </xsd:extension>
        </xsd:simpleContent>
    </xsd:complexType>

    <xsd:simpleType name="ObjectIdType">
        <xsd:annotation>
            <xsd:documentation>Abstract Type for identifier of a NeTEx Object.</xsd:documentation>
        </xsd:annotation>
        <xsd:restriction base="xsd:normalizedString"/>
    </xsd:simpleType>

What is the design reason for Version/StartDate Version/EndDate being xs:dateTime?

<StartDate>2013-01-01T00:00:00Z</StartDate>
<EndDate>2013-03-31T00:00:00Z</EndDate>

https://github.com/nick-knowles/NeTEx-XML/blob/master/schema/1.03/xsd/netex_framework/netex_responsibility/netex_version_version-v1.0.xsd#L149

While other parts of the standard have defined StartDate/EndDate and FromDate/ToDate as xs:date.

https://github.com/nick-knowles/NeTEx-XML/blob/master/schema/1.03/xsd/netex_framework/netex_reusableComponents/netex_serviceCalendar_version-v1.0.xsd#L188

The latter is something I would like to see uniformly applied.

There is typo in RailSubmodeEnumeration netex_sub_mode_version-v1.0.xsd

<xsd:enumeration value="intermational"/>
should be international instead

Several operators use custom graphics specific to a line/direction. The Presentation object allows Color like properties. We would like to find an extension to support Icons. Either by base64 encoding or an URI refering to an external source.

A specific journey has two Authority's. Only one AuthorityRef is allowed, I would suggest to set maxOccurs as unbounded.

Quite a few examples do not validate with the current NeTEx XSD an example is Netex_CDL1_Bus_Zonal_MobileProducts.xml Could they be updated?

netex_service/netex_dataObjectRequest_service-v1.0.xsd:4: element import: Schemas parser warning : Element '{http://www.w3.org/2001/XMLSchema}import': Skipping import of schema located at 'siri/siri_requests-v2.0.xsd' for the namespace 'http://www.siri.org.uk/siri', since this namespace was already imported with the schema located at 'siri_utility/siri_participant-v2.0.xsd'.
Schemas parser error : element decl. '{http://www.netex.org.uk/netex}DataObjectRequest', attribute 'substitutionGroup': The QName value '{http://www.siri.org.uk/siri}AbstractFunctionalServiceRequest' does not resolve to a(n) element declaration.
netex_service/netex_dataObjectRequest_service-v1.0.xsd:87: element complexType: Schemas parser error : complex type 'DataObjectRequestStructure', attribute 'base': The QName value '{http://www.siri.org.uk/siri}AbstractFunctionalServiceRequestStructure' does not resolve to a(n) simple type definition.
netex_service/netex_dataObjectRequest_service-v1.0.xsd:95: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element', attribute 'ref': The QName value '{http://www.siri.org.uk/siri}Extensions' does not resolve to a(n) element declaration.
Schemas parser error : element decl. '{http://www.netex.org.uk/netex}DataObjectSubscriptionRequest', attribute 'substitutionGroup': The QName value '{http://www.siri.org.uk/siri}AbstractFunctionalServiceSubscriptionRequest' does not resolve to a(n) element declaration.
netex_service/netex_dataObjectRequest_service-v1.0.xsd:129: element complexType: Schemas parser error : complex type 'DataObjectSubscriptionStructure', attribute 'base': The QName value '{http://www.siri.org.uk/siri}AbstractSubscriptionStructure' does not resolve to a(n) simple type definition.
netex_service/netex_dataObjectRequest_service-v1.0.xsd:142: element element: Schemas parser error : Element '{http://www.w3.org/2001/XMLSchema}element', attribute 'ref': The QName value '{http://www.siri.org.uk/siri}Extensions' does not resolve to a(n) element declaration.
Schemas parser error : element decl. '{http://www.netex.org.uk/netex}DataObjectDelivery', attribute 'substitutionGroup': The QName value '{http://www.siri.org.uk/siri}AbstractFunctionalServiceDelivery' does not resolve to a(n) element declaration.
netex_service/netex_dataObjectRequest_service-v1.0.xsd:167: element complexType: Schemas parser error : complex type 'DataObjectDeliveryStructure', attribute 'base': The QName value '{http://www.siri.org.uk/siri}AbstractServiceDeliveryStructure' does not resolve to a(n) simple type definition.
netex_service/netex_dataObjectRequest_service-v1.0.xsd:184: element element: Schemas parser error : element decl. '{http://www.netex.org.uk/netex}DataObjectCapabilitiesRequest', attribute 'type': The QName value '{http://www.siri.org.uk/siri}ServiceCapabilitiesRequestStructure' does not resolve to a(n) type definition.
Schemas parser error : element decl. '{http://www.netex.org.uk/netex}DataObjectCapabilitiesRequest', attribute 'substitutionGroup': The QName value '{http://www.siri.org.uk/siri}AbstractFunctionalServiceCapabilitiesRequest' does not resolve to a(n) element declaration.
Schemas parser error : element decl. '{http://www.netex.org.uk/netex}DataObjectCapabilitiesResponse', attribute 'substitutionGroup': The QName value '{http://www.siri.org.uk/siri}AbstractFunctionalServiceCapabilitiesResponse' does not resolve to a(n) element declaration.
netex_service/netex_dataObjectRequest_service-v1.0.xsd:195: element complexType: Schemas parser error : complex type 'DataObjectCapabilitiesResponseStructure', attribute 'base': The QName value '{http://www.siri.org.uk/siri}AbstractServiceCapabilitiesResponseStructure' does not resolve to a(n) simple type definition.
netex_service/netex_dataObjectRequest_service-v1.0.xsd:206: element attribute: Schemas parser error : attribute decl. 'version', attribute 'type': The QName value '{http://www.siri.org.uk/siri}VersionString' does not resolve to a(n) simple type definition.
netex_service/netex_dataObjectRequest_service-v1.0.xsd:220: element complexType: Schemas parser error : complex type 'DataObjectServiceCapabilitiesStructure', attribute 'base': The QName value '{http://www.siri.org.uk/siri}AbstractCapabilitiesStructure' does not resolve to a(n) simple type definition.
netex_service/netex_dataObjectRequest_service-v1.0.xsd:279: element complexType: Schemas parser error : complex type 'DataObjectCapabilityRequestPolicyStructure', attribute 'base': The QName value '{http://www.siri.org.uk/siri}CapabilityRequestPolicyStructure' does not resolve to a(n) simple type definition.
netex_service/netex_dataObjectRequest_service-v1.0.xsd:317: element complexType: Schemas parser error : complex type 'DataObjectServicePermissionStructure', attribute 'base': The QName value '{http://www.siri.org.uk/siri}AbsoluteBearingType' does not resolve to a(n) simple type definition.
WXS schema NeTEx_publication.xsd failed to compile

And see here how: https://github.com/StichtingOpenGeo/NeTEx/commits/v1.01

<xsd:selector xpath=".//netex:ResponsibilityRoleAssignment/ResponsibleAreaRef"/>

This must be changed to:

<xsd:selector xpath=".//netex:ResponsibilityRoleAssignment/netex:ResponsibleAreaRef"/>

This will affect all files with xsd:selector's for key-ref validation.

An AccessibilityAssessment can be added as property of a Line. Is it possible to apply this property at ServiceJourney (and therefore vehicle) level?

Hallo!
I guess that it is a mistake in netex_fareProduct_version-v1.0.xsd (v1.04b) where SUPPLEMENT PRODUCT should be able to reference FARE PRODUCT to which it is a supplement (according to documentation) by means of SupplementToFareProductRef. However, in scheme it refers to FareProductPriceIdType, and not to the FareProductIdType (see bellow) as I would expect.

<xsd:group name="SupplementProductGroup">
	<xsd:annotation>
		<xsd:documentation>Elements for a PREASSIGNED FARE PRODUCT.</xsd:documentation>
	</xsd:annotation>
	<xsd:sequence>
		<xsd:element name="SupplementToFareProductRef" type="FareProductPriceIdType" minOccurs="0">
			<xsd:annotation>
				<xsd:documentation>FARE PRODUCT to which this is a sublement.</xsd:documentation>
			</xsd:annotation>
		</xsd:element>
	</xsd:sequence>
</xsd:group>