Skip to content

the attribute in the relationshipStructure should not be id but name… - #1056

Open
ue71603 wants to merge 2 commits into
v2.1-wipfrom
fix-error-in-netex_relationship
Open

the attribute in the relationshipStructure should not be id but name…#1056
ue71603 wants to merge 2 commits into
v2.1-wipfrom
fix-error-in-netex_relationship

Conversation

@ue71603

@ue71603 ue71603 commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

in reality only name of classes are allowed and so the attribut can't be called id, but should be called nameOfClass.

as in most cases like nobody uses id, but if you do, then it must be a NameOfClass.

@ue71603 ue71603 added this to the netex_2.1 milestone Aug 5, 2026
@ue71603 ue71603 added the bug Technical mistake, inconsistency with the documentation, etc. label Aug 5, 2026
<xsd:documentation>Abstract Type for a serialisation of a NeTEx relationship.</xsd:documentation>
</xsd:annotation>
<xsd:attribute name="id" type="RelationshipId">
<xsd:attribute name="nameOfClass" type="RelationshipId">

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't think this is right.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is. have a look what RelationshipId really is.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is derived from NameOfClass.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RelationshipId isn't the right name... but you are right then.

@ue71603

ue71603 commented Aug 5, 2026

Copy link
Copy Markdown
Contributor Author

I try to change the name and we see if something breaks.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants