collection of electronically stored descriptive records or content units (including facts, full texts, pictures, and sound) with a common user interface and software for the etrieval and manipulation of the data

NOTE 1 to entry: The units or records are usually collected with a particular intent and are related to a defined topic. A database can be issued on CD-ROM, diskette, or other direct-access method, or as a computer file accessed through dial-up methods or through the Internet.

NOTE 2 to entry: Licensed databases are counted separately even if access to several licensed database products is effected through the same interface.

NOTE 3 to entry: A common interface providing access to a packet of serials or digital documents, usually offered by a publisher or vendor, is also to be counted as database. Additionally, the single serials or digital documents are counted as serials or digital documents.

the origin of operational data referring to one single responsibility. References to a data system are useful in an interoperated computer system

NOTE For SIRI, this entails in particular specific systems for assigning unique identifiers to relevant entities such as STOP POINTS or JOURNEYS, about which messages are to be exchanged, and which can be matched to the locally known entities identified by the respective internal operating data. The DATA SYSTEM must be mutually agreed between CLIENT and SERVER. A DATA SYSTEM has both a data model to describe the entities and their relationships, and a Namespace to describe the unambiguous set of identifier values.

a SIRI Service Participant is a participating system that exchanges SIRI messages with another Service Participant

NOTE Each Service Participant has a unique identifier, (the Participant Code), which provides a scope (i.e. unique namespace) for all non-global data references, such as stop identifiers, vehicle identifiers, and also for message identifiers of requests and subscriptions. Service Participants will either be SIRI Functional Service systems providing information, or accredited client systems that send request and subscriptions to the services to obtain information.

a coherent named set of features that a SIRI Functional Service may implement to provide particular application functionality

NOTE Some capabilities are common to all services; others are specific to individual functional services. Each SIRI functional service has a number of required capabilities, a number of capabilities for which alternatives are allowed, and a number of optional capabilities. A Capability Matrix is used both to specify the named capabilities for each SIRI functional service, and for the capabilities common to all SIRI functional services.

an application mechanism used to specify whether a participant may use Service Capabilities, or access, specific Topic content of a Service

equipment or service that provides a specific convenience or service to passengers

EXAMPLE Ticket machines, elevators, mechanical stairs, toilets, porterage, left luggage, etc.

NOTE A facility may be an equipment, a service, a personal device or a reserved area.

a classification of fare and other service classes by category of user entitled to use them

a public transport information facility, as for instance terminals (on street, at information desks, telematic,) or printed material (leaflets displayed at stops, booklets)

NOTE SIRI does not model or represent PI FACILITIES; rather it describes data services that may be used to supply PI FACILITIES.

data management function of a DATA ADMINISTRATOR needed for the distributed processing and sharing of data in a STOP PLACE, POINT OF INTEREST or TOPOGRAPHICAL PLACE model

entity that is managed by a DATA ADMINISTRATOR as part of a distributed system of data management of objects with well defined identifiers and data ownership

NOTE 1 to entry: Such objects conform to the abstract DATA MANAGED OBJECT supertype that defines associations and behaviour for data management.

a user defined VALIDITY CONDITION used by a rule for selecting versions (e.g. river level > 1,5 m and bad weather)

external event defining a VALIDITY CONDITION. E.g exceptional flow of a river, bad weather, road closure for works

a message sent by a Consumer Client to a Producer Server to indicate that it is still interested in receiving Subscriptions

NOT 1 to entry Life-sign messages allow the Producer to detect failed clients and terminate their subscriptions, therefore making a more efficient use of its resources. SIRI does not currently provide automatic Life Sign messages.

a description of a recognized mode of failure, reified in SIRI as a named error. Requests may be refused because of an Error Condition is detected. Different Error conditions are each represented in SIRI as separate elements each with an error code and a recommended error handling procedure.

a classification of VERSIONs. E.g shareability of ENTITies between several versions

a classification of VERSION FRAMEs according to a common purpose. E.g. line descriptions for line versions, vehicle schedules, operating costs. A TYPE OF FRAME is ruled by a unique TYPE OF VALIDITY

condition used in order to characterise a given VERSION of a VERSION FRAME

Note 1 to entry: A VALIDITY CONDITION consists of a parameter (e.g. date, triggering event, etc.) and its type of application (e.g. for, from, until, etc.).

the content data part of a Delivery message, as opposed to the elements used to manage the message exchange such as the Endpoint Reference elements

a Delivery containing only that information which has changed since the last update

an informational message that is exchanged between Participants using a General Message service.

NOTE 1 to entry: Informative messages have an identifier and version so they can be updated and revoked. Their content may be in plain text, or structured according to an agreed format. Informative messages may be segregated into separate information channels according to an agreed categorisation, for example , Warning, Advice, etc.

a transient data container element included in a SIRI functional service response that has a timestamp; it may optionally have an Item Identifier which can be used to reference it subsequently, for example to associate a cancellation of an earlier item.

physical entity that supports the transmission of signals carrying information between ITS

physical component, whatever its form factor (embedded, removable or not) that can be installed in a media to host Applications in a secure environment for their execution

a POINT where a beacon or similar device to support the automatic detection of vehicles passing by is located

a classification of CHECK CONSTRAINT (e.g. ticket collection, ticket purchase, baggage check-in, incoming customs, outgoing customs, tax refunds, etc.)

the different CLASSEes IN REPOSITORY which can be relevant for corresponding VERSION FRAMEs

a part of a public transport network where the ROUTEs of several JOURNEY PATTERNs are going in parallel and where the synchronisation of SERVICE JOURNEYs may be planned and controlled with respect to commonly used LINKs and STOP POINTs; COMMON SECTIONs are defined arbitrarily and need not cover the total lengths of topologically bundled sections

the ENTITY associated to a given VERSION

intended effect of a system, subsystem, product, or part

Note 1 to entry: Functions should have a single definite purpose. Function names should have a declarative structure (e.g. “Validate telecommands”) and say “what” is to be done rather than “how”. Good naming allows design components with strong cohesion to be easily derived.

data design, that takes into account the type of database to be used, but does not consider means of utilization of space or access

a type of INFRASTRUCTURE POINT used to describe a wire network

small piece of semiconductive material that contains interconnected electronic elements