application that uses ASN.1 encodings for communication (except XER)

a set of functions to be performed in a typical area combined to form a high level system design

architecture that provides a vision of a specific deployment of a system within a geographic area

method of writing specifications and developing applications, based on a platform-independent model (PIM)

NOTE A complete MDA specification consists of a definitive platform-independent base UML model, plus one or more platform-specific models (PSM) and interface definition sets, each describing how the base model is implemented on a different middleware platform.

<XML> property of an element

NOTE 1 to entry It is additional information about a piece of data (element). Often attributes are used to pass information about the element and hence can be said to provide metadata for the element. An attribute is a value indicator (=) and the attribute value is specified within the tag (i.e. <H3 align=""centre"">). Attribute in XML is a name=""value"" pair that can be placed in the start tag of an element. For XML, all values have to be quoted with single or double quotes.

association that connects exactly two classes

collection of data concepts that allows lookup by entity identifier

string consisting of one or more words, where each word within the string, except for the first, starts with an upper-case letter and all other letters are lowercase; the words follow each other without any

space; hyphens and numbers may be used, but the first character of the string must be a lower case alphabetic character; a hyphen may not be the last character or occur multiple times in sequence

data element, class, value domain, data frame, message or interface dialogue defined, at a minimum, with an unambiguous identifier and a definition

NOTE 1 to entry In order to exchange a value corresponding to a data concept, more information than an identifier, a name and a definition can be needed. For a property, a data type is needed. Depending on the kind of property, other data elements such as unit of measure, and language, can be needed as well. The additional information can be given in the data dictionary, in a data specification that references the data concept or associated with the data themselves.

<XML> create new types (both simple and complex)

XML document that conforms to a schema

EXAMPLE If the schema is WSDL, the XML document is an WSDL instance document.

formal set of production rules that comprise a grammar defining language, such as XML

XML based specification for the interoperable exchange of metadata

NOTE It is today most commonly used to exchange UML models between UML tools. XMI is specified in ISO/IEC 19503:2005.

a description or definition of a design in terms of its processes and data flows; it does not include hardware or physical items; a functional Architecture is an aspect of a “Logical”, “Process Oriented” decomposition of an overall TICS Architecture (see Process Oriented Logical Architecture); a functional Architecture is not specific to any location; a description of the system in terms of functions and information flows between the functions

set of related processes that are performed by a physical object to fulfil aspects of an ITS service

EXAMPLE A vehicle OBE can include a “vehicle basic safety” functional object.

NOTE 1 to entry The term “module” is used by the European FRAME architecture while the Architecture Reference for Cooperative and Intelligent Transportation (ARC-IT) uses the term “functional object”.

with respect to a Process Oriented Logical Architecture, the Physical Architecture is the allocation of the functions and data flows of the logical architecture to physical entities (but not relate to the deployment of equipment) (see Process Oriented and Logical Architecture); a Physical Architecture, whilst describing physical configurations in system terms, is not specific to any particular location

a subset of a physical architecture which mainly considers the realization of providing one or more service(s)

architecture view from the physical viewpoint

NOTE 1 to entry The term “deployment view” is sometimes used within the broader ICT community, but the term “physical view” is preferred to prevent confusion between the physical view of a reference architecture and any part of a deployment architecture.

work product establishing the conventions for the construction, interpretation and use of architecture views to frame specific system concerns

[SOURCE: ISO/IEC/IEEE 42010:2011, 3.6]

instance of an object identifier type which relates to an associated module

NOTE In ISO/IEC 8824 a module identifier is defined as: ModuleIdentifier::= modulereference DefinitiveIdentifier If the “DefinitiveIdentifier” is not empty, the denoted object identifier value unambiguously and uniquely identifies the module being defined. No defined value may be used in defining the object identifier value.

XML representation of an ASN.1 OID

EXAMPLE In the following example, the ASN.1 OID delimiter (white  ) changed by a designated delimiter.

