schema

specification prescribing for given platform (e.g. XML Schema, JSON Schema, ASN.1) structures used to represent data model

specification prescribing for given platform (e.g. XML Schema, JSON Schema, ASN.1) structures used to represent data model

schema processor

processor to validate schema

processor to validate schema

simple (data) types

types defined by directly specifying the set of its values

types defined by directly specifying the set of its values

single carriageway road segment; single carriageway road; single carriageway; undivided highway

roadway comprised of exactly one carriageway
NOTE 1 to entry: The World Road Association (PIARC) term is “single carriageway road” and is recognized as a preferred term. As per the definitions provided in this document, “single carriageway road segment” is more accurate and is the most preferred term. The term “single carriageway” by itself is not preferred but admitted.
NOTE 2 to entry: …

roadway comprised of exactly one carriageway
NOTE 1 to entry: The World Road Association (PIARC) term is “single carriageway road” and is recognized as a preferred term. As per the definitions provided in this document, “single carriageway road segment” is more accurate and is the most preferred term. The term “single carriageway” by itself is not preferred but admitted.
NOTE 2 to entry: A single carriageway road segment could have multiple lanes and could allow travel in opposite directions
NOTE 3 to entry: The term “undivided highway” is the equivalent American English term.

MTOM

SOAP Message Transmission Optimization Mechanism

soft shoulder

unpaved part of the road reservation not belonging to the carriageway but providing lateral support to it
NOTE 1 to entry: Soft shoulders are not normally intended for driving.
NOTE 2 to entry: Soft shoulders often have a grass or gravel surface.

unpaved part of the road reservation not belonging to the carriageway but providing lateral support to it
NOTE 1 to entry: Soft shoulders are not normally intended for driving.
NOTE 2 to entry: Soft shoulders often have a grass or gravel surface.

specified design

the exact equipment specification or manufacturers identification as installed in a deployment

the exact equipment specification or manufacturers identification as installed in a deployment

speed

rate of change of a material entity's position with respect to a frame of reference
NOTE 1 to entry: Speed is a function of time.
NOTE 2 to entry: Speed is the scalar absolute value (magnitude) of velocity.

rate of change of a material entity's position with respect to a frame of reference
NOTE 1 to entry: Speed is a function of time.
NOTE 2 to entry: Speed is the scalar absolute value (magnitude) of velocity.

stakeholder

individual or organisation having a right, share, claim or interest in a system or in its possession of characteristics that meet their needs and expectations
NOTE 1 to entry: Their involvement can be through use, manufacture of products, provision of Services, or regulation.

individual or organisation having a right, share, claim or interest in a system or in its possession of characteristics that meet their needs and expectations
NOTE 1 to entry: Their involvement can be through use, manufacture of products, provision of Services, or regulation.

stakeholder need

formal expression, using “shall” language, to define what the stakeholders expect the ITS implementation to provide, and from which the functional viewpoint is created, also known as “user need”

formal expression, using “shall” language, to define what the stakeholders expect the ITS implementation to provide, and from which the functional viewpoint is created, also known as “user need”

stakeholder; system stakeholder

individual, team, organization, or classes thereof, having an interest in a system
[SOURCE: ISO/IEC/IEEE 42010:2011, 3.10]

individual, team, organization, or classes thereof, having an interest in a system
[SOURCE: ISO/IEC/IEEE 42010:2011, 3.10]

stereotype

new type of modelling element that extends the semantics of the metamodel
NOTE 1 to entry: Stereotypes have to be based on certain existing types or classes in the metamodel. Stereotypes may extend the semantics, but not the structure of pre-existing types and classes. Certain stereotypes are predefined in the UML, others may be user defined. Stereotypes are one of three extensibility…

new type of modelling element that extends the semantics of the metamodel
NOTE 1 to entry: Stereotypes have to be based on certain existing types or classes in the metamodel. Stereotypes may extend the semantics, but not the structure of pre-existing types and classes. Certain stereotypes are predefined in the UML, others may be user defined. Stereotypes are one of three extensibility mechanisms in UML.
NOTE 2 to entry: The stereotype may specify additional constraints and tag definitions that apply to model elements. In addition, a stereotype may be used to indicate a difference in meaning or usage between two model elements with identical structure.

stub

client code required to talk to a remote service

client code required to talk to a remote service

sub module identifier

reference identifiers which relate to prescribed Sub Modules determined in subordinate Standards

reference identifiers which relate to prescribed Sub Modules determined in subordinate Standards

sub-processor

privacy stakeholder that processes PI on behalf of and in accordance with the instructions of a PI processor

privacy stakeholder that processes PI on behalf of and in accordance with the instructions of a PI processor

support system; ITS support system

ITS component that provides services in support of one or more other ITS components
EXAMPLE: Data distribution system, network time source, cooperative ITS credentials management system.

