Skip to content

Extended dated vehicle journey+replace pr368 and pr411#518

Closed
Aurige wants to merge 6 commits into
TransmodelEcosystem:nextfrom
Aurige:Extended-DatedVehicleJourney+Replace-PR368
Closed

Extended dated vehicle journey+replace pr368 and pr411#518
Aurige wants to merge 6 commits into
TransmodelEcosystem:nextfrom
Aurige:Extended-DatedVehicleJourney+Replace-PR368

Conversation

@Aurige
Copy link
Copy Markdown
Contributor

@Aurige Aurige commented Oct 6, 2023

Update of the Pr411 (that was merged and rolled back due to issues with examples uising UIC periods).
This new version integrates the decisions from the Meeting #13 on October 5th:

  • Update of examples to use OperatingDayRef in dated jouneys (keep the old UIC periods commented with an explicit mention of the deprecation).
  • UicOperatingPeriod deletion is now replaced by a simple deprecation (clearly stated in comments) for backward compatibility reasons.

Update of examples to use OperatingDayRef in dated jouneys (keep the old UIC Periods commented with an explicit mention of the deprecation).
UicOperatingPeriod deletion is now replaced by a simple deprecation (clearly stated in comments) for backward compatibility reasons.
@Aurige Aurige changed the base branch from master to next October 6, 2023 14:59
@skinkie
Copy link
Copy Markdown
Contributor

skinkie commented Oct 6, 2023

@Aurige you make a reference to an OperatingDay, is this defined in the file?

@Aurige
Copy link
Copy Markdown
Contributor Author

Aurige commented Oct 6, 2023

@Aurige you make a reference to an OperatingDay, is this defined in the file?

no, it is most likely that OpertatingDays can be shared across multiple such files and therefore exchanged separately in a calendar frame.

@skinkie
Copy link
Copy Markdown
Contributor

skinkie commented Oct 6, 2023

Lets not go into the direction that we share examples that do not validate on their own.

@Aurige
Copy link
Copy Markdown
Contributor Author

Aurige commented Oct 6, 2023

Lets not go into the direction that we share examples that do not validate on their own.

I checked validation with XML Spy (and external Ref are OK ...)

<LuggageCarriageFacilityList>cyclesAllowedWithReservation</LuggageCarriageFacilityList>
</ServiceFacilitySet>
</facilities>
<OperatingDayRef ref="tap:OperatingDay:2009-03-21"/>
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.

This is not an external ref, and is missing a version.

Aurige added 2 commits October 9, 2023 09:57
Addition of VersionRef to OperatingDayRef in order to clearly state that they refer to OperatingDay defined in another dataset
</ServiceFacilitySet>
</facilities>
<OperatingDayRef ref="tap:OperatingDay:2009-03-21"/>
<OperatingDayRef ref="tap:OperatingDay:2009-03-21" versionRef="1"/> <!-- reference to an OperationalDay defined in another dataset -->
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.

Just no. There is no reason not to include it in this example.

Copy link
Copy Markdown
Contributor

@EU-Agency-for-Railways EU-Agency-for-Railways left a comment

Choose a reason for hiding this comment

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

I reviewed the changes on the examples and the restriction to one operational day makes them useless for the purpose to explain the usage of NeTEx to replace the existing EDIFACT messages for the timetable data exchange for rail. Rail timetables are usually not planned for a specific operation day. So there is always a validity period plus a bitmask explaining the operating days. I would suggest to redraft the examples with a more suitable element (e.g. ServiceJourney).

@Aurige
Copy link
Copy Markdown
Contributor Author

Aurige commented Oct 12, 2023

thanks @EU-Agency-for-Railways
I agreed that the best way to go is to rework these examples and built new cleaner ones using ServiceJourney
This raised a few questions:

  • What do we do with the current examples ? do we just temporary drop them or deprecate them, waiting for the new version ?
  • Who can contribute to building new examples ? It's quite lot of examples to update (15 examples, some being quite long)... expect probably a few days to fully redesign and rebuilt them.

Also I would like to separate the XSD from the XML example updates, so it this is Ok for you, I'm going to remove the examples from this PR and create a new separate one for their update.

Reverting changes on UIC&ERA Examples
A dedicated PR/Issue willl be created for these examples
…ttps://github.com/Aurige/NeTEx into Extended-DatedVehicleJourney+Replace-PR368"

This reverts commit c99cf02, reversing
changes made to e1f6372.
@Aurige
Copy link
Copy Markdown
Contributor Author

Aurige commented Oct 13, 2023

@skinkie I reverted all changes to examples but had issues with other commits that were automatically brought back by Github and that were also modifying and breaking this PR... I had to revert it, but now it's a total mess ... I'm not sure what happened, but I'm afraid that I need to recreate this PR once more !!

@skinkie
Copy link
Copy Markdown
Contributor

skinkie commented Oct 13, 2023

@Aurige if you have a lot of free time, I have more interesting things to discuss ;-)

@Aurige
Copy link
Copy Markdown
Contributor Author

Aurige commented Oct 13, 2023

replaced by #520

@Aurige Aurige closed this Oct 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants