Skip to content

Replaced hypens (-) with commas :-) #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
atibaut wants to merge 1 commit into
base: v0
Choose a base branch
from
Open

Replaced hypens (-) with commas :-) #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,8 @@
To work on guides and documentation for NeTEx

# Vision for the guides
Any developer should be able to exchange standardised route and fare data for public transport – without first having to become an expert in Transmodel or NeTEx.
Any developer should be able to exchange standardised route and fare data for public transport, without first having to become an expert in Transmodel or NeTEx.

The guides shall bridge the gap between the complex NeTEx standard and the practical everyday reality of developers. By offering use-case-driven, domain-specific guides, we ensure that all stakeholders model data consistently, use the same building blocks, and populate the same fields in the same way – regardless of whether they are working with bus routes, flexible transport, or train lines requiring booking.
The guides shall bridge the gap between the complex NeTEx standard and the practical everyday reality of developers. By offering use-case-driven, domain-specific guides, we ensure that all stakeholders model data consistently, use the same building blocks, and populate the same fields in the same way, regardless of whether they are working with bus routes, flexible transport, or train lines requiring booking.

The result is an ecosystem where route data flows seamlessly between systems and stakeholders, where the onboarding threshold is low, and where the quality of exchanged data is high – because everyone follows a single, shared recipe tailored to their use case.
The result is an ecosystem where route data flows seamlessly between systems and stakeholders, where the onboarding threshold is low, and where the quality of exchanged data is high because everyone follows a single, shared recipe tailored to their use case.
Loading