ASN.1 OID: iso standard 24531 schema 1; XML OID (delimiter “_”): iso_standard_24531_schema_1; XML OID (delimiter “/”): iso/standard/24531/schema/1

with respect to process oriented decomposition, the Information Architecture defines the entities and the relationships of information (Data model) and the principal data constructs (see Process Oriented and Logical Architecture)

NOTE The Information Architecture is not specific to any location

architecture based on political or administrational infrastructure partitioning and its division of responsibilities (rather than functions)

specific form of a system architecture for use as a tool in the initial stages of an ITS implementation; non specified system design for a family of functionally different ITS systems, interconnected to operate in consort; it is the non specified system design for a family of functionally different systems, interconnected to operate in harmony. An ITS architecture can be described from different viewpoints, and from multiple viewpoints by conceptual, logical and / or physical representations.

NOTE An ITS Architecture is not specific to any single location. Additional terms may be explicitly referenced in individual standards or references to the source definition explicitly provided.

language for defining interfaces to CORBA objects which is independent of platform, operating system and programming language

IRI compact string of characters for identifying an abstract or physical resource

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

integration of each physical object necessary to implement one or more ITS applications

NOTE 1 to entry An ITS application typically requires multiple components (e.g. an ITS-S acting as a user and another ITS-S acting as a provider). An ITS implementation includes a sample of each component necessary for the service but often does not represent a complete deployment.

NOTE 2 to entry An ITS implementation is typically used for a laboratory or other experimental environment prior to a full-scale deployment.

framework that tells designers how elements of hardware and software are to operate in harmony using common protocols and air interface techniques (where applicable)

architecture view from the communications viewpoint

NOTE 1 to entry Within ITS, the preferred model for describing the communications view is based on the ITS-S reference architecture.

<UML> endpoint of an association, which connects the association to a classifier

descriptive word or group of words that labels a data concept within its defined context

<XML> element, group, attribute, attribute group, or data types that are not global

work product representing one or more architecture views and expressed in a format governed by a model kind

data concept that contains the formal syntactic definition, and optionally the semantic definition, of a defined set of other data concepts that are all version-controlled as a single unit; a module can be represented in multiple languages (e.g., ASN.1 or XML Schema) and compiled by computer systems

object class that the data concept describes

characteristics necessary to fully define how various physical objects interoperate to provide a service

NOTE 1 to entry Characteristics often include but are not limited to functional, performance and interface requirements.

name of a data concept expressed as a valid “typereference” as defined by ISO/IEC 8824-1

identifier that represents a version number that the data concept is more generally known by

<XML> all data between the start tag and end tag of an element

NOTE 1 to entry Content may be made up of mark-up characters and character data.

notation which can be used in association with a type, to define a subtype of that type

viewpoint showing how the “building blocks” from the physical viewpoint (or the functional viewpoint) can be allocated to the different types of organisation (or organisations themselves if known) that will be involved with the ITS implementation

structured proposal for business improvement that functions as a decision package for decision-makers The business case should explain why a project is required for the business and what the product or service is going to be. It should include an outline of the “Return on Investment” (ROI), or a cost/benefit analysis for the project, the project's product and performance characteristics, major project risks and the opportunities.

The business case addresses, at a high level, the business needs that the project seeks to meet. It includes the reasons for the project, the expected business benefits, the options considered (with reasons for rejecting or carrying forward each option), the expected costs of the project, a GAP analysis and the expected risks.

framework into which business processes are deployed and ensures that the organization's core qualities are realized across the business processes deployed within the organization

NOTE In this way organizations aim to consistently realize their core qualities across the services they offer to their clients

architecture viewpoint used to frame the policies, funding incentives, working arrangements and jurisdictional structure that support the technical layers of the architecture

architecture view from the enterprise viewpoint

work product expressing the architecture of a system from the perspective of specific system concerns

[SOURCE: ISO/IEC/IEEE 42010:2011, 3.5]

top most graphical section of a class box defining the name of the class and optionally a stereotype, inherited class and package scope

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”

