Service Interface for Real-Time Information (SIRI)

Assessment

• Open License Yes

• Transferable to Other Jurisdictions Yes

  Facilitation of adoption across jurisdiction is unclear because the protocol is intended to exchange information at the operator to operator level. However, SIRI's modularisation permits users to pick and choose the services they wish to implement. SIRI can be used with GTFS static data, referring to the same unique stopIDs

• Stakeholder Participation Yes

  Primary stakeholders of the SIRI protocol are defined as the purchasers and suppliers/product developers of public information transport systems. Contributors to the standard included equipment suppliers, transport authorities, transport operators, transport consultants from countries in the EU, public transit agencies in Germany, France, and the UK, and the EU Trident project

• Consensus-Based Governance No

  CEN Working Group manages the standard's governance. The group decides on changes made to the standard

• Extensions Yes

  Official documentation cites that SIRI is an extensible standard. Publishers expect additional services will be added to the standard in the future

• Human Readable Yes

  Standard utilizes universally understood tags and semantics. Clear documentation of field IDs as a reference

• Machine Readable Yes

  Siri uses XML to define messages using real-time public transport vehicle or journey time data. The schema is encoded as a W3C .xsd. Has reusable sub schemas and type packages. Schema uses the SOAP protocol to exchange messages between servers.

• Requires Up-To-Date / Real-Time Data Yes

  The protocol is able to handle real time transit schedule data

• Metadata Yes

  There is a metadata section to the XML schema