Replies: 3 comments 2 replies
-
|
Comment from @thbar: this is a good start and could be extended to a Glossary for the entire Transmodel ecosystem that could be a stand-alone source of truth (repository in this organisation) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Comment from @atibaut, other categories of documents should be added:
|
Beta Was this translation helpful? Give feedback.
2 replies
-
|
As of 5 May 2026, consensus for the categories of documents with the 3 as a starting point. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This is a proposal for us to clarify the names of the types of NeTEx documentation. The aim is to make sure that we agree on the content and purpose of each type. Also, it woud facilitate the dissemination in the future.
Profile: Any techincal documentation of NeTEx that is considered as a subset of NeTEx. Its objective is to facilitate the data exchange between stakeholders.
Example: EPIP, EPIAP, EFIP, Nordic Profile, Dutch Profile, French Profile
Technical guide: Any technical documentation that supports either the modelling of a functional part of NeTEx (e.g., stop places, timetables, fares, etc.), a category of public transport (e.g., alternatives modes of operation, flexible services, long-distance rail, etc.), or the needs of a specific category of stakeholders (e.g., data producers, data consumers, etc.).
Example: How to model multimodal stop places, Long-distance rail in NeTex, Quickstart for software developpers in NAP
General guide: Any non-technical documentation that supports the better understanding of NeTEx and its ecosystem.
Example: Why NeTEx?, NeTEx help guide for regulation authorities, FAQ, Glossary (or Ontology)
Beta Was this translation helpful? Give feedback.
All reactions