Learnings from French profile in MD

[ue71603]

Link: https://github.com/etalab/transport-profil-netex-fr/tree/v2.4/

• a folder per chapter
• tables as html
• tables not always optimsed
• no numbering
• no links
• choices break tables

[trurlurl]

Having had a look at the profile France...

WHAT I LIKE and would suggest considering whether to replicate for the Swiss profile:

• Yellow highlighting of what is additional / particular / requires special attention
• Modularity - separate documents: éléments communs, arrêts, réseaux, horaires, accessibilité
• Unused elements and structures not shown

What I don't like:

• Didn't see any clear guidelines / expectations regarding the non-required elements
• Majority of tables are html - how is maintainability solved?

QUESTION
In addition to required, would it make sense to further categorise elements as either recommended / expected, optional, not permitted (and, perhaps: planned, deprecated)?

IDEA
For each table a link to a XML code example in GitHub that can be used as a template. Useful for:

• copy/paste
• One has the complete picture with all elements - i.e., inheritance from abstract classes and groups have been included.
• The example files are automatically validated...
  • so the code is guaranteed to be valid;
  • when upgrading to a new version of NeTEx in the future, we'd see if our profile remains valid;
  • or, when working on NeTEx, this would help ensuring that the profile remains in sync.

[ue71603]

@trurlurl Can you make a list of stuff that you think we differ from the French profile? This i also something for Adrian to study.