Home

What is SIRI?

• The Standard Interface for Real-time Information describes how an interface, for example a REST API for exchange of SIRI messages over HTTP, must be implemented.
• How does the subscription mechanism work?
• What data must be transmitted per use case, e.g. delay of a vehicle, cancellation of a journey or a situation (accident) at a certain stop that affects passengers?

Formatting of Code / XML indentation

• SIRI schemas must be valid XSD files and have certain indentation.
• SIRI schemas must validate the standard SIRI examples (that include all functional services).
• SIRI elements, structures and types must follow certain naming conventions. Take also into account the Transmodel and NeTEx terminology.
• SIRI structures should be as flat as possible (no unnecessary nesting) and as complex as needed.

Examples:

• If a message usually contains multiple elements (of the same substructure), for example more than two EstimatedCalls, encapsulate them in a list.
• If a message usually contains a single element (of a certain substructure), but an arbitrary number is possible, then only set maxOccurs="unbounded" (and don't nest it further). An example is DepartureStopAssignment.

Process of Changes

• I want to contribute to the SIRI standard and change/extend the schema. Where do I start and how should I proceed?
• Is a pull request sufficient or do I also need to submit a change request in the form of the official template?