Skip to content
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

PassengerStopAssignment table in document does not align with XSD #661

Closed
skinkie opened this issue Feb 9, 2024 · 1 comment
Closed
Assignees
Labels
bug Technical mistake, inconsistency with the documentation, etc. document has been updated NeTEx Document already updated UML update needed Update UML physical model needed
Milestone

Comments

@skinkie
Copy link
Contributor

skinkie commented Feb 9, 2024

image

Notice that the documentation makes the StopPlaceRef or StopPlace mandatory, while it is not in the XSD. Please propose what needs to be changed. QuayRef may be enough, since a Quay itself can only be under a single StopPlace. But we had a discussion on that too, since QuayRef still exists...

        <xsd:group name="PassengerStopAssignmentGroup">
                <xsd:annotation>
                        <xsd:documentation>Elements for a PASSENGER STOP ASSIGNMENT.</xsd:documentation>
                </xsd:annotation>
                <xsd:sequence>
                        <xsd:choice minOccurs="0">
                                <xsd:annotation>
                                        <xsd:documentation>STOP PLACE to which SCHEDULED STOP POINT is to be  assigned.</xsd:documentation>
                                </xsd:annotation>
                                <xsd:element ref="StopPlaceRef"/>
                                <xsd:element ref="StopPlace"/>
                        </xsd:choice>
                        <xsd:choice minOccurs="0"> 
                                <xsd:annotation>
                                        <xsd:documentation>QUAY to which SCHEDULED STOP POINT is to be assigned.</xsd:documentation>
                                </xsd:annotation>
                                <xsd:element ref="QuayRef"/>
                                <xsd:element ref="Quay"/>
                        </xsd:choice>
                        <xsd:choice minOccurs="0">
                                <xsd:annotation>
                                        <xsd:documentation>BOARDING POSITION to which SCHEDULED STOP POINT is to be  assigned.</xsd:documentation>
                                </xsd:annotation>
                                <xsd:element ref="BoardingPositionRef"/>
                                <xsd:element ref="BoardingPosition"/>
                        </xsd:choice>
                        <xsd:element name="trainElements" minOccurs="0">
                                <xsd:annotation>
                                        <xsd:documentation>Train elements to which SCHEDULED STOP POINT is to be assigned.</xsd:documentation>
                                </xsd:annotation>
                                <xsd:complexType>
                                        <xsd:complexContent>
                                                <xsd:extension base="trainStopAssignments_RelStructure"/> 
                                        </xsd:complexContent>
                                </xsd:complexType>
                        </xsd:element>
                </xsd:sequence>
        </xsd:group>
@skinkie skinkie added bug Technical mistake, inconsistency with the documentation, etc. to be discussed group_decision_needed labels Feb 9, 2024
@Aurige Aurige added the needs documentation update The NeTEx document needs to be updated label Feb 22, 2024
@Aurige
Copy link
Contributor

Aurige commented Feb 22, 2024

Update the documentation accordingly (SP or Q of BP mandatory) + XSD ANNOTATION

@ue71603 ue71603 added this to the netex_2.0 milestone Apr 15, 2024
@ue71603 ue71603 assigned trurlurl and unassigned ue71603 Apr 17, 2024
@trurlurl trurlurl added document has been updated NeTEx Document already updated and removed only_docs_left labels May 29, 2024
@trurlurl trurlurl added the UML update needed Update UML physical model needed label May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Technical mistake, inconsistency with the documentation, etc. document has been updated NeTEx Document already updated UML update needed Update UML physical model needed
Projects
None yet
Development

No branches or pull requests

6 participants