<functional view> series of one or more functions in support of an ITS service

a methodology based on decomposition of the Conceptual Architecture into Functional, Control and Information Architectures

<UML> processor to validate schema

inter ORB protocol that allows ORBs to use the Internet as a communications bus by mapping inter ORB messages onto TCP/IP

<architecture> component member of an architecture model included in an architecture view

policy subject entity with which a policy assertion can be associated (WS-Policy)

EXAMPLE An endpoint, message, resource, operation.

transfer of personal information to recipients other than the data subject, the controller or a processor, in particular publishing of data as well as the use of data for another application purpose of the controller

architecture that provides a template solution for planning and deployment architectures

NOTE 1 to entry Interface standards are based on a reference architecture, which should be explicitly described.

namespace prefix

<XML> short name to uniquely identify the namespace profile

<UML> stereotyped package that contains model elements, which have been customized for a specific domain or purpose using extension mechanisms, such as stereotypes, tagged definitions and constraints

NOTE 1 to entry A profile may also specify model libraries on which it depends and the metamodel subset that it extends.

type which is used only for defining the value and subtype notation for a type

NOTE Associated types are defined when it is necessary to make it clear that there may be a significant difference between how the type is defined in ASN.1 and how it is encoded. Associated types do not appear in user specifications.

reference architecture for one or more ITS services

NOTE 1 to entry An ITS architecture can be a reference, planning or deployment architecture.

NOTE 2 to entry The Harmonised Architecture Reference for Technical Standards (HARTS; see Reference [26]) is an example of an ITS reference architecture.

electronic data dictionary that follows precise documented rules for the registration and management of stored data concepts

NOTE 1 to entry The data concept registry contains meta-attributes about data concepts in terms of their names and representational forms as well as the semantics associated with the data concepts. A data concept registry may contain metadata that assists information interchange and re-use, both from the perspective of human users and for machine-interpretation of data concepts.

NOTE 2 to entry A data concept registry typically includes advanced features for adding retrieving, and working with its contents.

organizational element or an individual appointed by ISO/TC 204 to undertake the day-to-day management of the Data Registry process

<enterprise view> element that represents the specified responsibilities between an enterprise object and another enterprise view element

set of rules for encoding electronic documents defined by the World Wide Web Consortium W3C

NOTE Although developed for documents, it is today widely used for data exchange in general, usually in conjunction with an XML Schema Definition

<use case> description of the sequence of events from the user's perspective to perform a task in a specified context

[SOURCE: ISO/IEC 25062:2006, A.17]

<XML, UML> system of representing an information model that defines the data’s elements and attributes

a formal description of the allowed content of an XML document that claims compliance to the schema

NOTE 1 to entry XML Schema Definitions allow for formal validation of syntactical compliance of instance documents.

event that starts the process in a scenario

tree whose root corresponds to ISO/IEC 9834-1 and whose nodes correspond to Registration Authorities

responsible for allocating arcs from a parent node

defined annotated outline for an ITS application specification

<UML> 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.

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

data type (or type for short) that represents in a formalised way a class of information (for example, numerical, textual, still image or video information); the representation is conformant to definitions given in ISO/IEC 8824-1

type definition that does not conform to ISO/IEC 8824

<XML> elements, comments, processing instructions, and text in an XML document

NOTE 1 to entry An XML document has a hierarchical structure, described as a tree. The tree has branches connecting at the nodes.

factor or condition necessary to achieve desired results within a specified context of use

[SOURCE: ISO/IEC TR 25060:2010, 2.25, modified — “for a user” removed from definition.]

types defined by directly specifying the set of its values

<enterprise view> element that represents an association between two resources

data element that cannot be further subdivided meaningfully within the context of ASN.1

<XML> identification of element types and structure within a document

NOTE 1 to entry The mark-up is not actually part of the content, but identifies the components and their roles.

function within the CORBA architecture that acts as a broker in fulfilling client requests for services from objects in a distributed environment