ITS component that provides services in support of one or more other ITS components
EXAMPLE: Data distribution system, network time source, cooperative ITS credentials management system.

supporting token

collection of (one or more) claims

collection of (one or more) claims

surface transport system

transport system designed to move material entities across the surface or near-surface of the Earth
NOTE 1 to entry: A surface transport system can include tunnels, bridges and similar elements.
NOTE 2 to entry: There is not complete agreement on the precise limitations of a “surface transport system” within the ITS community. Currently, the term is almost exclusively applied to ground…

transport system designed to move material entities across the surface or near-surface of the Earth
NOTE 1 to entry: A surface transport system can include tunnels, bridges and similar elements.
NOTE 2 to entry: There is not complete agreement on the precise limitations of a “surface transport system” within the ITS community. Currently, the term is almost exclusively applied to ground-based travel of goods and people over significant distances. The term is viewed as including ferry systems, which often form an integral part of a local surface transport system; it is less clear if it includes long-distance sea-fairing ships. The term “surface transport systems” is also generally limited to transport systems that cover a considerable distance (e.g. factory conveyance technologies are not often referred to as “surface transport systems”). It has been suggested that air travel, which is arguably a transport system designed to move physical entities between points on the surface of the earth, ought to be included in the scope of the term, but this perspective is not universally accepted. It is expected that the exact limitations of the term will be further refined as ITS matures.
NOTE 3 to entry: Due to the defined scope of ITS, the term “transport system” is intended to be interpreted as being synonymous with the term “surface transport system” unless explicitly specified otherwise.

syntax

set of rules defining the way in which data is put together with appropriate identifiers, delimiters, separator character(s), and other non-data characters to form messages

set of rules defining the way in which data is put together with appropriate identifiers, delimiters, separator character(s), and other non-data characters to form messages

system

combination of interacting elements organized to achieve one or more stated purposes
[SOURCE: ISO/IEC/IEEE 15288:2015, 4.1.46, modified — Notes to entry removed.]

combination of interacting elements organized to achieve one or more stated purposes
[SOURCE: ISO/IEC/IEEE 15288:2015, 4.1.46, modified — Notes to entry removed.]

tagged value

explicit definition of a property as a name-value pair
NOTE 1 to entry: Certain tags are predefined in the UML; others MAY be user defined. Tagged values are one of three extensibility mechanisms in UML.
NOTE 2 to entry: In a tagged value, the name is referred as the tag.

explicit definition of a property as a name-value pair
NOTE 1 to entry: Certain tags are predefined in the UML; others MAY be user defined. Tagged values are one of three extensibility mechanisms in UML.
NOTE 2 to entry: In a tagged value, the name is referred as the tag.

template

framework that may be used repeatedly to meet requirements that are similar to some extent

framework that may be used repeatedly to meet requirements that are similar to some extent

terminator; ITS terminator

entity that is external to the ITS service implementation but with which the implementation communicates either to obtain inputs or to which it can send outputs
NOTE 1 to entry: A terminator can exist within functional and physical views.

entity that is external to the ITS service implementation but with which the implementation communicates either to obtain inputs or to which it can send outputs
NOTE 1 to entry: A terminator can exist within functional and physical views.

third party

any person or legal entity receiving PI of a data subject other than the data subject itself or the controller or the processor

any person or legal entity receiving PI of a data subject other than the data subject itself or the controller or the processor

TICS architecture

a TICS Architecture can be described by conceptual, logical and/or physical representations; (see also Conceptual Architecture, Functional Architecture, Logical Architecture, Deployment Design); a TICS Architecture is not specific to any single location

a TICS Architecture can be described by conceptual, logical and/or physical representations; (see also Conceptual Architecture, Functional Architecture, Logical Architecture, Deployment Design); a TICS Architecture is not specific to any single location

TICS component

a subsystem of a TICS system, assembly, or other major element of a system which does not have, by itself, independent operational functionality

a subsystem of a TICS system, assembly, or other major element of a system which does not have, by itself, independent operational functionality

TICS system

a set of inter-related components which interact with one another in an organised fashion to provide independent operational functionality
NOTE: This is the IEEE Definition qualified with the “Independent operational functionality” phase).

a set of inter-related components which interact with one another in an organised fashion to provide independent operational functionality
NOTE: This is the IEEE Definition qualified with the “Independent operational functionality” phase).

TICS unit

minimum component capable of independent functionality

minimum component capable of independent functionality

token assertion

description of a token requirement
NOTE 1 to entry: Token assertions defined within a security binding are used to satisfy protection requirements.

description of a token requirement
NOTE 1 to entry: Token assertions defined within a security binding are used to satisfy protection requirements.

transit

alternative term for public transport that is used in some countries and in some instances and is
expanded to “public transit”

alternative term for public transport that is used in some countries and in some instances and is
expanded to “public transit”