Raw work for v2.0 changelog (temporary branch)

[thbar]

Working on a commit-per-commit basis to create the changelog is too challenging (at least with my current history). It involves 457 commits dating back to late 2020 (v1.3.1...next).

I'm creating this temporary branch & PR so that we can work collaboratively on the changelog.

What I've done:

• create individual diff-files (in todo, moved to processed once they are incorporated into the "raw changelog"), so that the work is versioned temporarily, and the GitHub UI is able to show files changes properly)
• review them gradually (& move them to processed once done)

Sharing it will make it easier to spread the load across us, and make it auditable.

EDIT:

• I've included only the files which have changed, in theory.
• Content is in this folder: https://github.com/NeTEx-CEN/NeTEx/tree/v2.0-changelog-tmp-work/diff-v1.3.1-next
• Ultimately we will have global remarks (e.g. ids are mandatory on X, Y, Z) but since I do not have a global view on all the changes, going through each file is "easier" & more solid.

[thbar]

Using AI + manual work locally, a basic changelog proposal (to be reworked) is:

Summary of impactful documented changes:

• Many version schemas now enforce stricter validation semantics: mandatory id/ref/version attributes were introduced or tightened in numerous object/ref structures.
• Key/unique/keyref definitions were expanded or renamed across frames and domain modules; reference integrity checks are broader and stricter in v2.0 validation contexts.
• Several constraints were reshaped (including removal of @order from some keys and selective cardinality/type adjustments), which can change pass/fail outcomes for existing XML instances.
• Publication-level schemas add or adjust integrity scopes (for example around Contract and FarePriceFrame) and align naming of site/path navigation key sets.
• Functional evolution is mostly additive, but existing datasets should be revalidated because compatibility now depends more on explicit identifiers and coherent cross-references.

@TuThoThai @skinkie @ue71603 is that a sound basis, or not that much, in your opinion?

[thbar]

Discussed with @TuThoThai:

• @TuThoThai will provide more important functional changes to highlight
• we will add guidance on how to validate locally with either v1.3.1 or v2.0.0 using xmllint or other tools
• we will encourage people to open issues with question label ; ultimately, one of the best guidances is the XSD validation

[TuThoThai]

Some functional changes to add to the changelog:

• addition of DECK PLAN and all related elements
• addition of languages attributes when using MultilingualString to handle translations of names, instead of using AlternativeName
• creation of privateCodes allowing several PrivateCode for the same element (e.g., ticketing, scheduling, etc.)
• changes to BookingArrangement and its use for flexible services, including relation to ServiceJourneyPattern
• addition of a relation between Facilities and Line
• clarification of abstracts elements
• addition and/or correction of values in enumerations (e.g., MedicalFacility, PassengerCommsFacility, SameZone, QuayType, PurchaseMoment, etc.)
• addition of enumerations such as PropulsionTypes, FuelTypes
• deprecation marking for several elements such as Order, PrivateCode, FlexibleLine, BaselineVersionRef, ExternalOperatorRef, PropulsionType, FuelType