diff --git a/concepts/concept-3.1.1.1.yaml b/concepts/concept-3.1.1.1.yaml index 10719bb..e158f03 100644 --- a/concepts/concept-3.1.1.1.yaml +++ b/concepts/concept-3.1.1.1.yaml @@ -11,7 +11,7 @@ eng: including associations among these things notes: [] examples: - - content: "{{urn:iso:std:iso:14812:3.1.1.6,person,Person}}, object, event, idea, + - content: "{{<>,person,Person}}, object, event, idea, process, etc." language_code: eng entry_status: valid diff --git a/concepts/concept-3.1.1.2.yaml b/concepts/concept-3.1.1.2.yaml index c9d2730..4a685e4 100644 --- a/concepts/concept-3.1.1.2.yaml +++ b/concepts/concept-3.1.1.2.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: immaterial entity definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.1,entity}} that does not occupy three-dimensional + - content: "{{<>,entity}} that does not occupy three-dimensional space" notes: [] examples: diff --git a/concepts/concept-3.1.1.3.yaml b/concepts/concept-3.1.1.3.yaml index 525d182..be88d21 100644 --- a/concepts/concept-3.1.1.3.yaml +++ b/concepts/concept-3.1.1.3.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: material entity definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.1,entity}} that occupies three-dimensional + - content: "{{<>,entity}} that occupies three-dimensional space" notes: - content: All material entities have certain characteristics that can be described diff --git a/concepts/concept-3.1.1.4.yaml b/concepts/concept-3.1.1.4.yaml index 914aba7..51f233f 100644 --- a/concepts/concept-3.1.1.4.yaml +++ b/concepts/concept-3.1.1.4.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: non-biological entity definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.3,material entity}} that is not and has + - content: "{{<>,material entity}} that is not and has never been a living organism" notes: [] examples: [] diff --git a/concepts/concept-3.1.1.5.yaml b/concepts/concept-3.1.1.5.yaml index 928769e..0998dc9 100644 --- a/concepts/concept-3.1.1.5.yaml +++ b/concepts/concept-3.1.1.5.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: biological entity definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.3,material entity}} that was or is a living + - content: "{{<>,material entity}} that was or is a living organism" notes: [] examples: [] diff --git a/concepts/concept-3.1.1.6.yaml b/concepts/concept-3.1.1.6.yaml index 04691ef..45b5dd7 100644 --- a/concepts/concept-3.1.1.6.yaml +++ b/concepts/concept-3.1.1.6.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: person definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.5,biological entity}} that is a human + - content: "{{<>,biological entity}} that is a human being" notes: [] examples: [] diff --git a/concepts/concept-3.1.10.1.yaml b/concepts/concept-3.1.10.1.yaml index dbdc0a1..ddbb412 100644 --- a/concepts/concept-3.1.10.1.yaml +++ b/concepts/concept-3.1.10.1.yaml @@ -7,16 +7,16 @@ eng: normative_status: preferred designation: data concept definition: - - content: "{{urn:iso:std:iso:14812:3.1.11.1,data element}}, {{urn:iso:std:iso:14812:3.1.11.2,class}}, - {{urn:iso:std:iso:14812:3.1.11.3,value domain}}, {{urn:iso:std:iso:14812:3.1.11.4,data - frame}}, {{urn:iso:std:iso:14812:3.1.11.5,message}} or {{urn:iso:std:iso:14812:3.1.11.6,interface + - content: "{{<>,data element}}, {{<>,class}}, + {{<>,value domain}}, {{<>,data + frame}}, {{<>,message}} or {{<>,interface dialogue}} defined, at a minimum, with an unambiguous identifier and a definition" notes: - content: 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 {{urn:iso:std:iso:14812:3.1.10.3,data dictionary}}, + information can be given in the {{<>,data dictionary}}, in a data specification that references the data concept or associated with the data themselves. examples: [] diff --git a/concepts/concept-3.1.10.2.yaml b/concepts/concept-3.1.10.2.yaml index 43e42b7..0dd32e1 100644 --- a/concepts/concept-3.1.10.2.yaml +++ b/concepts/concept-3.1.10.2.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: meta-attribute definition: - - content: documenting characteristic of a {{urn:iso:std:iso:14812:3.1.10.1,data - concept}} that is stored in a {{urn:iso:std:iso:14812:3.1.10.3,data dictionary}} + - content: documenting characteristic of a {{<>,data + concept}} that is stored in a {{<>,data dictionary}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.10.3.yaml b/concepts/concept-3.1.10.3.yaml index 29e4b6e..7209cce 100644 --- a/concepts/concept-3.1.10.3.yaml +++ b/concepts/concept-3.1.10.3.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: data dictionary definition: - - content: collection of {{urn:iso:std:iso:14812:3.1.10.1,data concept,data concepts}} - that allows lookup by {{urn:iso:std:iso:14812:3.1.1.1,entity}} identifier + - content: collection of {{<>,data concept,data concepts}} + that allows lookup by {{<>,entity}} identifier notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.10.4.yaml b/concepts/concept-3.1.10.4.yaml index 32dec3f..91b3288 100644 --- a/concepts/concept-3.1.10.4.yaml +++ b/concepts/concept-3.1.10.4.yaml @@ -7,11 +7,11 @@ eng: normative_status: preferred designation: data concept registry definition: - - content: electronic {{urn:iso:std:iso:14812:3.1.10.3,data dictionary}} that follows - precise documented rules for the registration and management of stored {{urn:iso:std:iso:14812:3.1.10.1,data + - content: electronic {{<>,data dictionary}} that follows + precise documented rules for the registration and management of stored {{<>,data concept,data concepts}} notes: - - content: The data concept registry contains {{urn:iso:std:iso:14812:3.1.10.2,meta-attribute,meta-attributes}} + - content: The data concept registry contains {{<>,meta-attribute,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 diff --git a/concepts/concept-3.1.11.1.yaml b/concepts/concept-3.1.11.1.yaml index 769f9be..0f5277c 100644 --- a/concepts/concept-3.1.11.1.yaml +++ b/concepts/concept-3.1.11.1.yaml @@ -12,7 +12,7 @@ eng: notes: - content: This definition states that a data element is “indivisible” in a given context. This means it is possible for a data element considered indivisible - in one context [e.g. {{urn:iso:std:iso:14812:3.4.1.1,location}}] to be divisible + in one context [e.g. {{<>,location}}] to be divisible in another context (e.g. latitude, longitude, and elevation). examples: [] language_code: eng diff --git a/concepts/concept-3.1.11.4.yaml b/concepts/concept-3.1.11.4.yaml index dce4714..b814016 100644 --- a/concepts/concept-3.1.11.4.yaml +++ b/concepts/concept-3.1.11.4.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: data frame definition: - - content: specific grouping of {{urn:iso:std:iso:14812:3.1.11.1,data element,data + - content: specific grouping of {{<>,data element,data elements}} that describes information of interest through a useful grouping - of more atomic properties about one or more {{urn:iso:std:iso:14812:3.1.11.2,class,classes}} + of more atomic properties about one or more {{<>,class,classes}} notes: - content: The grouping can be a set, sequence or a choice. - content: A data frame can contain other data frames. diff --git a/concepts/concept-3.1.11.5.yaml b/concepts/concept-3.1.11.5.yaml index 45956f6..738ba29 100644 --- a/concepts/concept-3.1.11.5.yaml +++ b/concepts/concept-3.1.11.5.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: message definition: - - content: grouping of {{urn:iso:std:iso:14812:3.1.11.1,data element,data elements}}, - {{urn:iso:std:iso:14812:3.1.11.4,data frame,data frames}}, or data elements + - content: grouping of {{<>,data element,data elements}}, + {{<>,data frame,data frames}}, or data elements and data frames that is used to convey information notes: [] examples: [] diff --git a/concepts/concept-3.1.12.1.yaml b/concepts/concept-3.1.12.1.yaml index d2f07e4..8ad03a5 100644 --- a/concepts/concept-3.1.12.1.yaml +++ b/concepts/concept-3.1.12.1.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: use case definition: - - content: description of the behavioural requirements of a {{urn:iso:std:iso:14812:3.1.2.1,system}} - and its {{urn:iso:std:iso:14812:3.1.6.4,interaction}} with a {{urn:iso:std:iso:14812:3.5.3.4,user}} + - content: description of the behavioural requirements of a {{<>,system}} + and its {{<>,interaction}} with a {{<>,user}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.12.2.yaml b/concepts/concept-3.1.12.2.yaml index cec5fc9..207e77c 100644 --- a/concepts/concept-3.1.12.2.yaml +++ b/concepts/concept-3.1.12.2.yaml @@ -11,7 +11,7 @@ eng: designation: use case scenario domain: use case definition: - - content: description of the sequence of events from the {{urn:iso:std:iso:14812:3.5.3.4,user,user's}} + - content: description of the sequence of events from the {{<>,user,user's}} perspective to perform a task in a specified context notes: [] examples: [] diff --git a/concepts/concept-3.1.13.2.yaml b/concepts/concept-3.1.13.2.yaml index 66f3524..ae1746f 100644 --- a/concepts/concept-3.1.13.2.yaml +++ b/concepts/concept-3.1.13.2.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: duration definition: - - content: time between two {{urn:iso:std:iso:14812:3.1.13.1,instant,instants}} + - content: time between two {{<>,instant,instants}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.2.1.yaml b/concepts/concept-3.1.2.1.yaml index 4ac220a..3aa1771 100644 --- a/concepts/concept-3.1.2.1.yaml +++ b/concepts/concept-3.1.2.1.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: system definition: - - content: combination of interacting {{urn:iso:std:iso:14812:3.1.3.10,element,elements}} + - content: combination of interacting {{<>,element,elements}} organized to achieve one or more stated purposes notes: [] examples: [] diff --git a/concepts/concept-3.1.2.2.yaml b/concepts/concept-3.1.2.2.yaml index e107fd1..b1773ef 100644 --- a/concepts/concept-3.1.2.2.yaml +++ b/concepts/concept-3.1.2.2.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: transport system definition: - - content: "{{urn:iso:std:iso:14812:3.1.2.1,system}} of infrastructure {{urn:iso:std:iso:14812:3.1.3.10,element,elements}} - and optionally {{urn:iso:std:iso:14812:3.7.1.1,vehicle,vehicles}} that are jointly - designed to move {{urn:iso:std:iso:14812:3.1.1.3,material entity,material entities}} + - content: "{{<>,system}} of infrastructure {{<>,element,elements}} + and optionally {{<>,vehicle,vehicles}} that are jointly + designed to move {{<>,material entity,material entities}} from an origin to a destination" notes: - content: Transport systems can also include any supporting system, such as information diff --git a/concepts/concept-3.1.2.3.yaml b/concepts/concept-3.1.2.3.yaml index 648d097..8e0516b 100644 --- a/concepts/concept-3.1.2.3.yaml +++ b/concepts/concept-3.1.2.3.yaml @@ -10,11 +10,11 @@ eng: normative_status: admitted designation: transport system definition: - - content: "{{urn:iso:std:iso:14812:3.1.2.2,transport system}} designed to move - {{urn:iso:std:iso:14812:3.1.1.3,material entity,material entities}} across the + - content: "{{<>,transport system}} designed to move + {{<>,material entity,material entities}} across the surface or near-surface of the Earth" notes: - - content: A surface transport system can include tunnels, bridges and similar {{urn:iso:std:iso:14812:3.1.3.10,element,elements}}. + - content: A surface transport system can include tunnels, bridges and similar {{<>,element,elements}}. - content: 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. diff --git a/concepts/concept-3.1.2.4.yaml b/concepts/concept-3.1.2.4.yaml index 5410820..6b99cbf 100644 --- a/concepts/concept-3.1.2.4.yaml +++ b/concepts/concept-3.1.2.4.yaml @@ -13,8 +13,8 @@ eng: normative_status: admitted designation: intelligent transportation system definition: - - content: "{{urn:iso:std:iso:14812:3.1.2.1,system}} comprised of information, communication, - sensor and control technologies and that is designed to benefit a {{urn:iso:std:iso:14812:3.1.2.3,surface + - content: "{{<>,system}} comprised of information, communication, + sensor and control technologies and that is designed to benefit a {{<>,surface transport system}}" notes: - content: '"Intelligent transportation system" is the American English equivalent.' diff --git a/concepts/concept-3.1.2.5.yaml b/concepts/concept-3.1.2.5.yaml index 01437f2..23ad7ba 100644 --- a/concepts/concept-3.1.2.5.yaml +++ b/concepts/concept-3.1.2.5.yaml @@ -10,9 +10,9 @@ eng: normative_status: preferred designation: C-ITS definition: - - content: subset of {{urn:iso:std:iso:14812:3.1.2.4,intelligent transport system,ITS}} - where information is shared among {{urn:iso:std:iso:14812:3.2.7.3,ITS station,ITS - stations}} in a manner that enables its use by multiple {{urn:iso:std:iso:14812:3.5.3.1,ITS + - content: subset of {{<>,intelligent transport system,ITS}} + where information is shared among {{<>,ITS station,ITS + stations}} in a manner that enables its use by multiple {{<>,ITS service,ITS services}} notes: [] examples: [] diff --git a/concepts/concept-3.1.3.1.yaml b/concepts/concept-3.1.3.1.yaml index 5243f4c..efb59d4 100644 --- a/concepts/concept-3.1.3.1.yaml +++ b/concepts/concept-3.1.3.1.yaml @@ -11,9 +11,9 @@ eng: designation: system architecture domain: system definition: - - content: fundamental concepts or properties of a {{urn:iso:std:iso:14812:3.1.2.1,system}} - in its {{urn:iso:std:iso:14812:3.1.3.11,environment}} embodied in its {{urn:iso:std:iso:14812:3.1.3.10,element,elements}}, - {{urn:iso:std:iso:14812:3.1.6.8,relationship,relationships}} and in the principles + - content: fundamental concepts or properties of a {{<>,system}} + in its {{<>,environment}} embodied in its {{<>,element,elements}}, + {{<>,relationship,relationships}} and in the principles of its design and evolution notes: [] examples: [] diff --git a/concepts/concept-3.1.3.10.yaml b/concepts/concept-3.1.3.10.yaml index 75b19d8..c838338 100644 --- a/concepts/concept-3.1.3.10.yaml +++ b/concepts/concept-3.1.3.10.yaml @@ -11,8 +11,8 @@ eng: designation: architecture element domain: architecture definition: - - content: component member of an {{urn:iso:std:iso:14812:3.1.3.9,architecture model}} - included in an {{urn:iso:std:iso:14812:3.1.3.7,architecture view}} + - content: component member of an {{<>,architecture model}} + included in an {{<>,architecture view}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.3.11.yaml b/concepts/concept-3.1.3.11.yaml index 4e00691..572b887 100644 --- a/concepts/concept-3.1.3.11.yaml +++ b/concepts/concept-3.1.3.11.yaml @@ -12,7 +12,7 @@ eng: domain: system definition: - content: context determining the setting and circumstances of all influences upon - a {{urn:iso:std:iso:14812:3.1.2.1,system}} + a {{<>,system}} notes: - content: The environment of a system includes developmental, technological, business, operational, organizational, political, economic, legal, regulatory, ecological diff --git a/concepts/concept-3.1.3.2.yaml b/concepts/concept-3.1.3.2.yaml index b9de41f..294cd95 100644 --- a/concepts/concept-3.1.3.2.yaml +++ b/concepts/concept-3.1.3.2.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: architecture description definition: - - content: work product used to express an {{urn:iso:std:iso:14812:3.1.3.1,architecture}} + - content: work product used to express an {{<>,architecture}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.3.3.yaml b/concepts/concept-3.1.3.3.yaml index 63d22b6..d79bb83 100644 --- a/concepts/concept-3.1.3.3.yaml +++ b/concepts/concept-3.1.3.3.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: architecture framework definition: - - content: conventions, principles and practices for the description of {{urn:iso:std:iso:14812:3.1.3.1,architecture,architectures}} - established within a specific domain of application and/or community of {{urn:iso:std:iso:14812:3.1.3.4,stakeholder,stakeholders}} + - content: conventions, principles and practices for the description of {{<>,architecture,architectures}} + established within a specific domain of application and/or community of {{<>,stakeholder,stakeholders}} notes: [] examples: - content: Generalised Enterprise Reference Architecture and Methodologies (GERAM) diff --git a/concepts/concept-3.1.3.4.yaml b/concepts/concept-3.1.3.4.yaml index 252dc03..bacd88b 100644 --- a/concepts/concept-3.1.3.4.yaml +++ b/concepts/concept-3.1.3.4.yaml @@ -11,8 +11,8 @@ eng: designation: system stakeholder domain: system definition: - - content: individual, team, organization, or {{urn:iso:std:iso:14812:3.1.12.2,scenario,classes}} - thereof, having an interest in a {{urn:iso:std:iso:14812:3.1.2.1,system}} + - content: individual, team, organization, or {{<>,scenario,classes}} + thereof, having an interest in a {{<>,system}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.3.5.yaml b/concepts/concept-3.1.3.5.yaml index 548ca33..f5d40fc 100644 --- a/concepts/concept-3.1.3.5.yaml +++ b/concepts/concept-3.1.3.5.yaml @@ -11,10 +11,10 @@ eng: designation: system concern domain: system definition: - - content: interest in a {{urn:iso:std:iso:14812:3.1.2.1,system}} relevant to one - or more of its {{urn:iso:std:iso:14812:3.1.3.4,stakeholder,stakeholders}} + - content: interest in a {{<>,system}} relevant to one + or more of its {{<>,stakeholder,stakeholders}} notes: - - content: A concern pertains to any influence on a system in its {{urn:iso:std:iso:14812:3.1.3.11,environment}}, + - content: A concern pertains to any influence on a system in its {{<>,environment}}, including developmental, technological, business, operational, organizational, political, economic, legal, regulatory, ecological and social influences. examples: [] diff --git a/concepts/concept-3.1.3.6.yaml b/concepts/concept-3.1.3.6.yaml index 3147776..289511c 100644 --- a/concepts/concept-3.1.3.6.yaml +++ b/concepts/concept-3.1.3.6.yaml @@ -8,8 +8,8 @@ eng: designation: architecture viewpoint definition: - content: work product establishing the conventions for the construction, interpretation - and use of {{urn:iso:std:iso:14812:3.1.3.7,architecture view,architecture views}} - to frame specific system {{urn:iso:std:iso:14812:3.1.3.5,concern,concerns}} + and use of {{<>,architecture view,architecture views}} + to frame specific system {{<>,concern,concerns}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.3.7.yaml b/concepts/concept-3.1.3.7.yaml index e4b485d..115e9fc 100644 --- a/concepts/concept-3.1.3.7.yaml +++ b/concepts/concept-3.1.3.7.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: architecture view definition: - - content: work product expressing the {{urn:iso:std:iso:14812:3.1.3.1,architecture}} - of a {{urn:iso:std:iso:14812:3.1.2.1,system}} from the perspective of specific - system {{urn:iso:std:iso:14812:3.1.3.5,concern,concerns}} + - content: work product expressing the {{<>,architecture}} + of a {{<>,system}} from the perspective of specific + system {{<>,concern,concerns}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.3.8.yaml b/concepts/concept-3.1.3.8.yaml index 5281f08..2e0c67d 100644 --- a/concepts/concept-3.1.3.8.yaml +++ b/concepts/concept-3.1.3.8.yaml @@ -9,8 +9,8 @@ eng: definition: - content: conventions for a type of modelling notes: - - content: Examples of model kinds include {{urn:iso:std:iso:14812:3.1.7.1,data - flow}} diagrams, {{urn:iso:std:iso:14812:3.1.11.2,class}} diagrams, Petri nets, + - content: Examples of model kinds include {{<>,data + flow}} diagrams, {{<>,class}} diagrams, Petri nets, balance sheets, organization charts and state transition models. examples: [] language_code: eng diff --git a/concepts/concept-3.1.3.9.yaml b/concepts/concept-3.1.3.9.yaml index bf58c09..6cd47d2 100644 --- a/concepts/concept-3.1.3.9.yaml +++ b/concepts/concept-3.1.3.9.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: architecture model definition: - - content: work product representing one or more {{urn:iso:std:iso:14812:3.1.3.7,architecture - view,architecture views}} and expressed in a format governed by a {{urn:iso:std:iso:14812:3.1.3.8,model + - content: work product representing one or more {{<>,architecture + view,architecture views}} and expressed in a format governed by a {{<>,model kind}} notes: [] examples: [] diff --git a/concepts/concept-3.1.4.1.yaml b/concepts/concept-3.1.4.1.yaml index ee26931..84ab4f8 100644 --- a/concepts/concept-3.1.4.1.yaml +++ b/concepts/concept-3.1.4.1.yaml @@ -7,11 +7,11 @@ eng: normative_status: preferred designation: communications view definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.7,architecture view}} from the {{urn:iso:std:iso:14812:3.1.4.2,communications + - content: "{{<>,architecture view}} from the {{<>,communications viewpoint}}" notes: - content: Within ITS, the preferred model for describing the communications view - is based on the {{urn:iso:std:iso:14812:3.1.9.4,ITS-S reference architecture}}. + is based on the {{<>,ITS-S reference architecture}}. examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.1.4.2.yaml b/concepts/concept-3.1.4.2.yaml index d668c53..27ae5cc 100644 --- a/concepts/concept-3.1.4.2.yaml +++ b/concepts/concept-3.1.4.2.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: communications viewpoint definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.6,architecture viewpoint}} used to frame - {{urn:iso:std:iso:14812:3.1.3.5,concern,concerns}} related to all layers of + - content: "{{<>,architecture viewpoint}} used to frame + {{<>,concern,concerns}} related to all layers of the Open Systems Interconnection (OSI) stack and related management and security issues" notes: [] diff --git a/concepts/concept-3.1.4.3.yaml b/concepts/concept-3.1.4.3.yaml index 53b3370..8bb0dd6 100644 --- a/concepts/concept-3.1.4.3.yaml +++ b/concepts/concept-3.1.4.3.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: enterprise view definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.7,architecture view}} from the {{urn:iso:std:iso:14812:3.1.4.4,enterprise + - content: "{{<>,architecture view}} from the {{<>,enterprise viewpoint}}" notes: [] examples: [] diff --git a/concepts/concept-3.1.4.4.yaml b/concepts/concept-3.1.4.4.yaml index dd00e15..904141f 100644 --- a/concepts/concept-3.1.4.4.yaml +++ b/concepts/concept-3.1.4.4.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: enterprise viewpoint definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.6,architecture viewpoint}} used to frame + - content: "{{<>,architecture viewpoint}} used to frame the policies, funding incentives, working arrangements and jurisdictional structure - that support the technical layers of the{{urn:iso:std:iso:14812:3.1.3.1,architecture}}" + that support the technical layers of the{{<>,architecture}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.4.5.yaml b/concepts/concept-3.1.4.5.yaml index 66bdfcb..bd473e4 100644 --- a/concepts/concept-3.1.4.5.yaml +++ b/concepts/concept-3.1.4.5.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: functional view definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.7,architecture view}} from the {{urn:iso:std:iso:14812:3.1.4.6,functional + - content: "{{<>,architecture view}} from the {{<>,functional viewpoint}}" notes: [] examples: [] diff --git a/concepts/concept-3.1.4.6.yaml b/concepts/concept-3.1.4.6.yaml index d8713ad..88c830c 100644 --- a/concepts/concept-3.1.4.6.yaml +++ b/concepts/concept-3.1.4.6.yaml @@ -7,10 +7,10 @@ eng: normative_status: preferred designation: functional viewpoint definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.6,architecture viewpoint}} used to frame - {{urn:iso:std:iso:14812:3.1.3.5,concern,concerns}} related to the definition - of {{urn:iso:std:iso:14812:3.1.7.2,process,processes}} that perform surface - transport functions and {{urn:iso:std:iso:14812:3.1.7.1,data flow,data flows}} + - content: "{{<>,architecture viewpoint}} used to frame + {{<>,concern,concerns}} related to the definition + of {{<>,process,processes}} that perform surface + transport functions and {{<>,data flow,data flows}} shared between these processes" notes: [] examples: [] diff --git a/concepts/concept-3.1.4.7.yaml b/concepts/concept-3.1.4.7.yaml index 5060d5c..2691c35 100644 --- a/concepts/concept-3.1.4.7.yaml +++ b/concepts/concept-3.1.4.7.yaml @@ -7,12 +7,12 @@ eng: normative_status: preferred designation: physical view definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.7,architecture view}} from the {{urn:iso:std:iso:14812:3.1.4.8,physical + - content: "{{<>,architecture view}} from the {{<>,physical viewpoint}}" notes: - content: 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 {{urn:iso:std:iso:14812:3.1.9.3,deployment + view of a reference architecture and any part of a {{<>,deployment architecture}}. examples: [] language_code: eng diff --git a/concepts/concept-3.1.4.8.yaml b/concepts/concept-3.1.4.8.yaml index 837c1ec..b6b1f6a 100644 --- a/concepts/concept-3.1.4.8.yaml +++ b/concepts/concept-3.1.4.8.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: physical viewpoint definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.6,architecture viewpoint}} used to frame - {{urn:iso:std:iso:14812:3.1.3.5,concern,concerns}} related to the assignment - of functionality to {{urn:iso:std:iso:14812:3.1.8.1,physical object,physical + - content: "{{<>,architecture viewpoint}} used to frame + {{<>,concern,concerns}} related to the assignment + of functionality to {{<>,physical object,physical objects}} and the interfaces among these physical objects" notes: [] examples: [] diff --git a/concepts/concept-3.1.5.1.yaml b/concepts/concept-3.1.5.1.yaml index edc30f0..416971e 100644 --- a/concepts/concept-3.1.5.1.yaml +++ b/concepts/concept-3.1.5.1.yaml @@ -14,7 +14,7 @@ eng: designation: information layer domain: ITS-S definition: - - content: part of the {{urn:iso:std:iso:14812:3.1.9.4,ITS-S reference architecture,ITS + - content: part of the {{<>,ITS-S reference architecture,ITS station reference architecture}} that is responsible for providing ITS-related functionality notes: @@ -22,7 +22,7 @@ eng: (NTCIP) standards identify an "information layer" on top of the traditional OSI stack. However, the purpose of this layer includes both information configuration and functionality. The ITS-S reference architecture separates these two roles - between the {{urn:iso:std:iso:14812:3.1.5.6,management entity}} and the application + between the {{<>,management entity}} and the application entity. examples: [] language_code: eng diff --git a/concepts/concept-3.1.5.3.yaml b/concepts/concept-3.1.5.3.yaml index 63b63d7..05af951 100644 --- a/concepts/concept-3.1.5.3.yaml +++ b/concepts/concept-3.1.5.3.yaml @@ -14,7 +14,7 @@ eng: designation: subnet layer domain: ITS-S definition: - - content: protocol layer in the {{urn:iso:std:iso:14812:3.1.9.4,ITS-S reference + - content: protocol layer in the {{<>,ITS-S reference architecture,ITS station reference architecture}} containing the OSI physical and data link layer protocols for ITS communications notes: diff --git a/concepts/concept-3.1.5.4.yaml b/concepts/concept-3.1.5.4.yaml index 92725bf..a855082 100644 --- a/concepts/concept-3.1.5.4.yaml +++ b/concepts/concept-3.1.5.4.yaml @@ -14,7 +14,7 @@ eng: designation: networking and transport layer domain: ITS-S definition: - - content: protocol layer in the {{urn:iso:std:iso:14812:3.1.9.4,ITS-S reference + - content: protocol layer in the {{<>,ITS-S reference architecture,ITS station reference architecture}} containing the OSI network and transport layer protocols notes: diff --git a/concepts/concept-3.1.5.5.yaml b/concepts/concept-3.1.5.5.yaml index ff1c854..afad0e6 100644 --- a/concepts/concept-3.1.5.5.yaml +++ b/concepts/concept-3.1.5.5.yaml @@ -14,13 +14,13 @@ eng: designation: application layer domain: ITS-S definition: - - content: protocol layer in the {{urn:iso:std:iso:14812:3.1.9.4,ITS-S reference + - content: protocol layer in the {{<>,ITS-S reference architecture,ITS station reference architecture}} containing the OSI session, presentation and application layer protocols notes: - content: Within the US, the NTCIP standards call the facilities layer the "application layer". However, as this term is easily confused with both the OSI application - layer and the {{urn:iso:std:iso:14812:3.1.5.1,application entity}}, the term + layer and the {{<>,application entity}}, the term should be avoided and qualified when used (e.g. OSI application layer). examples: [] language_code: eng diff --git a/concepts/concept-3.1.5.6.yaml b/concepts/concept-3.1.5.6.yaml index 948a231..4db0e8e 100644 --- a/concepts/concept-3.1.5.6.yaml +++ b/concepts/concept-3.1.5.6.yaml @@ -11,9 +11,9 @@ eng: designation: ITS-S management entity domain: ITS-S definition: - - content: part of the {{urn:iso:std:iso:14812:3.1.9.4,ITS-S reference architecture,ITS + - content: part of the {{<>,ITS-S reference architecture,ITS station reference architecture}} that is responsible for management of communications - and configuration information for the local {{urn:iso:std:iso:14812:3.1.8.1,physical + and configuration information for the local {{<>,physical object}} and possibly remote physical objects notes: [] examples: [] diff --git a/concepts/concept-3.1.5.7.yaml b/concepts/concept-3.1.5.7.yaml index 3a4f89e..1df9f1c 100644 --- a/concepts/concept-3.1.5.7.yaml +++ b/concepts/concept-3.1.5.7.yaml @@ -11,9 +11,9 @@ eng: designation: ITS-S security entity domain: ITS-S definition: - - content: part of the {{urn:iso:std:iso:14812:3.1.9.4,ITS-S reference architecture,ITS + - content: part of the {{<>,ITS-S reference architecture,ITS station reference architecture}} that is responsible for providing privacy, - communication security and {{urn:iso:std:iso:14812:3.1.2.1,system}} security + communication security and {{<>,system}} security notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.6.1.yaml b/concepts/concept-3.1.6.1.yaml index 2fd0f44..b6aacd8 100644 --- a/concepts/concept-3.1.6.1.yaml +++ b/concepts/concept-3.1.6.1.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: enterprise object definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.10,element}} within an {{urn:iso:std:iso:14812:3.1.4.3,enterprise + - content: "{{<>,element}} within an {{<>,enterprise view}} that represents an organization or individual" notes: [] examples: [] diff --git a/concepts/concept-3.1.6.10.yaml b/concepts/concept-3.1.6.10.yaml index 3ffb34d..c166c88 100644 --- a/concepts/concept-3.1.6.10.yaml +++ b/concepts/concept-3.1.6.10.yaml @@ -11,11 +11,11 @@ eng: designation: enterprise view extend domain: enterprise view definition: - - content: "{{urn:iso:std:iso:14812:3.1.6.8,relationship}} where one {{urn:iso:std:iso:14812:3.1.6.2,resource}} + - content: "{{<>,relationship}} where one {{<>,resource}} supplements another resource" notes: [] examples: - - content: A {{urn:iso:std:iso:14812:3.1.8.7,module}} can extend the functionality + - content: A {{<>,module}} can extend the functionality of another module. language_code: eng entry_status: valid diff --git a/concepts/concept-3.1.6.2.yaml b/concepts/concept-3.1.6.2.yaml index 87d021a..b6a972d 100644 --- a/concepts/concept-3.1.6.2.yaml +++ b/concepts/concept-3.1.6.2.yaml @@ -11,8 +11,8 @@ eng: designation: enterprise view resource domain: enterprise view definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.10,element}} that represents an {{urn:iso:std:iso:14812:3.1.1.1,entity}} - that is managed, operated, referenced and/or used to develop and provide {{urn:iso:std:iso:14812:3.1.2.4,intelligent + - content: "{{<>,element}} that represents an {{<>,entity}} + that is managed, operated, referenced and/or used to develop and provide {{<>,intelligent transport system,ITS}}" notes: [] examples: [] diff --git a/concepts/concept-3.1.6.4.yaml b/concepts/concept-3.1.6.4.yaml index 96f6cb7..130b141 100644 --- a/concepts/concept-3.1.6.4.yaml +++ b/concepts/concept-3.1.6.4.yaml @@ -11,8 +11,8 @@ eng: designation: enterprise view interaction domain: enterprise view definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.10,element}} that represents coordination - between two {{urn:iso:std:iso:14812:3.1.6.1,enterprise object,enterprise objects}}" + - content: "{{<>,element}} that represents coordination + between two {{<>,enterprise object,enterprise objects}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.6.5.yaml b/concepts/concept-3.1.6.5.yaml index 73c6010..641a075 100644 --- a/concepts/concept-3.1.6.5.yaml +++ b/concepts/concept-3.1.6.5.yaml @@ -11,13 +11,13 @@ eng: designation: enterprise view formal coordination domain: enterprise view definition: - - content: "{{urn:iso:std:iso:14812:3.1.6.4,interaction}} between two {{urn:iso:std:iso:14812:3.1.6.1,enterprise + - content: "{{<>,interaction}} between two {{<>,enterprise object,enterprise objects}} governed by a documented agreement" notes: [] examples: - content: A road operator can enter into formal agreement(s) with the owner of - a {{urn:iso:std:iso:14812:3.3.5.1,road}} and the owner(s) of the associated - {{urn:iso:std:iso:14812:3.3.1.10,roadside}} equipment. + a {{<>,road}} and the owner(s) of the associated + {{<>,roadside}} equipment. language_code: eng entry_status: valid sources: diff --git a/concepts/concept-3.1.6.6.yaml b/concepts/concept-3.1.6.6.yaml index 9ba0c84..2818f45 100644 --- a/concepts/concept-3.1.6.6.yaml +++ b/concepts/concept-3.1.6.6.yaml @@ -11,7 +11,7 @@ eng: designation: enterprise view informal coordination domain: enterprise view definition: - - content: "{{urn:iso:std:iso:14812:3.1.6.4,interaction}} between two {{urn:iso:std:iso:14812:3.1.6.1,enterprise + - content: "{{<>,interaction}} between two {{<>,enterprise object,enterprise objects}} governed by an understanding that is not documented in a formal agreement between the two parties" notes: [] diff --git a/concepts/concept-3.1.6.7.yaml b/concepts/concept-3.1.6.7.yaml index 835203f..3728919 100644 --- a/concepts/concept-3.1.6.7.yaml +++ b/concepts/concept-3.1.6.7.yaml @@ -11,9 +11,9 @@ eng: designation: enterprise view role domain: enterprise view definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.10,element}} that represents the specified - responsibilities between an {{urn:iso:std:iso:14812:3.1.6.1,enterprise object}} - and another {{urn:iso:std:iso:14812:3.1.4.3,enterprise view}} element" + - content: "{{<>,element}} that represents the specified + responsibilities between an {{<>,enterprise object}} + and another {{<>,enterprise view}} element" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.6.8.yaml b/concepts/concept-3.1.6.8.yaml index e6620ae..ff79da5 100644 --- a/concepts/concept-3.1.6.8.yaml +++ b/concepts/concept-3.1.6.8.yaml @@ -11,8 +11,8 @@ eng: designation: enterprise view relationship domain: enterprise view definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.10,element}} that represents an association - between two {{urn:iso:std:iso:14812:3.1.6.2,resource,resources}}" + - content: "{{<>,element}} that represents an association + between two {{<>,resource,resources}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.6.9.yaml b/concepts/concept-3.1.6.9.yaml index 317dfe1..af72049 100644 --- a/concepts/concept-3.1.6.9.yaml +++ b/concepts/concept-3.1.6.9.yaml @@ -11,11 +11,11 @@ eng: designation: enterprise view include domain: enterprise view definition: - - content: "{{urn:iso:std:iso:14812:3.1.6.8,relationship}} where one {{urn:iso:std:iso:14812:3.1.6.2,resource}} + - content: "{{<>,relationship}} where one {{<>,resource}} contains another resource" notes: [] examples: - - content: Every ITS component includes one or more {{urn:iso:std:iso:14812:3.1.8.7,module,modules}}. + - content: Every ITS component includes one or more {{<>,module,modules}}. language_code: eng entry_status: valid sources: diff --git a/concepts/concept-3.1.7.1.yaml b/concepts/concept-3.1.7.1.yaml index 58e57cf..75ddc51 100644 --- a/concepts/concept-3.1.7.1.yaml +++ b/concepts/concept-3.1.7.1.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: data flow definition: - - content: representation of data flowing between two {{urn:iso:std:iso:14812:3.1.7.2,process,processes}} - or between a process and a {{urn:iso:std:iso:14812:3.1.8.3,terminator}} + - content: representation of data flowing between two {{<>,process,processes}} + or between a process and a {{<>,terminator}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.7.2.yaml b/concepts/concept-3.1.7.2.yaml index 1573cb0..0a60c8a 100644 --- a/concepts/concept-3.1.7.2.yaml +++ b/concepts/concept-3.1.7.2.yaml @@ -11,8 +11,8 @@ eng: designation: functional view process domain: functional view definition: - - content: series of one or more {{urn:iso:std:iso:14812:3.1.7.3,function,functions}} - in support of an {{urn:iso:std:iso:14812:3.5.3.1,ITS service}} + - content: series of one or more {{<>,function,functions}} + in support of an {{<>,ITS service}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.7.3.yaml b/concepts/concept-3.1.7.3.yaml index 2f1c645..c552997 100644 --- a/concepts/concept-3.1.7.3.yaml +++ b/concepts/concept-3.1.7.3.yaml @@ -15,7 +15,7 @@ eng: a goal notes: - content: A function transforms inputs into outputs that may include the creation, - modification, monitoring or destruction of {{urn:iso:std:iso:14812:3.1.3.10,element,elements}}. + modification, monitoring or destruction of {{<>,element,elements}}. examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.1.7.4.yaml b/concepts/concept-3.1.7.4.yaml index ad28a5a..bc739ea 100644 --- a/concepts/concept-3.1.7.4.yaml +++ b/concepts/concept-3.1.7.4.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: process specification definition: - - content: "{{urn:iso:std:iso:14812:3.1.6.3,document}} that defines a lowest-level - {{urn:iso:std:iso:14812:3.1.7.2,process}}" + - content: "{{<>,document}} that defines a lowest-level + {{<>,process}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.8.1.yaml b/concepts/concept-3.1.8.1.yaml index 9be4293..9a4e0ab 100644 --- a/concepts/concept-3.1.8.1.yaml +++ b/concepts/concept-3.1.8.1.yaml @@ -11,16 +11,16 @@ eng: designation: ITS physical object domain: physical view definition: - - content: abstraction of a {{urn:iso:std:iso:14812:3.1.1.3,material entity}} that - interacts with other abstract material entities in the provision of {{urn:iso:std:iso:14812:3.5.3.1,ITS + - content: abstraction of a {{<>,material entity}} that + interacts with other abstract material entities in the provision of {{<>,ITS service,ITS services}} notes: - - content: Physical objects are represented as {{urn:iso:std:iso:14812:3.1.3.10,element,elements}} - within the {{urn:iso:std:iso:14812:3.1.4.7,physical view}} and perform a role. - Physical objects can be implemented as cloud-based {{urn:iso:std:iso:14812:3.1.2.1,system,systems}}. - - content: 'Within many {{urn:iso:std:iso:14812:3.1.9.5,ITS reference architecture,ITS + - content: Physical objects are represented as {{<>,element,elements}} + within the {{<>,physical view}} and perform a role. + Physical objects can be implemented as cloud-based {{<>,system,systems}}. + - content: 'Within many {{<>,ITS reference architecture,ITS reference architectures}}, physical objects are placed into one of five categories: - centre, support, field, vehicle or {{urn:iso:std:iso:14812:3.6.1.1,traveller}}.' + centre, support, field, vehicle or {{<>,traveller}}.' examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.1.8.2.yaml b/concepts/concept-3.1.8.2.yaml index 9479573..9b59a86 100644 --- a/concepts/concept-3.1.8.2.yaml +++ b/concepts/concept-3.1.8.2.yaml @@ -7,13 +7,13 @@ eng: normative_status: preferred designation: ITS component definition: - - content: "{{urn:iso:std:iso:14812:3.1.8.1,physical object}} that has been assigned - one or more {{urn:iso:std:iso:14812:3.1.8.6,functional object,functional objects}} - in the provision of one or more {{urn:iso:std:iso:14812:3.5.3.1,ITS service,ITS + - content: "{{<>,physical object}} that has been assigned + one or more {{<>,functional object,functional objects}} + in the provision of one or more {{<>,ITS service,ITS services}}" notes: - content: Physical objects are ITS components if they are an integral part of the - {{urn:iso:std:iso:14812:3.1.2.1,system}}; otherwise they are {{urn:iso:std:iso:14812:3.1.8.3,terminator,terminators}}. + {{<>,system}}; otherwise they are {{<>,terminator,terminators}}. examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.1.8.3.yaml b/concepts/concept-3.1.8.3.yaml index 62e19d6..5329e38 100644 --- a/concepts/concept-3.1.8.3.yaml +++ b/concepts/concept-3.1.8.3.yaml @@ -10,12 +10,12 @@ eng: normative_status: preferred designation: ITS terminator definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.1,entity}} that is external to the {{urn:iso:std:iso:14812:3.5.3.1,ITS + - content: "{{<>,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" notes: - - content: A terminator can exist within {{urn:iso:std:iso:14812:3.1.4.5,functional - view,functional}} and {{urn:iso:std:iso:14812:3.1.4.7,physical view,physical + - content: A terminator can exist within {{<>,functional + view,functional}} and {{<>,physical view,physical views}}. examples: [] language_code: eng diff --git a/concepts/concept-3.1.8.4.yaml b/concepts/concept-3.1.8.4.yaml index c0230c7..d6a94ff 100644 --- a/concepts/concept-3.1.8.4.yaml +++ b/concepts/concept-3.1.8.4.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: information flow definition: - - content: information that is exchanged between {{urn:iso:std:iso:14812:3.1.8.1,physical + - content: information that is exchanged between {{<>,physical object,physical objects}} notes: [] examples: [] diff --git a/concepts/concept-3.1.8.5.yaml b/concepts/concept-3.1.8.5.yaml index f0d16bd..a81a541 100644 --- a/concepts/concept-3.1.8.5.yaml +++ b/concepts/concept-3.1.8.5.yaml @@ -10,7 +10,7 @@ eng: normative_status: admitted designation: information flow triple definition: - - content: "{{urn:iso:std:iso:14812:3.1.8.4,information flow}} from a {{urn:iso:std:iso:14812:3.1.8.1,physical + - content: "{{<>,information flow}} from a {{<>,physical object}} acting as an information provider and sent to another physical object acting as an information consumer" notes: diff --git a/concepts/concept-3.1.8.6.yaml b/concepts/concept-3.1.8.6.yaml index bee9f23..53578da 100644 --- a/concepts/concept-3.1.8.6.yaml +++ b/concepts/concept-3.1.8.6.yaml @@ -10,9 +10,9 @@ eng: normative_status: preferred designation: ITS functional object definition: - - content: set of related {{urn:iso:std:iso:14812:3.1.7.2,process,processes}} that - are performed by a {{urn:iso:std:iso:14812:3.1.8.1,physical object}} to fulfil - aspects of an {{urn:iso:std:iso:14812:3.5.3.1,ITS service}} + - content: set of related {{<>,process,processes}} that + are performed by a {{<>,physical object}} to fulfil + aspects of an {{<>,ITS service}} notes: - content: The term "module" is used by the European FRAME architecture while the Architecture Reference for Cooperative and Intelligent Transportation (ARC-IT) diff --git a/concepts/concept-3.1.8.7.yaml b/concepts/concept-3.1.8.7.yaml index 03c1c71..7a38c97 100644 --- a/concepts/concept-3.1.8.7.yaml +++ b/concepts/concept-3.1.8.7.yaml @@ -10,7 +10,7 @@ eng: normative_status: preferred designation: ITS module definition: - - content: "{{urn:iso:std:iso:14812:3.1.8.6,functional object}} that can be replaced + - content: "{{<>,functional object}} that can be replaced and has defined interfaces" notes: [] examples: [] diff --git a/concepts/concept-3.1.9.1.yaml b/concepts/concept-3.1.9.1.yaml index af04d31..1a959fe 100644 --- a/concepts/concept-3.1.9.1.yaml +++ b/concepts/concept-3.1.9.1.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: reference architecture definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.1,architecture}} that provides a template - solution for {{urn:iso:std:iso:14812:3.1.9.2,planning architecture,planning}} - and {{urn:iso:std:iso:14812:3.1.9.3,deployment architecture,deployment architectures}}" + - content: "{{<>,architecture}} that provides a template + solution for {{<>,planning architecture,planning}} + and {{<>,deployment architecture,deployment architectures}}" notes: - content: Interface standards are based on a reference architecture, which should be explicitly described. diff --git a/concepts/concept-3.1.9.2.yaml b/concepts/concept-3.1.9.2.yaml index e847692..960faa4 100644 --- a/concepts/concept-3.1.9.2.yaml +++ b/concepts/concept-3.1.9.2.yaml @@ -10,9 +10,9 @@ eng: normative_status: admitted designation: regional architecture definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.1,architecture}} that provides a long-term - vision of {{urn:iso:std:iso:14812:3.1.3.10,element,system elements}} that may - be deployed and managed by different projects and/or {{urn:iso:std:iso:14812:3.1.1.1,entity,entities}} + - content: "{{<>,architecture}} that provides a long-term + vision of {{<>,element,system elements}} that may + be deployed and managed by different projects and/or {{<>,entity,entities}} within a geographic area" notes: - content: Some countries use the term "regional architecture", but in International diff --git a/concepts/concept-3.1.9.3.yaml b/concepts/concept-3.1.9.3.yaml index 81eb76b..5a9d1f6 100644 --- a/concepts/concept-3.1.9.3.yaml +++ b/concepts/concept-3.1.9.3.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: deployment architecture definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.1,architecture}} that provides a vision - of a specific deployment of a {{urn:iso:std:iso:14812:3.1.2.1,system}} within + - content: "{{<>,architecture}} that provides a vision + of a specific deployment of a {{<>,system}} within a geographic area" notes: [] examples: [] diff --git a/concepts/concept-3.1.9.4.yaml b/concepts/concept-3.1.9.4.yaml index 1a791ba..0150762 100644 --- a/concepts/concept-3.1.9.4.yaml +++ b/concepts/concept-3.1.9.4.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ITS-S reference architecture definition: - - content: "{{urn:iso:std:iso:14812:3.1.9.1,reference architecture}} for handling - communications within a {{urn:iso:std:iso:14812:3.1.8.1,physical object}} as + - content: "{{<>,reference architecture}} for handling + communications within a {{<>,physical object}} as defined in <>" notes: - content: The ITS-S reference architecture provides a model for describing communication. diff --git a/concepts/concept-3.1.9.5.yaml b/concepts/concept-3.1.9.5.yaml index f6177fc..685b72d 100644 --- a/concepts/concept-3.1.9.5.yaml +++ b/concepts/concept-3.1.9.5.yaml @@ -7,10 +7,10 @@ eng: normative_status: preferred designation: ITS reference architecture definition: - - content: "{{urn:iso:std:iso:14812:3.1.9.1,reference architecture}} for one or - more {{urn:iso:std:iso:14812:3.5.3.1,ITS service,ITS services}}" + - content: "{{<>,reference architecture}} for one or + more {{<>,ITS service,ITS services}}" notes: - - content: An ITS architecture can be a reference, planning or {{urn:iso:std:iso:14812:3.1.9.3,deployment + - content: An ITS architecture can be a reference, planning or {{<>,deployment architecture}}. - content: The Harmonised Architecture Reference for Technical Standards (HARTS; http://htg7.org[see] Reference <>) is an example of an ITS reference diff --git a/concepts/concept-3.1.9.6.yaml b/concepts/concept-3.1.9.6.yaml index b7a0ce5..bc77f3b 100644 --- a/concepts/concept-3.1.9.6.yaml +++ b/concepts/concept-3.1.9.6.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ITS planning architecture definition: - - content: "{{urn:iso:std:iso:14812:3.1.9.2,planning architecture}} for one or more - {{urn:iso:std:iso:14812:3.5.3.1,ITS service,ITS services}}" + - content: "{{<>,planning architecture}} for one or more + {{<>,ITS service,ITS services}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.1.9.7.yaml b/concepts/concept-3.1.9.7.yaml index c30cf87..93664e2 100644 --- a/concepts/concept-3.1.9.7.yaml +++ b/concepts/concept-3.1.9.7.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ITS deployment architecture definition: - - content: "{{urn:iso:std:iso:14812:3.1.9.3,deployment architecture}} for one or - more {{urn:iso:std:iso:14812:3.5.3.1,ITS service,ITS services}}" + - content: "{{<>,deployment architecture}} for one or + more {{<>,ITS service,ITS services}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.2.1.1.yaml b/concepts/concept-3.2.1.1.yaml index 868566f..c342cc3 100644 --- a/concepts/concept-3.2.1.1.yaml +++ b/concepts/concept-3.2.1.1.yaml @@ -10,9 +10,9 @@ eng: normative_status: preferred designation: ITS central system definition: - - content: "{{urn:iso:std:iso:14812:3.1.8.2,ITS component}} that provides application, - management, and/or administrative functions from a centralized{{urn:iso:std:iso:14812:3.4.1.1,location}}, - i.e. not at the {{urn:iso:std:iso:14812:3.3.1.10,roadside}}" + - content: "{{<>,ITS component}} that provides application, + management, and/or administrative functions from a centralized{{<>,location}}, + i.e. not at the {{<>,roadside}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.2.1.2.yaml b/concepts/concept-3.2.1.2.yaml index 35ff513..1c7f0af 100644 --- a/concepts/concept-3.2.1.2.yaml +++ b/concepts/concept-3.2.1.2.yaml @@ -13,11 +13,11 @@ eng: normative_status: preferred designation: roadside system definition: - - content: infrastructure-based {{urn:iso:std:iso:14812:3.1.8.2,ITS component}} + - content: infrastructure-based {{<>,ITS component}} located outside of a data centre that is designed to provide local processing or routing services while stationary notes: - - content: Typically, field systems are located along the {{urn:iso:std:iso:14812:3.3.1.10,roadside}}. + - content: Typically, field systems are located along the {{<>,roadside}}. - content: Typically, the operation of a field system is governed by management functions running in a centre system. - content: Field systems can be permanently installed or transportable. diff --git a/concepts/concept-3.2.1.3.yaml b/concepts/concept-3.2.1.3.yaml index 19ea45f..29fc50f 100644 --- a/concepts/concept-3.2.1.3.yaml +++ b/concepts/concept-3.2.1.3.yaml @@ -13,8 +13,8 @@ eng: normative_status: preferred designation: traveller system definition: - - content: "{{urn:iso:std:iso:14812:3.1.8.2,ITS component}}, other than a {{urn:iso:std:iso:14812:3.2.1.5,vehicle - system}}, that is used by a {{urn:iso:std:iso:14812:3.1.1.6,person}} in relation + - content: "{{<>,ITS component}}, other than a {{<>,vehicle + system}}, that is used by a {{<>,person}} in relation to a past, current or upcoming journey" notes: [] examples: [] diff --git a/concepts/concept-3.2.1.4.yaml b/concepts/concept-3.2.1.4.yaml index 3ca5d04..ad26980 100644 --- a/concepts/concept-3.2.1.4.yaml +++ b/concepts/concept-3.2.1.4.yaml @@ -10,12 +10,12 @@ eng: normative_status: preferred designation: ITS support system definition: - - content: "{{urn:iso:std:iso:14812:3.1.8.2,ITS component}} that provides services + - content: "{{<>,ITS component}} that provides services in support of one or more other ITS components" notes: [] examples: - - content: Data distribution {{urn:iso:std:iso:14812:3.1.2.1,system}}, network time - source, {{urn:iso:std:iso:14812:3.1.2.5,cooperative ITS}} credentials management + - content: Data distribution {{<>,system}}, network time + source, {{<>,cooperative ITS}} credentials management system. language_code: eng entry_status: valid diff --git a/concepts/concept-3.2.1.5.yaml b/concepts/concept-3.2.1.5.yaml index ed0b389..a38c840 100644 --- a/concepts/concept-3.2.1.5.yaml +++ b/concepts/concept-3.2.1.5.yaml @@ -10,8 +10,8 @@ eng: normative_status: preferred designation: ITS vehicle system definition: - - content: "{{urn:iso:std:iso:14812:3.1.8.2,ITS component}} that is installed as - a component of a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}}" + - content: "{{<>,ITS component}} that is installed as + a component of a {{<>,vehicle}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.2.2.1.yaml b/concepts/concept-3.2.2.1.yaml index 41d1f08..700e609 100644 --- a/concepts/concept-3.2.2.1.yaml +++ b/concepts/concept-3.2.2.1.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: emergency management central system definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.1,central system,centre system}} that - allows an {{urn:iso:std:iso:14812:3.1.1.1,entity}} to manage and respond to + - content: "{{<>,central system,centre system}} that + allows an {{<>,entity}} to manage and respond to crashes, events, disasters, evacuation orders and other incidents" notes: [] examples: [] diff --git a/concepts/concept-3.2.2.2.yaml b/concepts/concept-3.2.2.2.yaml index b07e033..c4dfc8b 100644 --- a/concepts/concept-3.2.2.2.yaml +++ b/concepts/concept-3.2.2.2.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: fleet and freight management central system definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.1,central system,centre system}} that + - content: "{{<>,central system,centre system}} that allows a fleet or freight operator to manage and control its personnel, equipment and/or freight" notes: [] diff --git a/concepts/concept-3.2.2.3.yaml b/concepts/concept-3.2.2.3.yaml index 878efed..4f7b74c 100644 --- a/concepts/concept-3.2.2.3.yaml +++ b/concepts/concept-3.2.2.3.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: maintenance and construction central management system definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.1,central system,centre system}} that - allows an {{urn:iso:std:iso:14812:3.1.1.1,entity}} to monitor and manage the - construction and maintenance of {{urn:iso:std:iso:14812:3.3.5.1,road}} infrastructure" + - content: "{{<>,central system,centre system}} that + allows an {{<>,entity}} to monitor and manage the + construction and maintenance of {{<>,road}} infrastructure" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.2.2.4.yaml b/concepts/concept-3.2.2.4.yaml index cea097a..3b7f7b3 100644 --- a/concepts/concept-3.2.2.4.yaml +++ b/concepts/concept-3.2.2.4.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: payment administration central system definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.1,central system,centre system}} that - allows an {{urn:iso:std:iso:14812:3.1.1.1,entity}} to manage financial transactions + - content: "{{<>,central system,centre system}} that + allows an {{<>,entity}} to manage financial transactions related to transportation, especially the electronic transfer of funds" notes: [] examples: [] diff --git a/concepts/concept-3.2.2.5.yaml b/concepts/concept-3.2.2.5.yaml index 89efd03..89ab37f 100644 --- a/concepts/concept-3.2.2.5.yaml +++ b/concepts/concept-3.2.2.5.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: public transport central management system definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.1,central system,centre system}} that - allows an {{urn:iso:std:iso:14812:3.1.1.1,entity}} to manage the activities - of a {{urn:iso:std:iso:14812:3.5.6.1,public transport}} agency" + - content: "{{<>,central system,centre system}} that + allows an {{<>,entity}} to manage the activities + of a {{<>,public transport}} agency" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.2.2.6.yaml b/concepts/concept-3.2.2.6.yaml index 5fdd116..1eb6e34 100644 --- a/concepts/concept-3.2.2.6.yaml +++ b/concepts/concept-3.2.2.6.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: traffic management central system definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.1,central system,centre system}} that - monitors and controls traffic and the {{urn:iso:std:iso:14812:3.3.5.2,road network}}" + - content: "{{<>,central system,centre system}} that + monitors and controls traffic and the {{<>,road network}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.2.2.7.yaml b/concepts/concept-3.2.2.7.yaml index abff2f0..2a39340 100644 --- a/concepts/concept-3.2.2.7.yaml +++ b/concepts/concept-3.2.2.7.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: traffic regulation central system definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.1,central system,centre system}} that + - content: "{{<>,central system,centre system}} that officially records traffic regulations in electronic form so that they can be distributed to other systems" notes: [] diff --git a/concepts/concept-3.2.2.8.yaml b/concepts/concept-3.2.2.8.yaml index dcb2dc5..de16c71 100644 --- a/concepts/concept-3.2.2.8.yaml +++ b/concepts/concept-3.2.2.8.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: transport information central system definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.1,central system,centre system}} that + - content: "{{<>,central system,centre system}} that provides information of interest to the travelling public" notes: [] examples: [] diff --git a/concepts/concept-3.2.3.1.yaml b/concepts/concept-3.2.3.1.yaml index a1cbc67..b1552cd 100644 --- a/concepts/concept-3.2.3.1.yaml +++ b/concepts/concept-3.2.3.1.yaml @@ -10,7 +10,7 @@ eng: normative_status: preferred designation: ITS field support equipment definition: - - content: portable {{urn:iso:std:iso:14812:3.2.1.2,field system}} used by field + - content: portable {{<>,field system}} used by field personnel to locally troubleshoot, initialize, reprogram and test infrastructure equipment notes: [] diff --git a/concepts/concept-3.2.3.2.yaml b/concepts/concept-3.2.3.2.yaml index 2c86b5e..c1d293f 100644 --- a/concepts/concept-3.2.3.2.yaml +++ b/concepts/concept-3.2.3.2.yaml @@ -10,15 +10,15 @@ eng: normative_status: preferred designation: ITS roadway equipment definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.2,field system}} that performs localized - {{urn:iso:std:iso:14812:3.5.3.1,ITS service,ITS services}}" + - content: "{{<>,field system}} that performs localized + {{<>,ITS service,ITS services}}" notes: - content: ITS services that can be performed by ITS roadside equipment include surveillance, traffic control, information provision, payment transaction services, and/or enforcement - content: '"ITS roadway equipment" is used within the current version of the Architecture Reference for Cooperative and Intelligent Transportation (ARC-IT; see Reference - <>). The term {{urn:iso:std:iso:14812:3.3.1.3,roadway}} has been revised + <>). The term {{<>,roadway}} has been revised to reflect that the equipment is typically along the roadway rather than a part of the roadway.' examples: diff --git a/concepts/concept-3.2.3.3.yaml b/concepts/concept-3.2.3.3.yaml index d917b16..439fcdd 100644 --- a/concepts/concept-3.2.3.3.yaml +++ b/concepts/concept-3.2.3.3.yaml @@ -16,10 +16,10 @@ eng: normative_status: admitted designation: connected vehicle roadside equipment definition: - - content: ITS {{urn:iso:std:iso:14812:3.2.3.2,ITS roadside equipment,roadside equipment}} - that perform {{urn:iso:std:iso:14812:3.5.3.1,ITS service,ITS services}} by exchanging - electronic {{urn:iso:std:iso:14812:3.1.11.5,message}} with nearby {{urn:iso:std:iso:14812:3.2.1.5,vehicle - system,vehicle systems}} and/or {{urn:iso:std:iso:14812:3.2.1.3,personal system,personal + - content: ITS {{<>,ITS roadside equipment,roadside equipment}} + that perform {{<>,ITS service,ITS services}} by exchanging + electronic {{<>,message}} with nearby {{<>,vehicle + system,vehicle systems}} and/or {{<>,personal system,personal systems}} via short-range wireless technologies notes: - content: Connected roadside equipment typically provides ITS-related functionality diff --git a/concepts/concept-3.2.3.4.yaml b/concepts/concept-3.2.3.4.yaml index 5e1522f..e47152f 100644 --- a/concepts/concept-3.2.3.4.yaml +++ b/concepts/concept-3.2.3.4.yaml @@ -13,9 +13,9 @@ eng: normative_status: preferred designation: RSU definition: - - content: part of {{urn:iso:std:iso:14812:3.2.3.3,connected roadside equipment}} - that provides wireless connectivity to {{urn:iso:std:iso:14812:3.2.1.5,vehicle - system,vehicle systems}} and/or {{urn:iso:std:iso:14812:3.2.1.3,personal system,personal + - content: part of {{<>,connected roadside equipment}} + that provides wireless connectivity to {{<>,vehicle + system,vehicle systems}} and/or {{<>,personal system,personal systems}} notes: [] examples: [] diff --git a/concepts/concept-3.2.3.5.yaml b/concepts/concept-3.2.3.5.yaml index c0b6f54..2418aac 100644 --- a/concepts/concept-3.2.3.5.yaml +++ b/concepts/concept-3.2.3.5.yaml @@ -10,7 +10,7 @@ eng: normative_status: preferred designation: ITS connected unit definition: - - content: electronic device that is {{urn:iso:std:iso:14812:3.2.3.6,connected}} + - content: electronic device that is {{<>,connected}} using one or more communication media notes: [] examples: [] diff --git a/concepts/concept-3.2.3.6.yaml b/concepts/concept-3.2.3.6.yaml index d15956b..07142a8 100644 --- a/concepts/concept-3.2.3.6.yaml +++ b/concepts/concept-3.2.3.6.yaml @@ -10,13 +10,13 @@ eng: normative_status: preferred designation: ITS connected definition: - - content: characteristic of a {{urn:iso:std:iso:14812:3.1.1.3,material entity}} + - content: characteristic of a {{<>,material entity}} that is equipped with enabled (i.e. on) and operational electronic communication - technologies to support {{urn:iso:std:iso:14812:3.5.3.1,ITS service,ITS services}}, + technologies to support {{<>,ITS service,ITS services}}, including the means to send and receive data to and from other connected entities notes: - content: The term "connected" does not imply support for any specific communications - interface or {{urn:iso:std:iso:14812:3.2.9.2,ITS-S application process}}. + interface or {{<>,ITS-S application process}}. examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.2.4.1.yaml b/concepts/concept-3.2.4.1.yaml index 1baa58e..da1e4e6 100644 --- a/concepts/concept-3.2.4.1.yaml +++ b/concepts/concept-3.2.4.1.yaml @@ -13,9 +13,9 @@ eng: normative_status: admitted designation: external in-vehicle device definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.3,personal system}} consisting of global - navigation satellite system (GNSS) and/or wireless {{urn:iso:std:iso:14812:3.1.8.7,module,modules}} - that are {{urn:iso:std:iso:14812:3.2.3.6,connected}} to a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} + - content: "{{<>,personal system}} consisting of global + navigation satellite system (GNSS) and/or wireless {{<>,module,modules}} + that are {{<>,connected}} to a {{<>,vehicle}} during a trip" notes: [] examples: [] diff --git a/concepts/concept-3.2.4.2.yaml b/concepts/concept-3.2.4.2.yaml index d65a222..fb7799f 100644 --- a/concepts/concept-3.2.4.2.yaml +++ b/concepts/concept-3.2.4.2.yaml @@ -10,8 +10,8 @@ eng: normative_status: preferred designation: ITS personal information device definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.3,personal system}} that enables personal - access to {{urn:iso:std:iso:14812:3.6.1.1,traveller}} information" + - content: "{{<>,personal system}} that enables personal + access to {{<>,traveller}} information" notes: [] examples: - content: Personal computer. diff --git a/concepts/concept-3.2.4.3.yaml b/concepts/concept-3.2.4.3.yaml index 18d8fe5..5488da6 100644 --- a/concepts/concept-3.2.4.3.yaml +++ b/concepts/concept-3.2.4.3.yaml @@ -10,8 +10,8 @@ eng: normative_status: preferred designation: ITS nomadic device definition: - - content: "{{urn:iso:std:iso:14812:3.2.4.2,personal information device}} that is - taken with and can be accessed by the {{urn:iso:std:iso:14812:3.6.1.1,traveller}} + - content: "{{<>,personal information device}} that is + taken with and can be accessed by the {{<>,traveller}} during a journey" notes: [] examples: diff --git a/concepts/concept-3.2.4.4.yaml b/concepts/concept-3.2.4.4.yaml index 5701871..dfd04bc 100644 --- a/concepts/concept-3.2.4.4.yaml +++ b/concepts/concept-3.2.4.4.yaml @@ -10,8 +10,8 @@ eng: normative_status: preferred designation: ITS public information device definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.3,personal system}} that provides {{urn:iso:std:iso:14812:3.5.8.2,commercial,public}} - access to {{urn:iso:std:iso:14812:3.6.1.1,traveller}} information" + - content: "{{<>,personal system}} that provides {{<>,commercial,public}} + access to {{<>,traveller}} information" notes: [] examples: - content: Kiosk. diff --git a/concepts/concept-3.2.5.1.yaml b/concepts/concept-3.2.5.1.yaml index 21d08b3..3fc68eb 100644 --- a/concepts/concept-3.2.5.1.yaml +++ b/concepts/concept-3.2.5.1.yaml @@ -10,8 +10,8 @@ eng: normative_status: preferred designation: CCMS definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.4,support system}} that enables trusted - communications among {{urn:iso:std:iso:14812:3.1.8.2,ITS component,ITS components}} + - content: "{{<>,support system}} that enables trusted + communications among {{<>,ITS component,ITS components}} and protects data from unauthorized access" notes: [] examples: [] diff --git a/concepts/concept-3.2.5.2.yaml b/concepts/concept-3.2.5.2.yaml index cf68f5f..3cb96dc 100644 --- a/concepts/concept-3.2.5.2.yaml +++ b/concepts/concept-3.2.5.2.yaml @@ -10,8 +10,8 @@ eng: normative_status: preferred designation: ITS map provision system definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.4,support system}} that provides map databases - used to support {{urn:iso:std:iso:14812:3.5.3.1,ITS service,ITS services}}" + - content: "{{<>,support system}} that provides map databases + used to support {{<>,ITS service,ITS services}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.2.6.1.yaml b/concepts/concept-3.2.6.1.yaml index 8558c36..24a8782 100644 --- a/concepts/concept-3.2.6.1.yaml +++ b/concepts/concept-3.2.6.1.yaml @@ -16,8 +16,8 @@ eng: normative_status: admitted designation: onboard equipment definition: - - content: "{{urn:iso:std:iso:14812:3.2.1.5,vehicle system}} that provides all ITS - functionality on-board the {{urn:iso:std:iso:14812:3.7.1.1,vehicle}}" + - content: "{{<>,vehicle system}} that provides all ITS + functionality on-board the {{<>,vehicle}}" notes: - content: ITS on-board equipment relates to any functionality. When there is a need to distinguish between core functionality and that by a special vehicle, diff --git a/concepts/concept-3.2.6.2.yaml b/concepts/concept-3.2.6.2.yaml index 69f62a1..49940a3 100644 --- a/concepts/concept-3.2.6.2.yaml +++ b/concepts/concept-3.2.6.2.yaml @@ -16,9 +16,9 @@ eng: normative_status: admitted designation: onboard unit definition: - - content: part of {{urn:iso:std:iso:14812:3.2.6.1,ITS on-board equipment,on-board - equipment}} that provides wireless connectivity to other {{urn:iso:std:iso:14812:3.1.8.2,ITS - component,ITS components}} external to the {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} + - content: part of {{<>,ITS on-board equipment,on-board + equipment}} that provides wireless connectivity to other {{<>,ITS + component,ITS components}} external to the {{<>,vehicle}} notes: - content: An OBU implementation can also include ITS functionality. examples: [] diff --git a/concepts/concept-3.2.7.1.yaml b/concepts/concept-3.2.7.1.yaml index 45d1efd..eef3d97 100644 --- a/concepts/concept-3.2.7.1.yaml +++ b/concepts/concept-3.2.7.1.yaml @@ -10,8 +10,8 @@ eng: normative_status: preferred designation: BSMD definition: - - content: abstract {{urn:iso:std:iso:14812:3.1.1.1,entity}} representing a managed - processing and memory {{urn:iso:std:iso:14812:3.1.3.11,environment}} that provides + - content: abstract {{<>,entity}} representing a managed + processing and memory {{<>,environment}} that provides protection from code and data that has not been determined to meet established security requirements notes: [] diff --git a/concepts/concept-3.2.7.2.yaml b/concepts/concept-3.2.7.2.yaml index 5f3e5da..61c1175 100644 --- a/concepts/concept-3.2.7.2.yaml +++ b/concepts/concept-3.2.7.2.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: ITS trust domain definition: - - content: set of {{urn:iso:std:iso:14812:3.2.7.1,bounded secured managed domain,bounded + - content: set of {{<>,bounded secured managed domain,bounded secured managed domains}} that meet a defined set of ITS industry security requirements notes: [] examples: [] diff --git a/concepts/concept-3.2.7.3.yaml b/concepts/concept-3.2.7.3.yaml index 9de9444..b2f9e19 100644 --- a/concepts/concept-3.2.7.3.yaml +++ b/concepts/concept-3.2.7.3.yaml @@ -10,8 +10,8 @@ eng: normative_status: preferred designation: ITS-S definition: - - content: "{{urn:iso:std:iso:14812:3.2.7.1,bounded secured managed domain}} that - is able to meet requirements of the {{urn:iso:std:iso:14812:3.2.7.2,ITS trust + - content: "{{<>,bounded secured managed domain}} that + is able to meet requirements of the {{<>,ITS trust domain}} within which it wishes to participate" notes: - content: The ITS station reference architecture is defined in <>. diff --git a/concepts/concept-3.2.7.4.yaml b/concepts/concept-3.2.7.4.yaml index 6e34210..a7e9cad 100644 --- a/concepts/concept-3.2.7.4.yaml +++ b/concepts/concept-3.2.7.4.yaml @@ -13,7 +13,7 @@ eng: normative_status: preferred designation: ITS-SU definition: - - content: instantiation of an {{urn:iso:std:iso:14812:3.2.7.3,ITS station}} + - content: instantiation of an {{<>,ITS station}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.2.7.5.yaml b/concepts/concept-3.2.7.5.yaml index b60eb53..0a230e9 100644 --- a/concepts/concept-3.2.7.5.yaml +++ b/concepts/concept-3.2.7.5.yaml @@ -13,8 +13,8 @@ eng: normative_status: preferred designation: ITS-SCU definition: - - content: physical unit in an {{urn:iso:std:iso:14812:3.2.7.4,ITS-S unit}} containing - part or all of the functionality of an {{urn:iso:std:iso:14812:3.2.7.3,ITS station,ITS-S}} + - content: physical unit in an {{<>,ITS-S unit}} containing + part or all of the functionality of an {{<>,ITS station,ITS-S}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.2.7.6.yaml b/concepts/concept-3.2.7.6.yaml index 031395c..48f74d0 100644 --- a/concepts/concept-3.2.7.6.yaml +++ b/concepts/concept-3.2.7.6.yaml @@ -10,9 +10,9 @@ eng: normative_status: preferred designation: ITS-S host definition: - - content: "{{urn:iso:std:iso:14812:3.2.7.3,ITS station,ITS-S}} functionalities - in an {{urn:iso:std:iso:14812:3.2.7.8,ITS-S node}} other than the functionalities - of an {{urn:iso:std:iso:14812:3.2.7.7,ITS-S router}}, ITS-S border router, ITS-S + - content: "{{<>,ITS station,ITS-S}} functionalities + in an {{<>,ITS-S node}} other than the functionalities + of an {{<>,ITS-S router}}, ITS-S border router, ITS-S mobile router or an ITS-S gateway" notes: - content: ITS-S border router and ITS-S mobile router are ITS-S routers with added diff --git a/concepts/concept-3.2.7.7.yaml b/concepts/concept-3.2.7.7.yaml index 1c24f95..ab13269 100644 --- a/concepts/concept-3.2.7.7.yaml +++ b/concepts/concept-3.2.7.7.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ITS-S router definition: - - content: "{{urn:iso:std:iso:14812:3.2.7.3,ITS station,ITS-S}} functionalities - in an {{urn:iso:std:iso:14812:3.2.7.8,ITS-S node}} that enable connecting two + - content: "{{<>,ITS station,ITS-S}} functionalities + in an {{<>,ITS-S node}} that enable connecting two networks and forwarding packets not explicitly addressed to the ITS-S node" notes: [] examples: [] diff --git a/concepts/concept-3.2.7.8.yaml b/concepts/concept-3.2.7.8.yaml index aeb8b62..fbb4a3a 100644 --- a/concepts/concept-3.2.7.8.yaml +++ b/concepts/concept-3.2.7.8.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: ITS-S node definition: - - content: "{{urn:iso:std:iso:14812:3.3.5.4,node}} comprised of a set of functionalities - in an {{urn:iso:std:iso:14812:3.2.7.4,ITS-S unit}} that is {{urn:iso:std:iso:14812:3.2.3.6,connected}} - to the {{urn:iso:std:iso:14812:3.2.7.3,ITS station}}-internal network or comprises + - content: "{{<>,node}} comprised of a set of functionalities + in an {{<>,ITS-S unit}} that is {{<>,connected}} + to the {{<>,ITS station}}-internal network or comprises an entire ITS-S unit" notes: [] examples: [] diff --git a/concepts/concept-3.2.8.1.yaml b/concepts/concept-3.2.8.1.yaml index 7e256cc..5b56d91 100644 --- a/concepts/concept-3.2.8.1.yaml +++ b/concepts/concept-3.2.8.1.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ITS application definition: - - content: realization of an {{urn:iso:std:iso:14812:3.5.3.1,ITS service}} that - involves an association of two or more complementary {{urn:iso:std:iso:14812:3.2.9.2,ITS-S + - content: realization of an {{<>,ITS service}} that + involves an association of two or more complementary {{<>,ITS-S application process,ITS-S application processes}} notes: [] examples: [] diff --git a/concepts/concept-3.2.8.2.yaml b/concepts/concept-3.2.8.2.yaml index f543ed0..cb00ef8 100644 --- a/concepts/concept-3.2.8.2.yaml +++ b/concepts/concept-3.2.8.2.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: interoperability design definition: - - content: characteristics necessary to fully define how various {{urn:iso:std:iso:14812:3.1.8.1,physical - object,physical objects}} interoperate to provide a {{urn:iso:std:iso:14812:3.5.2.1,service}} + - content: characteristics necessary to fully define how various {{<>,physical + object,physical objects}} interoperate to provide a {{<>,service}} notes: - content: Characteristics often include but are not limited to functional, performance and interface requirements. diff --git a/concepts/concept-3.2.8.3.yaml b/concepts/concept-3.2.8.3.yaml index 115098e..00b40e8 100644 --- a/concepts/concept-3.2.8.3.yaml +++ b/concepts/concept-3.2.8.3.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: ITS application specification definition: - - content: one or more {{urn:iso:std:iso:14812:3.1.6.3,document,documents}} that - detail the {{urn:iso:std:iso:14812:3.2.8.2,interoperability design}} for an - {{urn:iso:std:iso:14812:3.2.8.1,ITS application}} + - content: one or more {{<>,document,documents}} that + detail the {{<>,interoperability design}} for an + {{<>,ITS application}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.2.8.4.yaml b/concepts/concept-3.2.8.4.yaml index e193c65..9ab1409 100644 --- a/concepts/concept-3.2.8.4.yaml +++ b/concepts/concept-3.2.8.4.yaml @@ -10,7 +10,7 @@ eng: normative_status: preferred designation: ITS application template definition: - - content: defined annotated outline for an {{urn:iso:std:iso:14812:3.2.8.3,ITS + - content: defined annotated outline for an {{<>,ITS application specification}} notes: [] examples: [] diff --git a/concepts/concept-3.2.8.5.yaml b/concepts/concept-3.2.8.5.yaml index 048dcf3..e353f84 100644 --- a/concepts/concept-3.2.8.5.yaml +++ b/concepts/concept-3.2.8.5.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ITS implementation definition: - - content: integration of each {{urn:iso:std:iso:14812:3.1.8.1,physical object}} - necessary to implement one or more {{urn:iso:std:iso:14812:3.2.8.1,ITS application,ITS + - content: integration of each {{<>,physical object}} + necessary to implement one or more {{<>,ITS application,ITS applications}} notes: - content: An ITS application typically requires multiple components (e.g. an ITS-S @@ -16,7 +16,7 @@ eng: includes a sample of each component necessary for the service but often does not represent a complete deployment. - content: An ITS implementation is typically used for a laboratory or other experimental - {{urn:iso:std:iso:14812:3.1.3.11,environment}} prior to a full-scale deployment. + {{<>,environment}} prior to a full-scale deployment. examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.2.8.6.yaml b/concepts/concept-3.2.8.6.yaml index 2a0700c..35503d8 100644 --- a/concepts/concept-3.2.8.6.yaml +++ b/concepts/concept-3.2.8.6.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: ITS deployment definition: - - content: installation capable of performing one or more {{urn:iso:std:iso:14812:3.2.8.1,ITS + - content: installation capable of performing one or more {{<>,ITS application,ITS applications}} notes: - content: An ITS deployment typically refers to the support, central and roadside diff --git a/concepts/concept-3.2.9.1.yaml b/concepts/concept-3.2.9.1.yaml index 3c3fa18..f891252 100644 --- a/concepts/concept-3.2.9.1.yaml +++ b/concepts/concept-3.2.9.1.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: ITS application role definition: - - content: "{{urn:iso:std:iso:14812:3.5.4.4,ITS-S user need}} expressed as a formal + - content: "{{<>,ITS-S user need}} expressed as a formal set of interoperability requirements that need to be fulfilled to satisfy a - portion of functionality of an {{urn:iso:std:iso:14812:3.2.8.1,ITS application}}" + portion of functionality of an {{<>,ITS application}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.2.9.2.yaml b/concepts/concept-3.2.9.2.yaml index c6797a7..25b0290 100644 --- a/concepts/concept-3.2.9.2.yaml +++ b/concepts/concept-3.2.9.2.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ITS-S application process definition: - - content: "{{urn:iso:std:iso:14812:3.1.3.10,element}} in an {{urn:iso:std:iso:14812:3.2.7.3,ITS - station}} that performs information processing for an {{urn:iso:std:iso:14812:3.5.4.1,ITS-S + - content: "{{<>,element}} in an {{<>,ITS + station}} that performs information processing for an {{<>,ITS-S service}}" notes: [] examples: [] diff --git a/concepts/concept-3.2.9.3.yaml b/concepts/concept-3.2.9.3.yaml index 5d8a023..f40a593 100644 --- a/concepts/concept-3.2.9.3.yaml +++ b/concepts/concept-3.2.9.3.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ITS-S application definition: - - content: "{{urn:iso:std:iso:14812:3.2.9.2,ITS-S application process}} residing - in the {{urn:iso:std:iso:14812:3.1.5.1,application entity}}" + - content: "{{<>,ITS-S application process}} residing + in the {{<>,application entity}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.2.9.4.yaml b/concepts/concept-3.2.9.4.yaml index 172ce94..0ec88b4 100644 --- a/concepts/concept-3.2.9.4.yaml +++ b/concepts/concept-3.2.9.4.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ITS-S application implementation definition: - - content: implementation of an {{urn:iso:std:iso:14812:3.2.9.2,ITS-S application - process}} within the {{urn:iso:std:iso:14812:3.1.5.1,application entity}} + - content: implementation of an {{<>,ITS-S application + process}} within the {{<>,application entity}} notes: - content: An implementation is typically associated with an implementation name, a version and release number. diff --git a/concepts/concept-3.2.9.5.yaml b/concepts/concept-3.2.9.5.yaml index 9c2b4b0..33c0d4c 100644 --- a/concepts/concept-3.2.9.5.yaml +++ b/concepts/concept-3.2.9.5.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ITS-S application process installation definition: - - content: installation of an implementation of an {{urn:iso:std:iso:14812:3.2.9.2,ITS-S - application process}} on an {{urn:iso:std:iso:14812:3.2.7.3,ITS station}} + - content: installation of an implementation of an {{<>,ITS-S + application process}} on an {{<>,ITS station}} notes: - content: An implementation is typically associated with an implementation name, a version and release number. diff --git a/concepts/concept-3.2.9.6.yaml b/concepts/concept-3.2.9.6.yaml index 1f1793e..61ee6b5 100644 --- a/concepts/concept-3.2.9.6.yaml +++ b/concepts/concept-3.2.9.6.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ITS-S application installation definition: - - content: "{{urn:iso:std:iso:14812:3.2.9.5,ITS-S application process installation}} - within the {{urn:iso:std:iso:14812:3.1.5.1,application entity}}" + - content: "{{<>,ITS-S application process installation}} + within the {{<>,application entity}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.3.1.1.yaml b/concepts/concept-3.3.1.1.yaml index ef6c724..68366ae 100644 --- a/concepts/concept-3.3.1.1.yaml +++ b/concepts/concept-3.3.1.1.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: cross-section definition: - - content: transverse view of {{urn:iso:std:iso:14812:3.3.5.1,road}} geometry + - content: transverse view of {{<>,road}} geometry notes: - - content: The transverse view provides a vertical section of the ground and {{urn:iso:std:iso:14812:3.3.1.5,carriageway}} + - content: The transverse view provides a vertical section of the ground and {{<>,carriageway}} at right angles to the centre line of the carriageway. examples: - content: "<>." diff --git a/concepts/concept-3.3.1.10.yaml b/concepts/concept-3.3.1.10.yaml index 513ae14..f25fc29 100644 --- a/concepts/concept-3.3.1.10.yaml +++ b/concepts/concept-3.3.1.10.yaml @@ -7,11 +7,11 @@ eng: normative_status: preferred designation: roadside definition: - - content: portion of the {{urn:iso:std:iso:14812:3.3.1.2,road reservation}} excluding - all {{urn:iso:std:iso:14812:3.3.1.3,roadway}} and {{urn:iso:std:iso:14812:3.3.1.4,driving + - content: portion of the {{<>,road reservation}} excluding + all {{<>,roadway}} and {{<>,driving space,driving space(s)}} notes: - - content: Roadside, {{urn:iso:std:iso:14812:3.3.1.18,shoulder}} and {{urn:iso:std:iso:14812:3.3.1.11,verge}} + - content: Roadside, {{<>,shoulder}} and {{<>,verge}} define similar but slightly different concepts examples: [] language_code: eng diff --git a/concepts/concept-3.3.1.11.yaml b/concepts/concept-3.3.1.11.yaml index e075179..abd6a5b 100644 --- a/concepts/concept-3.3.1.11.yaml +++ b/concepts/concept-3.3.1.11.yaml @@ -7,13 +7,13 @@ eng: normative_status: preferred designation: verge definition: - - content: unpaved part of the {{urn:iso:std:iso:14812:3.3.1.10,roadside}} designed + - content: unpaved part of the {{<>,roadside}} designed for travel safety purposes notes: - - content: A verge can separate two {{urn:iso:std:iso:14812:3.3.1.13,lane,lanes}} - of different modes, separate a {{urn:iso:std:iso:14812:3.3.1.13,traffic lane}} + - content: A verge can separate two {{<>,lane,lanes}} + of different modes, separate a {{<>,traffic lane}} from a ditch, or separate a lane from another safety hazard. - - content: Roadside, {{urn:iso:std:iso:14812:3.3.1.18,shoulder}} and verge define + - content: Roadside, {{<>,shoulder}} and verge define similar but slightly different concepts. examples: [] language_code: eng diff --git a/concepts/concept-3.3.1.12.yaml b/concepts/concept-3.3.1.12.yaml index 918266d..a496236 100644 --- a/concepts/concept-3.3.1.12.yaml +++ b/concepts/concept-3.3.1.12.yaml @@ -11,19 +11,19 @@ eng: designation: generic lane domain: generic definition: - - content: portion of {{urn:iso:std:iso:14812:3.3.1.2,road reservation}} intended - to accommodate a single line of moving {{urn:iso:std:iso:14812:3.1.1.3,material + - content: portion of {{<>,road reservation}} intended + to accommodate a single line of moving {{<>,material entity,material entities}} along its length notes: - - content: "{{urn:iso:std:iso:14812:3.3.1.13,lane,Lanes}} are often bounded by lane + - content: "{{<>,lane,Lanes}} are often bounded by lane markings." - content: Lanes may be significantly wider than the normal vehicle width to allow variance in lane position of the vehicle as well as for various vehicle dimensions. - - content: The "lane" nomenclature typically refers to {{urn:iso:std:iso:14812:3.7.6.3,motor - vehicle}} usage, but can also refer to other purposes, such as {{urn:iso:std:iso:14812:3.3.3.4,sidewalk,sidewalks}}. + - content: The "lane" nomenclature typically refers to {{<>,motor + vehicle}} usage, but can also refer to other purposes, such as {{<>,sidewalk,sidewalks}}. examples: - - content: "{{urn:iso:std:iso:14812:3.3.1.13,traffic lane,Traffic lane}}, {{urn:iso:std:iso:14812:3.3.3.1,cycle - lane}}, {{urn:iso:std:iso:14812:3.3.3.4,sidewalk}}." + - content: "{{<>,traffic lane,Traffic lane}}, {{<>,cycle + lane}}, {{<>,sidewalk}}." language_code: eng entry_status: valid sources: diff --git a/concepts/concept-3.3.1.13.yaml b/concepts/concept-3.3.1.13.yaml index dfcb661..6ba4247 100644 --- a/concepts/concept-3.3.1.13.yaml +++ b/concepts/concept-3.3.1.13.yaml @@ -10,13 +10,13 @@ eng: normative_status: preferred designation: lane definition: - - content: portion of {{urn:iso:std:iso:14812:3.3.1.5,carriageway}} designed to - accommodate a single line of moving {{urn:iso:std:iso:14812:3.7.6.1,road vehicle,road + - content: portion of {{<>,carriageway}} designed to + accommodate a single line of moving {{<>,road vehicle,road vehicles}} notes: - content: The term "lane" is often used to refer to a "traffic lane" when the context is known to be "traffic". - - content: A traffic lane can be bi-directional, such as a single lane {{urn:iso:std:iso:14812:3.3.5.1,road}}, + - content: A traffic lane can be bi-directional, such as a single lane {{<>,road}}, a two-way turn/overtaking lane, or a reversible flow lane. - content: Some jurisdictions allow supplemental uses of a traffic lane, such as multiple motorcycles sharing the width of a traffic lane or allowing a bicycle diff --git a/concepts/concept-3.3.1.14.yaml b/concepts/concept-3.3.1.14.yaml index 27401ec..a98027f 100644 --- a/concepts/concept-3.3.1.14.yaml +++ b/concepts/concept-3.3.1.14.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: reserved lane definition: - - content: "{{urn:iso:std:iso:14812:3.3.1.13,traffic lane}} restricted to a specific - subset of {{urn:iso:std:iso:14812:3.7.6.1,road vehicle,road vehicles}} or {{urn:iso:std:iso:14812:3.5.3.4,user}} + - content: "{{<>,traffic lane}} restricted to a specific + subset of {{<>,road vehicle,road vehicles}} or {{<>,user}} categories" notes: - content: A traffic lane may be reserved permanently or under certain conditions diff --git a/concepts/concept-3.3.1.15.yaml b/concepts/concept-3.3.1.15.yaml index 6b9e6ac..8fb2bfe 100644 --- a/concepts/concept-3.3.1.15.yaml +++ b/concepts/concept-3.3.1.15.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: usable width definition: - - content: all {{urn:iso:std:iso:14812:3.3.1.13,traffic lane,traffic lanes}} of - a {{urn:iso:std:iso:14812:3.3.1.5,carriageway}} + - content: all {{<>,traffic lane,traffic lanes}} of + a {{<>,carriageway}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.3.1.16.yaml b/concepts/concept-3.3.1.16.yaml index 55fc337..e26ac96 100644 --- a/concepts/concept-3.3.1.16.yaml +++ b/concepts/concept-3.3.1.16.yaml @@ -7,14 +7,14 @@ eng: normative_status: preferred designation: lay-by definition: - - content: short length of paved {{urn:iso:std:iso:14812:3.3.1.5,carriageway}} at - its edge designed to allow a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} to draw - out of the {{urn:iso:std:iso:14812:3.3.1.13,traffic lane,traffic lanes}} and + - content: short length of paved {{<>,carriageway}} at + its edge designed to allow a {{<>,vehicle}} to draw + out of the {{<>,traffic lane,traffic lanes}} and stop temporarily notes: - - content: Lay-bys are not part of a {{urn:iso:std:iso:14812:3.3.1.19,hard shoulder}}. + - content: Lay-bys are not part of a {{<>,hard shoulder}}. - content: Lay-bys can be used for emergency situations, picking up/dropping off - {{urn:iso:std:iso:14812:3.6.2.1,passenger,passengers}}, etc. + {{<>,passenger,passengers}}, etc. examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.3.1.17.yaml b/concepts/concept-3.3.1.17.yaml index e469b3b..09cb6a4 100644 --- a/concepts/concept-3.3.1.17.yaml +++ b/concepts/concept-3.3.1.17.yaml @@ -7,12 +7,12 @@ eng: normative_status: preferred designation: hardstanding definition: - - content: part of a paved {{urn:iso:std:iso:14812:3.3.1.5,carriageway}} that is - not a {{urn:iso:std:iso:14812:3.3.1.13,traffic lane}}, {{urn:iso:std:iso:14812:3.3.1.19,hard - shoulder}}, or {{urn:iso:std:iso:14812:3.3.1.16,lay-by}}. + - content: part of a paved {{<>,carriageway}} that is + not a {{<>,traffic lane}}, {{<>,hard + shoulder}}, or {{<>,lay-by}}. notes: - content: Hardstanding can include edges of a hard shoulder outside of designated - lane markings, slips for future connector {{urn:iso:std:iso:14812:3.3.5.1,road,roads}}, + lane markings, slips for future connector {{<>,road,roads}}, etc. examples: - content: See <>. diff --git a/concepts/concept-3.3.1.18.yaml b/concepts/concept-3.3.1.18.yaml index f950dcb..c361dca 100644 --- a/concepts/concept-3.3.1.18.yaml +++ b/concepts/concept-3.3.1.18.yaml @@ -7,13 +7,13 @@ eng: normative_status: preferred designation: shoulder definition: - - content: either a {{urn:iso:std:iso:14812:3.3.1.19,hard shoulder}} or a {{urn:iso:std:iso:14812:3.3.1.20,soft + - content: either a {{<>,hard shoulder}} or a {{<>,soft shoulder}} notes: - content: In some jurisdictions, a shoulder can be used for emergency stops and/or other purposes in addition to providing a clear zone for safety purposes. - - content: "{{urn:iso:std:iso:14812:3.3.1.10,roadside,Roadside}}, shoulder, and - {{urn:iso:std:iso:14812:3.3.1.11,verge}} define similar but slightly different + - content: "{{<>,roadside,Roadside}}, shoulder, and + {{<>,verge}} define similar but slightly different concepts" examples: [] language_code: eng diff --git a/concepts/concept-3.3.1.19.yaml b/concepts/concept-3.3.1.19.yaml index 69a1bcc..d06f2d8 100644 --- a/concepts/concept-3.3.1.19.yaml +++ b/concepts/concept-3.3.1.19.yaml @@ -7,10 +7,10 @@ eng: normative_status: preferred designation: hard shoulder definition: - - content: part of the paved {{urn:iso:std:iso:14812:3.3.1.5,carriageway}} designed + - content: part of the paved {{<>,carriageway}} designed to support traffic loads but not normally intended for driving notes: - - content: A hard shoulder can be narrow or wide enough for a {{urn:iso:std:iso:14812:3.3.1.13,traffic + - content: A hard shoulder can be narrow or wide enough for a {{<>,traffic lane}}. - content: A hard shoulder can have a surface that discourages usage as a driving surface in some countries. diff --git a/concepts/concept-3.3.1.2.yaml b/concepts/concept-3.3.1.2.yaml index bdf6f3d..bf02aa0 100644 --- a/concepts/concept-3.3.1.2.yaml +++ b/concepts/concept-3.3.1.2.yaml @@ -10,15 +10,15 @@ eng: normative_status: preferred designation: easement definition: - - content: area legally reserved for {{urn:iso:std:iso:14812:3.3.5.1,road}} transport + - content: area legally reserved for {{<>,road}} transport purposes and support notes: - content: Support includes physical equipment such as safety devices, signage and controller cabinets as well as access by maintenance vehicles and personnel. - - content: The road reservation includes all {{urn:iso:std:iso:14812:3.3.1.5,carriageway,carriageways}} - as well as width to allow for {{urn:iso:std:iso:14812:3.3.1.10,roadside}} devices, - {{urn:iso:std:iso:14812:3.3.1.18,shoulder,shoulders}}, {{urn:iso:std:iso:14812:3.3.1.11,verge,verges}}, - {{urn:iso:std:iso:14812:3.3.3.3,footway,footways}}, drainage facilities, sound + - content: The road reservation includes all {{<>,carriageway,carriageways}} + as well as width to allow for {{<>,roadside}} devices, + {{<>,shoulder,shoulders}}, {{<>,verge,verges}}, + {{<>,footway,footways}}, drainage facilities, sound walls, slopes, embankments, etc. examples: [] language_code: eng diff --git a/concepts/concept-3.3.1.20.yaml b/concepts/concept-3.3.1.20.yaml index 5bd1bbf..ba03e4f 100644 --- a/concepts/concept-3.3.1.20.yaml +++ b/concepts/concept-3.3.1.20.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: soft shoulder definition: - - content: unpaved part of the {{urn:iso:std:iso:14812:3.3.1.2,road reservation}} - not belonging to the {{urn:iso:std:iso:14812:3.3.1.5,carriageway}} but providing + - content: unpaved part of the {{<>,road reservation}} + not belonging to the {{<>,carriageway}} but providing lateral support to it notes: - content: Soft shoulders are not normally intended for driving. diff --git a/concepts/concept-3.3.1.3.yaml b/concepts/concept-3.3.1.3.yaml index a38694d..fee09a2 100644 --- a/concepts/concept-3.3.1.3.yaml +++ b/concepts/concept-3.3.1.3.yaml @@ -7,23 +7,23 @@ eng: normative_status: preferred designation: roadway definition: - - content: part of the surface of the {{urn:iso:std:iso:14812:3.3.1.2,road reservation}} - primarily designed for the movement of {{urn:iso:std:iso:14812:3.7.1.1,vehicle,vehicles}} + - content: part of the surface of the {{<>,road reservation}} + primarily designed for the movement of {{<>,vehicle,vehicles}} that conform to a specified set of requirements notes: - - content: A roadway is characterized using a {{urn:iso:std:iso:14812:3.3.1.1,cross-section}} + - content: A roadway is characterized using a {{<>,cross-section}} of a road facility as the roadway characteristics often change along the length - of the road. See "{{urn:iso:std:iso:14812:3.3.5.1,road}}", "{{urn:iso:std:iso:14812:3.3.5.7,road - section}}", "{{urn:iso:std:iso:14812:3.3.5.8,road segment}}", and "{{urn:iso:std:iso:14812:3.3.5.6,road + of the road. See "{{<>,road}}", "{{<>,road + section}}", "{{<>,road segment}}", and "{{<>,road link,road links}}" for different types of stretches of roadway. - content: In practice, the roadway design considers a variety of issues, which can result in suboptimal road segments that violate normal design guidelines. - Such {{urn:iso:std:iso:14812:3.4.1.1,location,locations}} are typically posted + Such {{<>,location,locations}} are typically posted with warning signs, but they are still designed for the movement of vehicles. - content: While the roadway is designed with certain vehicle characteristics in mind, local regulations typically allow a wider set of vehicles to use the roadway. - - content: The roadway includes any contiguous {{urn:iso:std:iso:14812:3.3.1.19,hard - shoulder}}, {{urn:iso:std:iso:14812:3.3.1.17,hardstanding}} and {{urn:iso:std:iso:14812:3.3.1.14,reserved + - content: The roadway includes any contiguous {{<>,hard + shoulder}}, {{<>,hardstanding}} and {{<>,reserved lane,reserved lanes}}. examples: [] language_code: eng diff --git a/concepts/concept-3.3.1.4.yaml b/concepts/concept-3.3.1.4.yaml index 08709ad..6911ea5 100644 --- a/concepts/concept-3.3.1.4.yaml +++ b/concepts/concept-3.3.1.4.yaml @@ -7,12 +7,12 @@ eng: normative_status: preferred designation: driving space definition: - - content: area above the {{urn:iso:std:iso:14812:3.3.1.3,roadway}} that is primarily - designed for the movement of {{urn:iso:std:iso:14812:3.7.1.1,vehicle,vehicles}} + - content: area above the {{<>,roadway}} that is primarily + designed for the movement of {{<>,vehicle,vehicles}} notes: - content: In practice, the driving space design considers a variety of issues, - which can result in suboptimal {{urn:iso:std:iso:14812:3.3.5.1,road}} segments - that violate normal design guidelines. Such {{urn:iso:std:iso:14812:3.4.1.1,location,locations}} + which can result in suboptimal {{<>,road}} segments + that violate normal design guidelines. Such {{<>,location,locations}} are typically posted with warning signs, but they are still designed for the movement of vehicles. - content: While the driving space is designed with certain vehicle characteristics diff --git a/concepts/concept-3.3.1.5.yaml b/concepts/concept-3.3.1.5.yaml index 71562c0..34b9995 100644 --- a/concepts/concept-3.3.1.5.yaml +++ b/concepts/concept-3.3.1.5.yaml @@ -7,16 +7,16 @@ eng: normative_status: preferred designation: carriageway definition: - - content: contiguous area of {{urn:iso:std:iso:14812:3.3.1.3,roadway}} along a - {{urn:iso:std:iso:14812:3.3.5.8,road segment}} + - content: contiguous area of {{<>,roadway}} along a + {{<>,road segment}} notes: - - content: A carriageway is comprised of one or more traffic {{urn:iso:std:iso:14812:3.3.1.13,traffic - lane,lanes}} [i.e. the {{urn:iso:std:iso:14812:3.3.1.15,usable width}}] and - could include {{urn:iso:std:iso:14812:3.3.1.18,shoulder,shoulders}} and {{urn:iso:std:iso:14812:3.3.1.16,lay-by,lay-bys}}. - - content: Carriageways are separated by {{urn:iso:std:iso:14812:3.3.2.1,physical + - content: A carriageway is comprised of one or more traffic {{<>,traffic + lane,lanes}} [i.e. the {{<>,usable width}}] and + could include {{<>,shoulder,shoulders}} and {{<>,lay-by,lay-bys}}. + - content: Carriageways are separated by {{<>,physical traffic separator,physical traffic separators}}. - - content: When looking at a {{urn:iso:std:iso:14812:3.3.1.1,cross-section}} of - the {{urn:iso:std:iso:14812:3.3.1.2,road reservation}}, the roadway consists + - content: When looking at a {{<>,cross-section}} of + the {{<>,road reservation}}, the roadway consists of all of the carriageways. examples: [] language_code: eng diff --git a/concepts/concept-3.3.1.6.yaml b/concepts/concept-3.3.1.6.yaml index 46754bb..5aec9f3 100644 --- a/concepts/concept-3.3.1.6.yaml +++ b/concepts/concept-3.3.1.6.yaml @@ -7,19 +7,19 @@ eng: normative_status: preferred designation: travelled way definition: - - content: part of the {{urn:iso:std:iso:14812:3.3.1.3,roadway}} that is currently + - content: part of the {{<>,roadway}} that is currently intended for transport purposes notes: - - content: The travelled way does not include {{urn:iso:std:iso:14812:3.3.1.19,hard - shoulder,hard shoulders}}, {{urn:iso:std:iso:14812:3.3.1.17,hardstanding}}, + - content: The travelled way does not include {{<>,hard + shoulder,hard shoulders}}, {{<>,hardstanding}}, or other areas that are not currently intended for normal operational use. In other words, while these other areas are "designed" for transport purposes, they are not "intended" for normal transport purposes (at present); rather these extra areas exist for safety and other exceptional use conditions. - content: While the limits of the roadway are defined by the design of the physical infrastructure and are generally static; the limits of the travelled way can - be dynamic, such as in the case of a {{urn:iso:std:iso:14812:3.3.4.1,hard shoulder - for emergency use}} being converted into {{urn:iso:std:iso:14812:3.3.4.2,hard + be dynamic, such as in the case of a {{<>,hard shoulder + for emergency use}} being converted into {{<>,hard shoulder running}} operation. examples: [] language_code: eng diff --git a/concepts/concept-3.3.1.7.yaml b/concepts/concept-3.3.1.7.yaml index bd7f231..29452a6 100644 --- a/concepts/concept-3.3.1.7.yaml +++ b/concepts/concept-3.3.1.7.yaml @@ -16,14 +16,14 @@ eng: normative_status: admitted designation: undivided highway definition: - - content: "{{urn:iso:std:iso:14812:3.3.1.3,roadway}} comprised of exactly one {{urn:iso:std:iso:14812:3.3.1.5,carriageway}}" + - content: "{{<>,roadway}} comprised of exactly one {{<>,carriageway}}" notes: - content: 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. - - content: A single carriageway road segment could have multiple {{urn:iso:std:iso:14812:3.3.1.13,lane,lanes}} + - content: A single carriageway road segment could have multiple {{<>,lane,lanes}} and could allow travel in opposite directions - content: The term "undivided highway" is the equivalent American English term. examples: [] diff --git a/concepts/concept-3.3.1.8.yaml b/concepts/concept-3.3.1.8.yaml index d7b1e4f..f4b29a2 100644 --- a/concepts/concept-3.3.1.8.yaml +++ b/concepts/concept-3.3.1.8.yaml @@ -16,7 +16,7 @@ eng: normative_status: admitted designation: dual carriageway definition: - - content: "{{urn:iso:std:iso:14812:3.3.1.3,roadway}} comprised of exactly two {{urn:iso:std:iso:14812:3.3.1.5,carriageway,carriageways}}" + - content: "{{<>,roadway}} comprised of exactly two {{<>,carriageway,carriageways}}" notes: - content: The PIARC term is "dual carriageway road" and is recognized as a preferred term. As per the definitions provided in this document, "dual carriageway road diff --git a/concepts/concept-3.3.1.9.yaml b/concepts/concept-3.3.1.9.yaml index dfe0b4f..087dd14 100644 --- a/concepts/concept-3.3.1.9.yaml +++ b/concepts/concept-3.3.1.9.yaml @@ -13,11 +13,11 @@ eng: normative_status: admitted designation: multiple carriageway definition: - - content: "{{urn:iso:std:iso:14812:3.3.1.3,roadway}} comprised of more than two - {{urn:iso:std:iso:14812:3.3.1.5,carriageway,carriageways}}" + - content: "{{<>,roadway}} comprised of more than two + {{<>,carriageway,carriageways}}" notes: - content: The PIARC term is "multiple carriageway road" and is recognized as a - preferred term. As per the definitions provided in this document, "{{urn:iso:std:iso:14812:3.3.1.8,dual + preferred term. As per the definitions provided in this document, "{{<>,dual carriageway road segment}}" is more accurate and is the most preferred term. The term "dual carriageway" by itself is not preferred but admitted. - content: The separate carriageways are typically designed for separate traffic diff --git a/concepts/concept-3.3.2.1.yaml b/concepts/concept-3.3.2.1.yaml index 124be01..c795f3e 100644 --- a/concepts/concept-3.3.2.1.yaml +++ b/concepts/concept-3.3.2.1.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: physical traffic separator definition: - - content: mechanism used to physically separate {{urn:iso:std:iso:14812:3.3.1.5,carriageway,carriageways}} + - content: mechanism used to physically separate {{<>,carriageway,carriageways}} notes: - content: Mechanisms include various types of barriers, such as walls, rails, pylons, kerbs and ditches, as well as open, unpaved space. If two streams of traffic diff --git a/concepts/concept-3.3.2.2.yaml b/concepts/concept-3.3.2.2.yaml index bd9f2ed..32e078f 100644 --- a/concepts/concept-3.3.2.2.yaml +++ b/concepts/concept-3.3.2.2.yaml @@ -16,8 +16,8 @@ eng: normative_status: admitted designation: neutral ground definition: - - content: part of the {{urn:iso:std:iso:14812:3.3.1.2,road reservation}} between - {{urn:iso:std:iso:14812:3.3.1.5,carriageway,carriageways}} designed for travel + - content: part of the {{<>,road reservation}} between + {{<>,carriageway,carriageways}} designed for travel safety purposes notes: - content: A central reservation can be paved or unpaved and can be equipped with diff --git a/concepts/concept-3.3.2.3.yaml b/concepts/concept-3.3.2.3.yaml index a5dc2e9..080c121 100644 --- a/concepts/concept-3.3.2.3.yaml +++ b/concepts/concept-3.3.2.3.yaml @@ -13,9 +13,9 @@ eng: normative_status: admitted designation: concrete barrier definition: - - content: "{{urn:iso:std:iso:14812:3.3.2.1,physical traffic separator}} that consists - of a wall with a wide, sloped base designed to divert {{urn:iso:std:iso:14812:3.7.1.1,vehicle,vehicles}} - back into their {{urn:iso:std:iso:14812:3.3.1.13,traffic lane}}" + - content: "{{<>,physical traffic separator}} that consists + of a wall with a wide, sloped base designed to divert {{<>,vehicle,vehicles}} + back into their {{<>,traffic lane}}" notes: - content: Jersey barriers are typically modular. They are typically made of concrete but can also be made with other materials such as plastic filled with water diff --git a/concepts/concept-3.3.3.1.yaml b/concepts/concept-3.3.3.1.yaml index b005cc7..b5a9bb2 100644 --- a/concepts/concept-3.3.3.1.yaml +++ b/concepts/concept-3.3.3.1.yaml @@ -7,14 +7,14 @@ eng: normative_status: preferred designation: cycle lane definition: - - content: "{{urn:iso:std:iso:14812:3.3.1.13,lane}} designed for the through movement + - content: "{{<>,lane}} designed for the through movement of cycles" notes: - - content: Cycle lanes are typically much narrower than {{urn:iso:std:iso:14812:3.3.1.13,traffic + - content: Cycle lanes are typically much narrower than {{<>,traffic lane,traffic lanes}}. - - content: Cycle lanes are typically part of either a {{urn:iso:std:iso:14812:3.3.1.15,usable - width,carriageway}} or a {{urn:iso:std:iso:14812:3.3.3.2,cycleway}}. - - content: Cycle lanes could also allow and be designed for {{urn:iso:std:iso:14812:3.7.6.2,motorized + - content: Cycle lanes are typically part of either a {{<>,usable + width,carriageway}} or a {{<>,cycleway}}. + - content: Cycle lanes could also allow and be designed for {{<>,motorized vehicle,motorized vehicles}} (e.g. e-scooters, mopeds, etc.) with similar performance characteristics as human-powered cycles, subject to local regulations. examples: [] diff --git a/concepts/concept-3.3.3.2.yaml b/concepts/concept-3.3.3.2.yaml index 377c644..719d895 100644 --- a/concepts/concept-3.3.3.2.yaml +++ b/concepts/concept-3.3.3.2.yaml @@ -11,11 +11,11 @@ eng: designation: cycle track definition: - content: infrastructure primarily designed for the use of cycles and separate - from a {{urn:iso:std:iso:14812:3.3.1.5,carriageway}} + from a {{<>,carriageway}} notes: - - content: Local legislation can allow cycleways to be used by a variety of {{urn:iso:std:iso:14812:3.7.5.2,low-speed + - content: Local legislation can allow cycleways to be used by a variety of {{<>,low-speed vehicle,low-speed vehicles}} (e.g. low-speed scooters, skateboards, etc.) and - can share usage of other low-speed modes such as {{urn:iso:std:iso:14812:3.6.1.3,pedestrian,pedestrians}}, + can share usage of other low-speed modes such as {{<>,pedestrian,pedestrians}}, horseback riders, etc. examples: [] language_code: eng diff --git a/concepts/concept-3.3.3.3.yaml b/concepts/concept-3.3.3.3.yaml index fff87e6..96551a1 100644 --- a/concepts/concept-3.3.3.3.yaml +++ b/concepts/concept-3.3.3.3.yaml @@ -13,12 +13,12 @@ eng: normative_status: admitted designation: pavement definition: - - content: "{{urn:iso:std:iso:14812:3.3.1.13,lane}} primarily designed for the movement - of {{urn:iso:std:iso:14812:3.6.1.3,pedestrian,pedestrians}}" + - content: "{{<>,lane}} primarily designed for the movement + of {{<>,pedestrian,pedestrians}}" notes: - content: A paved footway is called a "pavement" in British English. - content: Regulations typically allow footways to be used by other ultra-low speed - {{urn:iso:std:iso:14812:3.5.3.4,user,users}}, such as the users of wheelchairs + {{<>,user,users}}, such as the users of wheelchairs and strollers. examples: [] language_code: eng diff --git a/concepts/concept-3.3.3.4.yaml b/concepts/concept-3.3.3.4.yaml index 97c089e..f1661dd 100644 --- a/concepts/concept-3.3.3.4.yaml +++ b/concepts/concept-3.3.3.4.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: sidewalk definition: - - content: "{{urn:iso:std:iso:14812:3.3.3.3,footway}} along a {{urn:iso:std:iso:14812:3.3.1.10,roadside}}" + - content: "{{<>,footway}} along a {{<>,roadside}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.3.4.1.yaml b/concepts/concept-3.3.4.1.yaml index d3759b3..00d96e2 100644 --- a/concepts/concept-3.3.4.1.yaml +++ b/concepts/concept-3.3.4.1.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: hard shoulder for emergency use definition: - - content: operating mode of a {{urn:iso:std:iso:14812:3.3.1.19,hard shoulder}} + - content: operating mode of a {{<>,hard shoulder}} that allows operation of emergency, construction, maintenance, or other special - use {{urn:iso:std:iso:14812:3.7.1.1,vehicle,vehicles}} or for emergency stopping + use {{<>,vehicle,vehicles}} or for emergency stopping and is prohibited for other vehicle usage notes: [] examples: [] diff --git a/concepts/concept-3.3.4.2.yaml b/concepts/concept-3.3.4.2.yaml index 756b10a..3eb6d99 100644 --- a/concepts/concept-3.3.4.2.yaml +++ b/concepts/concept-3.3.4.2.yaml @@ -8,10 +8,10 @@ eng: designation: hard shoulder running definition: - content: |- - operating mode of a {{urn:iso:std:iso:14812:3.3.1.19,hard shoulder}} that + operating mode of a {{<>,hard shoulder}} that allows operation of general-purpose - {{urn:iso:std:iso:14812:3.7.6.3,motor vehicle,motor vehicles}} as an extra - {{urn:iso:std:iso:14812:3.3.1.13,lane}} + {{<>,motor vehicle,motor vehicles}} as an extra + {{<>,lane}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.3.5.1.yaml b/concepts/concept-3.3.5.1.yaml index 6cd8e05..9c212c7 100644 --- a/concepts/concept-3.3.5.1.yaml +++ b/concepts/concept-3.3.5.1.yaml @@ -7,13 +7,13 @@ eng: normative_status: preferred designation: road definition: - - content: curvilinear length of {{urn:iso:std:iso:14812:3.3.1.3,roadway}} that + - content: curvilinear length of {{<>,roadway}} that shares the same identification notes: - - content: A length of the {{urn:iso:std:iso:14812:3.3.5.2,road network}} may be + - content: A length of the {{<>,road network}} may be referenced by multiple designators (e.g. Main Street and Route 7). In this case, - there would be two "roads" that share the same set of "{{urn:iso:std:iso:14812:3.3.1.5,carriageway,carriageways}}". - - content: A road can change directions at a {{urn:iso:std:iso:14812:3.3.6.2,junction}}. + there would be two "roads" that share the same set of "{{<>,carriageway,carriageways}}". + - content: A road can change directions at a {{<>,junction}}. - content: The identification is generally a name or number. examples: [] language_code: eng diff --git a/concepts/concept-3.3.5.10.yaml b/concepts/concept-3.3.5.10.yaml index 15300a2..ad0a4ce 100644 --- a/concepts/concept-3.3.5.10.yaml +++ b/concepts/concept-3.3.5.10.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: lane segment definition: - - content: "{{urn:iso:std:iso:14812:3.3.5.1,road,link}} that represents a contiguous - length of a {{urn:iso:std:iso:14812:3.3.5.9,lane link}} characterized by the + - content: "{{<>,road,link}} that represents a contiguous + length of a {{<>,lane link}} characterized by the same physical characteristics" notes: [] examples: [] diff --git a/concepts/concept-3.3.5.2.yaml b/concepts/concept-3.3.5.2.yaml index 911189a..0f10d37 100644 --- a/concepts/concept-3.3.5.2.yaml +++ b/concepts/concept-3.3.5.2.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: road network definition: - - content: interconnected collection of {{urn:iso:std:iso:14812:3.3.5.1,road,roads}} + - content: interconnected collection of {{<>,road,roads}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.3.5.3.yaml b/concepts/concept-3.3.5.3.yaml index 92182b5..cd05dba 100644 --- a/concepts/concept-3.3.5.3.yaml +++ b/concepts/concept-3.3.5.3.yaml @@ -7,13 +7,13 @@ eng: normative_status: preferred designation: road model definition: - - content: representation of a {{urn:iso:std:iso:14812:3.3.5.2,road network}} + - content: representation of a {{<>,road network}} notes: - - content: Road models for different {{urn:iso:std:iso:14812:3.1.2.1,system,systems}} - will often define different models. For example, a public {{urn:iso:std:iso:14812:3.1.2.2,transport - system}} can define {{urn:iso:std:iso:14812:3.3.5.6,road link,road links}} based - on the {{urn:iso:std:iso:14812:3.4.1.1,location}} of bus stops while a traffic - system can define road links based on the location of {{urn:iso:std:iso:14812:3.3.6.2,junction,junctions}}. + - content: Road models for different {{<>,system,systems}} + will often define different models. For example, a public {{<>,transport + system}} can define {{<>,road link,road links}} based + on the {{<>,location}} of bus stops while a traffic + system can define road links based on the location of {{<>,junction,junctions}}. examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.3.5.4.yaml b/concepts/concept-3.3.5.4.yaml index 13d779b..ac6f39d 100644 --- a/concepts/concept-3.3.5.4.yaml +++ b/concepts/concept-3.3.5.4.yaml @@ -11,13 +11,13 @@ eng: designation: road network node domain: road network definition: - - content: component of a {{urn:iso:std:iso:14812:3.3.5.3,road model}} representing - a {{urn:iso:std:iso:14812:3.4.1.3,point location}} of the {{urn:iso:std:iso:14812:3.3.5.2,road + - content: component of a {{<>,road model}} representing + a {{<>,point location}} of the {{<>,road network}} graph notes: - - content: The point location typically represents a point along the {{urn:iso:std:iso:14812:3.3.5.1,road}} - which can be used to designate the {{urn:iso:std:iso:14812:3.4.1.1,location}} - of a {{urn:iso:std:iso:14812:3.3.6.2,junction}}, {{urn:iso:std:iso:14812:3.5.6.1,public + - content: The point location typically represents a point along the {{<>,road}} + which can be used to designate the {{<>,location}} + of a {{<>,junction}}, {{<>,public transport}} stop, jurisdictional boundary, termination point, etc. examples: [] language_code: eng diff --git a/concepts/concept-3.3.5.5.yaml b/concepts/concept-3.3.5.5.yaml index 40bf7db..ebe0fc6 100644 --- a/concepts/concept-3.3.5.5.yaml +++ b/concepts/concept-3.3.5.5.yaml @@ -8,8 +8,8 @@ eng: designation: link domain: road network definition: - - content: component of a {{urn:iso:std:iso:14812:3.3.5.3,road model}} that represents - a connection between two {{urn:iso:std:iso:14812:3.3.5.4,node,nodes}} + - content: component of a {{<>,road model}} that represents + a connection between two {{<>,node,nodes}} notes: - content: A link can be curvilinear and can have various attributes such as width. examples: [] diff --git a/concepts/concept-3.3.5.6.yaml b/concepts/concept-3.3.5.6.yaml index d226ccb..7332443 100644 --- a/concepts/concept-3.3.5.6.yaml +++ b/concepts/concept-3.3.5.6.yaml @@ -7,14 +7,14 @@ eng: normative_status: preferred designation: road link definition: - - content: "{{urn:iso:std:iso:14812:3.3.5.5,link}} representing a contiguous length - of a {{urn:iso:std:iso:14812:3.3.5.1,road}} between two {{urn:iso:std:iso:14812:3.3.5.4,node,nodes}} + - content: "{{<>,link}} representing a contiguous length + of a {{<>,road}} between two {{<>,node,nodes}} of operational or managerial significance" notes: - content: The operational characteristics of the nodes would relate to the type - of {{urn:iso:std:iso:14812:3.3.5.3,road model}}. For example, a traffic {{urn:iso:std:iso:14812:3.1.2.1,system}} - can base its road links on nodes that represent {{urn:iso:std:iso:14812:3.3.6.2,junction,junctions}} - and road {{urn:iso:std:iso:14812:3.1.8.3,terminator,terminators}}. + of {{<>,road model}}. For example, a traffic {{<>,system}} + can base its road links on nodes that represent {{<>,junction,junctions}} + and road {{<>,terminator,terminators}}. examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.3.5.7.yaml b/concepts/concept-3.3.5.7.yaml index ad573cf..a9b6c7e 100644 --- a/concepts/concept-3.3.5.7.yaml +++ b/concepts/concept-3.3.5.7.yaml @@ -7,11 +7,11 @@ eng: normative_status: preferred designation: road section definition: - - content: aggregation of one or more {{urn:iso:std:iso:14812:3.3.5.6,road link,road - links}} that represents a contiguous length of a {{urn:iso:std:iso:14812:3.3.5.1,road}} + - content: aggregation of one or more {{<>,road link,road + links}} that represents a contiguous length of a {{<>,road}} that shares the same management and operational strategies notes: - - content: Different {{urn:iso:std:iso:14812:3.3.5.3,road model,road models}} can + - content: Different {{<>,road model,road models}} can divide the same road into different road sections. examples: - content: A traffic signal timing plan is applied to one road section. diff --git a/concepts/concept-3.3.5.8.yaml b/concepts/concept-3.3.5.8.yaml index 95d9bb1..7574306 100644 --- a/concepts/concept-3.3.5.8.yaml +++ b/concepts/concept-3.3.5.8.yaml @@ -7,14 +7,14 @@ eng: normative_status: preferred designation: road segment definition: - - content: "{{urn:iso:std:iso:14812:3.3.5.5,link}} that represents a contiguous - length of a {{urn:iso:std:iso:14812:3.3.5.6,road link}} characterized by the + - content: "{{<>,link}} that represents a contiguous + length of a {{<>,road link}} characterized by the same physical characteristics" notes: - content: The definition of road segments is highly dependent on which characteristics are modelled by the implementation. Characteristics that can result in a new - road segment include addition or subtraction of a {{urn:iso:std:iso:14812:3.3.1.13,lane}}, - a change in {{urn:iso:std:iso:14812:3.3.1.3,roadway}} width, the change of {{urn:iso:std:iso:14812:3.3.5.1,road}} + road segment include addition or subtraction of a {{<>,lane}}, + a change in {{<>,roadway}} width, the change of {{<>,road}} type (e.g. start/end of a bridge), etc. examples: [] language_code: eng diff --git a/concepts/concept-3.3.5.9.yaml b/concepts/concept-3.3.5.9.yaml index 1d5455d..2492503 100644 --- a/concepts/concept-3.3.5.9.yaml +++ b/concepts/concept-3.3.5.9.yaml @@ -7,14 +7,14 @@ eng: normative_status: preferred designation: lane link definition: - - content: "{{urn:iso:std:iso:14812:3.3.5.5,link}} that represents a {{urn:iso:std:iso:14812:3.3.1.13,lane}} - of a {{urn:iso:std:iso:14812:3.3.5.6,road link}}" + - content: "{{<>,link}} that represents a {{<>,lane}} + of a {{<>,road link}}" notes: - - content: A {{urn:iso:std:iso:14812:3.3.5.10,lane segment}} can start or end at - {{urn:iso:std:iso:14812:3.4.1.1,location,locations}} other than the start or - end of the corresponding {{urn:iso:std:iso:14812:3.3.5.8,road segment}} (e.g. + - content: A {{<>,lane segment}} can start or end at + {{<>,location,locations}} other than the start or + end of the corresponding {{<>,road segment}} (e.g. a lane can start mid-block). - - content: A lane segment only includes the{{urn:iso:std:iso:14812:3.5.9.2,sequential}} + - content: A lane segment only includes the{{<>,sequential}} lane links, it does not include lane links from adjacent lanes. examples: [] language_code: eng diff --git a/concepts/concept-3.3.6.1.yaml b/concepts/concept-3.3.6.1.yaml index 0b94807..a1f063d 100644 --- a/concepts/concept-3.3.6.1.yaml +++ b/concepts/concept-3.3.6.1.yaml @@ -7,14 +7,14 @@ eng: normative_status: preferred designation: intersection definition: - - content: space where two or more {{urn:iso:std:iso:14812:3.3.5.1,road,roads}} + - content: space where two or more {{<>,road,roads}} meet or cross notes: - - content: Intersections can be associated with zero {{urn:iso:std:iso:14812:3.3.6.2,junction,junctions}}, + - content: Intersections can be associated with zero {{<>,junction,junctions}}, such as a motorway crossing a road without any connecting ramps, or can be associated - with one or more junctions, such as a diamond {{urn:iso:std:iso:14812:3.3.6.9,interchange}}. + with one or more junctions, such as a diamond {{<>,interchange}}. - content: Complex intersections can be viewed as multiple intersections by providing - separate designations for distinct {{urn:iso:std:iso:14812:3.3.5.6,road link,road + separate designations for distinct {{<>,road link,road links}}. For example, one model could depict a complex intersection as being associated with multiple junctions; another model could depict the same physical infrastructure as being multiple intersections that are interconnected by different diff --git a/concepts/concept-3.3.6.10.yaml b/concepts/concept-3.3.6.10.yaml index f1adff6..ad8bf58 100644 --- a/concepts/concept-3.3.6.10.yaml +++ b/concepts/concept-3.3.6.10.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: grade separated manoeuvre definition: - - content: "{{urn:iso:std:iso:14812:3.3.6.7,intersection manoeuvre,manoeuvre}} that + - content: "{{<>,intersection manoeuvre,manoeuvre}} that is vertically separated from one or more manoeuvres that cross its two-dimensional path" notes: [] diff --git a/concepts/concept-3.3.6.2.yaml b/concepts/concept-3.3.6.2.yaml index ed81a5c..ad73db7 100644 --- a/concepts/concept-3.3.6.2.yaml +++ b/concepts/concept-3.3.6.2.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: junction definition: - - content: "{{urn:iso:std:iso:14812:3.3.6.1,intersection}} that allows {{urn:iso:std:iso:14812:3.6.1.1,traveller,travellers}} - to change {{urn:iso:std:iso:14812:3.3.5.1,road,roads}}" + - content: "{{<>,intersection}} that allows {{<>,traveller,travellers}} + to change {{<>,road,roads}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.3.6.3.yaml b/concepts/concept-3.3.6.3.yaml index 4445c7e..8b36e19 100644 --- a/concepts/concept-3.3.6.3.yaml +++ b/concepts/concept-3.3.6.3.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ingress lane definition: - - content: "{{urn:iso:std:iso:14812:3.3.1.13,traffic lane}} designed for entering - a {{urn:iso:std:iso:14812:3.3.6.2,junction}}" + - content: "{{<>,traffic lane}} designed for entering + a {{<>,junction}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.3.6.4.yaml b/concepts/concept-3.3.6.4.yaml index 1f35ea4..1915ae1 100644 --- a/concepts/concept-3.3.6.4.yaml +++ b/concepts/concept-3.3.6.4.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ingress link definition: - - content: all {{urn:iso:std:iso:14812:3.3.6.3,ingress lane,ingress lanes}} on a - {{urn:iso:std:iso:14812:3.3.5.6,road link}} + - content: all {{<>,ingress lane,ingress lanes}} on a + {{<>,road link}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.3.6.5.yaml b/concepts/concept-3.3.6.5.yaml index 1646252..bec4295 100644 --- a/concepts/concept-3.3.6.5.yaml +++ b/concepts/concept-3.3.6.5.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: egress lane definition: - - content: "{{urn:iso:std:iso:14812:3.3.1.13,traffic lane}} designed for exiting - a {{urn:iso:std:iso:14812:3.3.6.2,junction}}" + - content: "{{<>,traffic lane}} designed for exiting + a {{<>,junction}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.3.6.6.yaml b/concepts/concept-3.3.6.6.yaml index 30ab824..e0698b5 100644 --- a/concepts/concept-3.3.6.6.yaml +++ b/concepts/concept-3.3.6.6.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: egress link definition: - - content: all {{urn:iso:std:iso:14812:3.3.6.5,egress lane,egress lanes}} on a {{urn:iso:std:iso:14812:3.3.5.6,road + - content: all {{<>,egress lane,egress lanes}} on a {{<>,road link}} notes: [] examples: [] diff --git a/concepts/concept-3.3.6.7.yaml b/concepts/concept-3.3.6.7.yaml index c7384c5..f2532ac 100644 --- a/concepts/concept-3.3.6.7.yaml +++ b/concepts/concept-3.3.6.7.yaml @@ -14,8 +14,8 @@ eng: designation: maneuver domain: junction definition: - - content: movement from an {{urn:iso:std:iso:14812:3.3.6.3,ingress lane}} to an - {{urn:iso:std:iso:14812:3.3.6.5,egress lane}} + - content: movement from an {{<>,ingress lane}} to an + {{<>,egress lane}} notes: - content: The term "maneuver" is the American English spelling. examples: [] diff --git a/concepts/concept-3.3.6.8.yaml b/concepts/concept-3.3.6.8.yaml index 3872020..20f99de 100644 --- a/concepts/concept-3.3.6.8.yaml +++ b/concepts/concept-3.3.6.8.yaml @@ -13,7 +13,7 @@ eng: normative_status: admitted designation: grade junction definition: - - content: "{{urn:iso:std:iso:14812:3.3.6.2,junction}} without any {{urn:iso:std:iso:14812:3.3.6.10,grade + - content: "{{<>,junction}} without any {{<>,grade separated manoeuvre,grade separated manoeuvres}}" notes: [] examples: [] diff --git a/concepts/concept-3.3.6.9.yaml b/concepts/concept-3.3.6.9.yaml index d8264bb..5c78299 100644 --- a/concepts/concept-3.3.6.9.yaml +++ b/concepts/concept-3.3.6.9.yaml @@ -7,14 +7,14 @@ eng: normative_status: preferred designation: interchange definition: - - content: "{{urn:iso:std:iso:14812:3.3.6.2,junction}} with at least one {{urn:iso:std:iso:14812:3.3.6.10,grade + - content: "{{<>,junction}} with at least one {{<>,grade separated manoeuvre}}" notes: - content: The term "interchange" typically refers to the facilities that enable - all available manoeuvres at the grade separated {{urn:iso:std:iso:14812:3.3.6.1,intersection}}, + all available manoeuvres at the grade separated {{<>,intersection}}, which typically includes multiple junctions. - - content: The grade separation allows {{urn:iso:std:iso:14812:3.6.1.1,traveller,travellers}} - on the {{urn:iso:std:iso:14812:3.3.5.5,link}} to pass unimpeded through the + - content: The grade separation allows {{<>,traveller,travellers}} + on the {{<>,link}} to pass unimpeded through the interchange when congestion is not present. examples: [] language_code: eng diff --git a/concepts/concept-3.4.1.2.yaml b/concepts/concept-3.4.1.2.yaml index 44b259a..b2ccfc8 100644 --- a/concepts/concept-3.4.1.2.yaml +++ b/concepts/concept-3.4.1.2.yaml @@ -10,7 +10,7 @@ eng: normative_status: preferred designation: ITS spatial location definition: - - content: "{{urn:iso:std:iso:14812:3.4.1.1,location}} within three-dimensional + - content: "{{<>,location}} within three-dimensional space" notes: - content: The "location" could be a point (consuming no space) or could consume diff --git a/concepts/concept-3.4.1.3.yaml b/concepts/concept-3.4.1.3.yaml index b0648d6..162dfc5 100644 --- a/concepts/concept-3.4.1.3.yaml +++ b/concepts/concept-3.4.1.3.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: point location definition: - - content: "{{urn:iso:std:iso:14812:3.4.1.2,spatial location}} with no length in + - content: "{{<>,spatial location}} with no length in any of the spatial dimensions" notes: [] examples: [] diff --git a/concepts/concept-3.4.1.5.yaml b/concepts/concept-3.4.1.5.yaml index 77c3396..39d9b5b 100644 --- a/concepts/concept-3.4.1.5.yaml +++ b/concepts/concept-3.4.1.5.yaml @@ -10,8 +10,8 @@ eng: normative_status: preferred designation: ITS linear location definition: - - content: "{{urn:iso:std:iso:14812:3.4.1.2,spatial location}} that extends between - two {{urn:iso:std:iso:14812:3.4.1.3,point location,point locations}} along a + - content: "{{<>,spatial location}} that extends between + two {{<>,point location,point locations}} along a defined path" notes: - content: The path can exhibit 3-dimensional characteristics. diff --git a/concepts/concept-3.4.1.6.yaml b/concepts/concept-3.4.1.6.yaml index 81f6767..bb46edd 100644 --- a/concepts/concept-3.4.1.6.yaml +++ b/concepts/concept-3.4.1.6.yaml @@ -10,7 +10,7 @@ eng: normative_status: preferred designation: ITS area location definition: - - content: "{{urn:iso:std:iso:14812:3.4.1.2,spatial location}} enclosed within a + - content: "{{<>,spatial location}} enclosed within a two-dimensional boundary or boundaries across a defined surface" notes: - content: The boundary can consist of a single curvilinear line (e.g. a circle) diff --git a/concepts/concept-3.4.2.1.yaml b/concepts/concept-3.4.2.1.yaml index a620756..f0211f9 100644 --- a/concepts/concept-3.4.2.1.yaml +++ b/concepts/concept-3.4.2.1.yaml @@ -10,7 +10,7 @@ eng: normative_status: preferred designation: ITS location referencing definition: - - content: process used to develop a {{urn:iso:std:iso:14812:3.4.2.2,spatial reference}} + - content: process used to develop a {{<>,spatial reference}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.4.2.2.yaml b/concepts/concept-3.4.2.2.yaml index 9dfd745..922bd8e 100644 --- a/concepts/concept-3.4.2.2.yaml +++ b/concepts/concept-3.4.2.2.yaml @@ -13,7 +13,7 @@ eng: normative_status: admitted designation: location reference definition: - - content: description of a {{urn:iso:std:iso:14812:3.4.1.2,spatial location}} in + - content: description of a {{<>,spatial location}} in the real world according to a defined reference system notes: - content: It is not necessary for the rules be formal coordinates but they could diff --git a/concepts/concept-3.4.2.3.yaml b/concepts/concept-3.4.2.3.yaml index 25d5e19..e999626 100644 --- a/concepts/concept-3.4.2.3.yaml +++ b/concepts/concept-3.4.2.3.yaml @@ -10,7 +10,7 @@ eng: normative_status: admitted designation: dynamic location reference definition: - - content: "{{urn:iso:std:iso:14812:3.4.2.2,spatial reference}} generated on-the-fly + - content: "{{<>,spatial reference}} generated on-the-fly based on geographic properties in a digital map database" notes: [] examples: [] diff --git a/concepts/concept-3.4.2.4.yaml b/concepts/concept-3.4.2.4.yaml index 35f83e2..7026fc3 100644 --- a/concepts/concept-3.4.2.4.yaml +++ b/concepts/concept-3.4.2.4.yaml @@ -10,9 +10,9 @@ eng: normative_status: admitted designation: pre-coded location reference definition: - - content: "{{urn:iso:std:iso:14812:3.4.2.2,spatial reference}} using a unique identifier - that is agreed upon in both the sender and receiver {{urn:iso:std:iso:14812:3.1.2.1,system}} - to select a {{urn:iso:std:iso:14812:3.4.1.1,location}} from a set of pre-coded + - content: "{{<>,spatial reference}} using a unique identifier + that is agreed upon in both the sender and receiver {{<>,system}} + to select a {{<>,location}} from a set of pre-coded locations" notes: [] examples: [] diff --git a/concepts/concept-3.4.2.5.yaml b/concepts/concept-3.4.2.5.yaml index 72e8e20..f1b7b62 100644 --- a/concepts/concept-3.4.2.5.yaml +++ b/concepts/concept-3.4.2.5.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: link location definition: - - content: "{{urn:iso:std:iso:14812:3.4.2.4,pre-coded spatial reference}} defined - within the {{urn:iso:std:iso:14812:3.3.5.2,road network}} database" + - content: "{{<>,pre-coded spatial reference}} defined + within the {{<>,road network}} database" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.4.2.6.yaml b/concepts/concept-3.4.2.6.yaml index 0d8c0ff..a4f1c59 100644 --- a/concepts/concept-3.4.2.6.yaml +++ b/concepts/concept-3.4.2.6.yaml @@ -10,8 +10,8 @@ eng: normative_status: deprecated designation: location code definition: - - content: "{{urn:iso:std:iso:14812:3.4.2.2,spatial reference}} in the form of a - label or code that identifies a {{urn:iso:std:iso:14812:3.4.1.1,location}}" + - content: "{{<>,spatial reference}} in the form of a + label or code that identifies a {{<>,location}}" notes: - content: The term "location code" has been used previously in ISO/TC 204 documents, but "geographic identifier" is preferred to better align with the activities diff --git a/concepts/concept-3.4.2.7.yaml b/concepts/concept-3.4.2.7.yaml index 9c2d7a3..d3f071d 100644 --- a/concepts/concept-3.4.2.7.yaml +++ b/concepts/concept-3.4.2.7.yaml @@ -10,8 +10,8 @@ eng: normative_status: admitted designation: location table definition: - - content: register of {{urn:iso:std:iso:14812:3.4.2.2,spatial reference,spatial - references}} of one or more {{urn:iso:std:iso:14812:3.4.1.1,location}} sub-types + - content: register of {{<>,spatial reference,spatial + references}} of one or more {{<>,location}} sub-types containing some information regarding position notes: - content: The positional information need not be coordinates but could be descriptive. diff --git a/concepts/concept-3.5.1.1.yaml b/concepts/concept-3.5.1.1.yaml index 75548ef..32cc5c5 100644 --- a/concepts/concept-3.5.1.1.yaml +++ b/concepts/concept-3.5.1.1.yaml @@ -8,7 +8,7 @@ eng: designation: service definition: - content: provision of one or more capabilities, functionalities or facilities - to enable one or more tasks to fulfil a {{urn:iso:std:iso:14812:3.5.1.4,user + to enable one or more tasks to fulfil a {{<>,user need,need}} notes: [] examples: [] diff --git a/concepts/concept-3.5.1.2.yaml b/concepts/concept-3.5.1.2.yaml index 5988840..5104cc6 100644 --- a/concepts/concept-3.5.1.2.yaml +++ b/concepts/concept-3.5.1.2.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: service provider definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.1,entity}} that delivers one or more {{urn:iso:std:iso:14812:3.5.2.1,service,services}}" + - content: "{{<>,entity}} that delivers one or more {{<>,service,services}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.1.3.yaml b/concepts/concept-3.5.1.3.yaml index b042174..7cb684b 100644 --- a/concepts/concept-3.5.1.3.yaml +++ b/concepts/concept-3.5.1.3.yaml @@ -10,11 +10,11 @@ eng: normative_status: preferred designation: consumer definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.1,entity}} that has a {{urn:iso:std:iso:14812:3.5.1.4,user + - content: "{{<>,entity}} that has a {{<>,user need,need}} to be fulfilled" notes: - content: The term "consumer" can be used when fulfilling the need results in the - consumption of a {{urn:iso:std:iso:14812:3.1.6.2,resource}}. + consumption of a {{<>,resource}}. examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.5.10.1.yaml b/concepts/concept-3.5.10.1.yaml index af33e57..5b10ceb 100644 --- a/concepts/concept-3.5.10.1.yaml +++ b/concepts/concept-3.5.10.1.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: network model definition: - - content: infrastructure framework for the agreement between a {{urn:iso:std:iso:14812:3.5.1.2,service - provider}} and a {{urn:iso:std:iso:14812:3.5.3.4,user}} + - content: infrastructure framework for the agreement between a {{<>,service + provider}} and a {{<>,user}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.10.2.yaml b/concepts/concept-3.5.10.2.yaml index 2be0b18..91b904c 100644 --- a/concepts/concept-3.5.10.2.yaml +++ b/concepts/concept-3.5.10.2.yaml @@ -8,9 +8,9 @@ eng: designation: station-based roundtrip domain: transport service definition: - - content: "{{urn:iso:std:iso:14812:3.5.9.1,operational model,operational mode}} - where the {{urn:iso:std:iso:14812:3.5.2.1,transport service}} is initiated and - terminated at the same facility managed by the {{urn:iso:std:iso:14812:3.5.2.2,transport + - content: "{{<>,operational model,operational mode}} + where the {{<>,transport service}} is initiated and + terminated at the same facility managed by the {{<>,transport provider}}" notes: [] examples: [] diff --git a/concepts/concept-3.5.10.3.yaml b/concepts/concept-3.5.10.3.yaml index 0b3bfd5..919e676 100644 --- a/concepts/concept-3.5.10.3.yaml +++ b/concepts/concept-3.5.10.3.yaml @@ -8,9 +8,9 @@ eng: designation: station-based one-way domain: transport service definition: - - content: "{{urn:iso:std:iso:14812:3.5.9.1,operational model,operational mode}} - where the {{urn:iso:std:iso:14812:3.5.2.1,transport service}} is initiated and - terminated at two different facilities managed by the {{urn:iso:std:iso:14812:3.5.2.2,transport + - content: "{{<>,operational model,operational mode}} + where the {{<>,transport service}} is initiated and + terminated at two different facilities managed by the {{<>,transport provider}}" notes: [] examples: [] diff --git a/concepts/concept-3.5.10.4.yaml b/concepts/concept-3.5.10.4.yaml index a36e1d7..eadef42 100644 --- a/concepts/concept-3.5.10.4.yaml +++ b/concepts/concept-3.5.10.4.yaml @@ -8,8 +8,8 @@ eng: designation: free-floating domain: transport service definition: - - content: "{{urn:iso:std:iso:14812:3.5.10.1,network model}} where the {{urn:iso:std:iso:14812:3.5.2.1,transport - service}} may be initiated and terminated at any {{urn:iso:std:iso:14812:3.4.1.1,location}} + - content: "{{<>,network model}} where the {{<>,transport + service}} may be initiated and terminated at any {{<>,location}} meeting basic criteria" notes: - content: The basic criteria typically include geographic limits and requirements diff --git a/concepts/concept-3.5.11.1.yaml b/concepts/concept-3.5.11.1.yaml index 8167e02..49209e5 100644 --- a/concepts/concept-3.5.11.1.yaml +++ b/concepts/concept-3.5.11.1.yaml @@ -7,11 +7,11 @@ eng: normative_status: preferred designation: shuttle service definition: - - content: "{{urn:iso:std:iso:14812:3.5.6.2,shared transport service}} that transports - {{urn:iso:std:iso:14812:3.6.2.1,passenger,passengers}} between two specified - {{urn:iso:std:iso:14812:3.4.1.1,location,locations}}" + - content: "{{<>,shared transport service}} that transports + {{<>,passenger,passengers}} between two specified + {{<>,location,locations}}" notes: - - content: Each location can be defined as point, linear or {{urn:iso:std:iso:14812:3.4.1.6,area + - content: Each location can be defined as point, linear or {{<>,area location,area locations}}. However, the areas of the two locations should not overlap. examples: [] diff --git a/concepts/concept-3.5.11.2.yaml b/concepts/concept-3.5.11.2.yaml index 32b1ab1..41be7fc 100644 --- a/concepts/concept-3.5.11.2.yaml +++ b/concepts/concept-3.5.11.2.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: taxi service definition: - - content: "{{urn:iso:std:iso:14812:3.5.8.2,commercial}} {{urn:iso:std:iso:14812:3.5.6.2,shared - transport service}} that transports {{urn:iso:std:iso:14812:3.6.2.1,passenger,passengers}} - {{urn:iso:std:iso:14812:3.5.9.2,sequential,sequentially}}" + - content: "{{<>,commercial}} {{<>,shared + transport service}} that transports {{<>,passenger,passengers}} + {{<>,sequential,sequentially}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.11.3.yaml b/concepts/concept-3.5.11.3.yaml index d21f231..8b35792 100644 --- a/concepts/concept-3.5.11.3.yaml +++ b/concepts/concept-3.5.11.3.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: taxi-share service definition: - - content: "{{urn:iso:std:iso:14812:3.5.8.2,commercial}} {{urn:iso:std:iso:14812:3.5.6.2,shared - transport service}} that transports {{urn:iso:std:iso:14812:3.6.2.1,passenger,passengers}} - {{urn:iso:std:iso:14812:3.5.9.3,concurrent,concurrently}}" + - content: "{{<>,commercial}} {{<>,shared + transport service}} that transports {{<>,passenger,passengers}} + {{<>,concurrent,concurrently}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.11.4.yaml b/concepts/concept-3.5.11.4.yaml index a42fd92..273a388 100644 --- a/concepts/concept-3.5.11.4.yaml +++ b/concepts/concept-3.5.11.4.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: rideshare service definition: - - content: "{{urn:iso:std:iso:14812:3.5.8.4,cooperative}} {{urn:iso:std:iso:14812:3.5.6.2,shared - transport service}} that transports {{urn:iso:std:iso:14812:3.6.2.1,passenger,passengers}} - {{urn:iso:std:iso:14812:3.5.9.3,concurrent,concurrently}}" + - content: "{{<>,cooperative}} {{<>,shared + transport service}} that transports {{<>,passenger,passengers}} + {{<>,concurrent,concurrently}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.11.5.yaml b/concepts/concept-3.5.11.5.yaml index 1212995..d1c714f 100644 --- a/concepts/concept-3.5.11.5.yaml +++ b/concepts/concept-3.5.11.5.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ridesourced service definition: - - content: "{{urn:iso:std:iso:14812:3.5.8.2,commercial}}, {{urn:iso:std:iso:14812:3.5.7.5,peer-to-peer}} - {{urn:iso:std:iso:14812:3.5.6.2,shared transport service}} that transports {{urn:iso:std:iso:14812:3.6.2.1,passenger,passengers}}" + - content: "{{<>,commercial}}, {{<>,peer-to-peer}} + {{<>,shared transport service}} that transports {{<>,passenger,passengers}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.11.6.yaml b/concepts/concept-3.5.11.6.yaml index 709db5c..70bffce 100644 --- a/concepts/concept-3.5.11.6.yaml +++ b/concepts/concept-3.5.11.6.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ridesplit service definition: - - content: "{{urn:iso:std:iso:14812:3.5.11.5,ridesourced service}} that serves {{urn:iso:std:iso:14812:3.6.2.1,passenger,passengers}} - {{urn:iso:std:iso:14812:3.5.9.3,concurrent,concurrently}}" + - content: "{{<>,ridesourced service}} that serves {{<>,passenger,passengers}} + {{<>,concurrent,concurrently}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.11.7.yaml b/concepts/concept-3.5.11.7.yaml index 5955cfb..8c24ca0 100644 --- a/concepts/concept-3.5.11.7.yaml +++ b/concepts/concept-3.5.11.7.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: courier network service definition: - - content: "{{urn:iso:std:iso:14812:3.5.8.2,commercial}}, {{urn:iso:std:iso:14812:3.5.7.5,peer-to-peer}} - {{urn:iso:std:iso:14812:3.5.6.2,shared transport service}} that transports goods" + - content: "{{<>,commercial}}, {{<>,peer-to-peer}} + {{<>,shared transport service}} that transports goods" notes: - content: The goods are typically small packages, letters, food, etc. examples: [] diff --git a/concepts/concept-3.5.12.1.yaml b/concepts/concept-3.5.12.1.yaml index 26f8f11..c110dfc 100644 --- a/concepts/concept-3.5.12.1.yaml +++ b/concepts/concept-3.5.12.1.yaml @@ -10,7 +10,7 @@ eng: normative_status: admitted designation: bicycle sharing service definition: - - content: "{{urn:iso:std:iso:14812:3.5.6.3,shared vehicle service}} that shares + - content: "{{<>,shared vehicle service}} that shares bicycles" notes: - content: The term "bicycle sharing service" is admitted, but "bikesharing service" diff --git a/concepts/concept-3.5.12.2.yaml b/concepts/concept-3.5.12.2.yaml index 1a41866..ff6da0d 100644 --- a/concepts/concept-3.5.12.2.yaml +++ b/concepts/concept-3.5.12.2.yaml @@ -10,8 +10,8 @@ eng: normative_status: admitted designation: passenger car sharing service definition: - - content: "{{urn:iso:std:iso:14812:3.5.6.3,shared vehicle service}} that shares - {{urn:iso:std:iso:14812:3.6.2.1,passenger}} cars" + - content: "{{<>,shared vehicle service}} that shares + {{<>,passenger}} cars" notes: - content: The term "passenger car sharing service" is admitted but has the same meaning. diff --git a/concepts/concept-3.5.13.1.yaml b/concepts/concept-3.5.13.1.yaml index 2fecb94..22135a5 100644 --- a/concepts/concept-3.5.13.1.yaml +++ b/concepts/concept-3.5.13.1.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: mobility app definition: - - content: "{{urn:iso:std:iso:14812:3.2.9.4,ITS-S application implementation}} designed + - content: "{{<>,ITS-S application implementation}} designed to assist an individual transport consumer in understanding transport-related information, making decisions, and/or acting upon decisions" notes: [] diff --git a/concepts/concept-3.5.13.2.yaml b/concepts/concept-3.5.13.2.yaml index f82a53f..f7328d4 100644 --- a/concepts/concept-3.5.13.2.yaml +++ b/concepts/concept-3.5.13.2.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: B2C mobility sharing app definition: - - content: "{{urn:iso:std:iso:14812:3.5.13.1,mobility app}} that assists a {{urn:iso:std:iso:14812:3.5.2.3,transport - user}} in acquiring a {{urn:iso:std:iso:14812:3.5.2.1,transport service}} from + - content: "{{<>,mobility app}} that assists a {{<>,transport + user}} in acquiring a {{<>,transport service}} from a specific business" notes: [] examples: [] diff --git a/concepts/concept-3.5.13.3.yaml b/concepts/concept-3.5.13.3.yaml index d677ee4..1335280 100644 --- a/concepts/concept-3.5.13.3.yaml +++ b/concepts/concept-3.5.13.3.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: navigation app definition: - - content: "{{urn:iso:std:iso:14812:3.5.13.1,mobility app}} that assists a {{urn:iso:std:iso:14812:3.5.2.3,transport + - content: "{{<>,mobility app}} that assists a {{<>,transport user}} to determine the best route to a destination" notes: [] examples: [] diff --git a/concepts/concept-3.5.13.4.yaml b/concepts/concept-3.5.13.4.yaml index 0881dd2..2c567f7 100644 --- a/concepts/concept-3.5.13.4.yaml +++ b/concepts/concept-3.5.13.4.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: P2P mobility sharing app definition: - - content: "{{urn:iso:std:iso:14812:3.5.13.1,mobility app}} that assists a {{urn:iso:std:iso:14812:3.5.2.3,transport - user}} in acquiring {{urn:iso:std:iso:14812:3.5.2.1,transport service}} from + - content: "{{<>,mobility app}} that assists a {{<>,transport + user}} in acquiring {{<>,transport service}} from an individual that participates in the mobility app's network" notes: [] examples: [] diff --git a/concepts/concept-3.5.13.5.yaml b/concepts/concept-3.5.13.5.yaml index 1c67c8d..30a2e4d 100644 --- a/concepts/concept-3.5.13.5.yaml +++ b/concepts/concept-3.5.13.5.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ridesourcing app definition: - - content: "{{urn:iso:std:iso:14812:3.5.13.4,P2P mobility sharing app}} for acquiring - a {{urn:iso:std:iso:14812:3.5.11.5,ridesourced service}}" + - content: "{{<>,P2P mobility sharing app}} for acquiring + a {{<>,ridesourced service}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.13.6.yaml b/concepts/concept-3.5.13.6.yaml index 31cb7a4..922fdd1 100644 --- a/concepts/concept-3.5.13.6.yaml +++ b/concepts/concept-3.5.13.6.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: public transport app definition: - - content: "{{urn:iso:std:iso:14812:3.5.13.1,mobility app}} that assists a {{urn:iso:std:iso:14812:3.5.2.3,transport - user}} in using a {{urn:iso:std:iso:14812:3.5.6.1,public transport}} {{urn:iso:std:iso:14812:3.1.2.1,system}}" + - content: "{{<>,mobility app}} that assists a {{<>,transport + user}} in using a {{<>,public transport}} {{<>,system}}" notes: - content: A public transport app can include features such as viewing maps, searching routes and schedules, real-time arrival information, ticketing, electronic boarding diff --git a/concepts/concept-3.5.13.7.yaml b/concepts/concept-3.5.13.7.yaml index 32aa0f5..8cfc92b 100644 --- a/concepts/concept-3.5.13.7.yaml +++ b/concepts/concept-3.5.13.7.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: real-time traveller information app definition: - - content: "{{urn:iso:std:iso:14812:3.5.13.1,mobility app}} that provides information - about current travel conditions to a {{urn:iso:std:iso:14812:3.5.2.3,transport + - content: "{{<>,mobility app}} that provides information + about current travel conditions to a {{<>,transport user}}" notes: [] examples: [] diff --git a/concepts/concept-3.5.13.8.yaml b/concepts/concept-3.5.13.8.yaml index 0eed54e..d5dad2d 100644 --- a/concepts/concept-3.5.13.8.yaml +++ b/concepts/concept-3.5.13.8.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: taxi hailing app definition: - - content: "{{urn:iso:std:iso:14812:3.5.13.1,mobility app}} that assists a {{urn:iso:std:iso:14812:3.5.2.3,transport + - content: "{{<>,mobility app}} that assists a {{<>,transport user}} in electronically requesting a taxi" notes: [] examples: [] diff --git a/concepts/concept-3.5.13.9.yaml b/concepts/concept-3.5.13.9.yaml index 7a11436..b0c4b8e 100644 --- a/concepts/concept-3.5.13.9.yaml +++ b/concepts/concept-3.5.13.9.yaml @@ -7,11 +7,11 @@ eng: normative_status: preferred designation: trip aggregator app definition: - - content: "{{urn:iso:std:iso:14812:3.5.13.1,mobility app}} that assists a {{urn:iso:std:iso:14812:3.5.2.3,transport - user}} in planning trips that may span multiple vehicle modes or {{urn:iso:std:iso:14812:3.5.2.2,transport + - content: "{{<>,mobility app}} that assists a {{<>,transport + user}} in planning trips that may span multiple vehicle modes or {{<>,transport provider,transport providers}}" notes: - - content: The assistance can include reservations, ticketing and similar {{urn:iso:std:iso:14812:3.5.2.1,service,services}}. + - content: The assistance can include reservations, ticketing and similar {{<>,service,services}}. examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.5.2.1.yaml b/concepts/concept-3.5.2.1.yaml index 1252c95..c9d221b 100644 --- a/concepts/concept-3.5.2.1.yaml +++ b/concepts/concept-3.5.2.1.yaml @@ -11,9 +11,9 @@ eng: designation: service domain: transport definition: - - content: "{{urn:iso:std:iso:14812:3.5.2.1,service}} that delivers one or more - {{urn:iso:std:iso:14812:3.1.1.3,material entity,material entities}} from one - {{urn:iso:std:iso:14812:3.4.1.1,location}} to another to satisfy a {{urn:iso:std:iso:14812:3.5.2.4,transport + - content: "{{<>,service}} that delivers one or more + {{<>,material entity,material entities}} from one + {{<>,location}} to another to satisfy a {{<>,transport need}}" notes: - content: The material entities delivered can be people and/or goods. diff --git a/concepts/concept-3.5.2.2.yaml b/concepts/concept-3.5.2.2.yaml index dac810a..d157bc9 100644 --- a/concepts/concept-3.5.2.2.yaml +++ b/concepts/concept-3.5.2.2.yaml @@ -14,7 +14,7 @@ eng: designation: provider domain: transport definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.1,entity}} that delivers one or more {{urn:iso:std:iso:14812:3.5.2.1,transport + - content: "{{<>,entity}} that delivers one or more {{<>,transport service,transport services}}" notes: [] examples: [] diff --git a/concepts/concept-3.5.2.3.yaml b/concepts/concept-3.5.2.3.yaml index d02b110..b5535a3 100644 --- a/concepts/concept-3.5.2.3.yaml +++ b/concepts/concept-3.5.2.3.yaml @@ -14,7 +14,7 @@ eng: designation: consumer domain: transport definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.1,entity}} that has a {{urn:iso:std:iso:14812:3.5.2.4,transport + - content: "{{<>,entity}} that has a {{<>,transport need}} to be fulfilled" notes: [] examples: [] diff --git a/concepts/concept-3.5.2.4.yaml b/concepts/concept-3.5.2.4.yaml index f69a380..6e3a087 100644 --- a/concepts/concept-3.5.2.4.yaml +++ b/concepts/concept-3.5.2.4.yaml @@ -14,9 +14,9 @@ eng: designation: need domain: transport definition: - - content: "{{urn:iso:std:iso:14812:3.5.1.4,user need,need}} to transport one or - more {{urn:iso:std:iso:14812:3.1.1.3,material entity,material entities}} to - a different {{urn:iso:std:iso:14812:3.4.1.1,location}}" + - content: "{{<>,user need,need}} to transport one or + more {{<>,material entity,material entities}} to + a different {{<>,location}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.3.1.yaml b/concepts/concept-3.5.3.1.yaml index 652b863..389e2f1 100644 --- a/concepts/concept-3.5.3.1.yaml +++ b/concepts/concept-3.5.3.1.yaml @@ -10,7 +10,7 @@ eng: normative_status: preferred designation: service definition: - - content: functionality that fulfils one or more {{urn:iso:std:iso:14812:3.5.3.4,ITS + - content: functionality that fulfils one or more {{<>,ITS user need}} notes: [] examples: [] diff --git a/concepts/concept-3.5.3.2.yaml b/concepts/concept-3.5.3.2.yaml index 71ec0ef..c73257a 100644 --- a/concepts/concept-3.5.3.2.yaml +++ b/concepts/concept-3.5.3.2.yaml @@ -10,12 +10,12 @@ eng: normative_status: preferred designation: service provider definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.1,entity}} that delivers one or more {{urn:iso:std:iso:14812:3.5.3.1,ITS + - content: "{{<>,entity}} that delivers one or more {{<>,ITS service}}" notes: - - content: "{{urn:iso:std:iso:14812:3.1.2.5,cooperative ITS,Cooperative ITS}} services + - content: "{{<>,cooperative ITS,Cooperative ITS}} services often require multiple entities cooperatively working together to provide a - unified {{urn:iso:std:iso:14812:3.5.2.1,service}} where the individual entities + unified {{<>,service}} where the individual entities are simultaneously ITS service providers and ITS users." examples: [] language_code: eng diff --git a/concepts/concept-3.5.3.3.yaml b/concepts/concept-3.5.3.3.yaml index d5cd97e..c41e960 100644 --- a/concepts/concept-3.5.3.3.yaml +++ b/concepts/concept-3.5.3.3.yaml @@ -10,7 +10,7 @@ eng: normative_status: preferred designation: user definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.1,entity}} that has an {{urn:iso:std:iso:14812:3.5.3.4,ITS + - content: "{{<>,entity}} that has an {{<>,ITS user need}} to be fulfilled" notes: [] examples: [] diff --git a/concepts/concept-3.5.3.4.yaml b/concepts/concept-3.5.3.4.yaml index 541f53d..0493a67 100644 --- a/concepts/concept-3.5.3.4.yaml +++ b/concepts/concept-3.5.3.4.yaml @@ -13,9 +13,9 @@ eng: normative_status: preferred designation: need definition: - - content: "{{urn:iso:std:iso:14812:3.5.1.4,user need,need}} of an {{urn:iso:std:iso:14812:3.1.1.1,entity}} - external to the {{urn:iso:std:iso:14812:3.1.2.4,intelligent transport system}} - for a {{urn:iso:std:iso:14812:3.1.2.3,surface transport system}} benefit that + - content: "{{<>,user need,need}} of an {{<>,entity}} + external to the {{<>,intelligent transport system}} + for a {{<>,surface transport system}} benefit that can be met with the use of information, communication, sensor, and/or control technologies" notes: [] diff --git a/concepts/concept-3.5.4.1.yaml b/concepts/concept-3.5.4.1.yaml index d222553..7755582 100644 --- a/concepts/concept-3.5.4.1.yaml +++ b/concepts/concept-3.5.4.1.yaml @@ -11,8 +11,8 @@ eng: designation: service domain: ITS-S definition: - - content: performance of one or more tasks to fulfil an {{urn:iso:std:iso:14812:3.5.4.4,ITS-S - user need}} for an {{urn:iso:std:iso:14812:3.5.4.3,ITS-S user}} + - content: performance of one or more tasks to fulfil an {{<>,ITS-S + user need}} for an {{<>,ITS-S user}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.4.2.yaml b/concepts/concept-3.5.4.2.yaml index 8509e40..9004534 100644 --- a/concepts/concept-3.5.4.2.yaml +++ b/concepts/concept-3.5.4.2.yaml @@ -11,8 +11,8 @@ eng: designation: service provider domain: ITS-S definition: - - content: "{{urn:iso:std:iso:14812:3.2.7.3,ITS station,ITS-S}} that delivers one - or more {{urn:iso:std:iso:14812:3.5.4.1,ITS-S service,ITS-S services}}" + - content: "{{<>,ITS station,ITS-S}} that delivers one + or more {{<>,ITS-S service,ITS-S services}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.4.3.yaml b/concepts/concept-3.5.4.3.yaml index fcd3515..b514735 100644 --- a/concepts/concept-3.5.4.3.yaml +++ b/concepts/concept-3.5.4.3.yaml @@ -11,7 +11,7 @@ eng: designation: user domain: ITS-S definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.1,entity}} that has an {{urn:iso:std:iso:14812:3.5.4.4,ITS-S + - content: "{{<>,entity}} that has an {{<>,ITS-S user need}} to be fulfilled" notes: [] examples: [] diff --git a/concepts/concept-3.5.4.4.yaml b/concepts/concept-3.5.4.4.yaml index 6891ea5..6485b16 100644 --- a/concepts/concept-3.5.4.4.yaml +++ b/concepts/concept-3.5.4.4.yaml @@ -14,8 +14,8 @@ eng: designation: need domain: ITS-S definition: - - content: "{{urn:iso:std:iso:14812:3.5.1.4,user need,need}} for processing within - a {{urn:iso:std:iso:14812:3.2.7.1,bounded secured managed domain,bounded, secure, + - content: "{{<>,user need,need}} for processing within + a {{<>,bounded secured managed domain,bounded, secure, managed domain}}" notes: [] examples: [] diff --git a/concepts/concept-3.5.5.1.yaml b/concepts/concept-3.5.5.1.yaml index 434e8ba..879303a 100644 --- a/concepts/concept-3.5.5.1.yaml +++ b/concepts/concept-3.5.5.1.yaml @@ -11,7 +11,7 @@ eng: designation: communication process domain: ITS-S definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.1,entity}} that delivers one or more {{urn:iso:std:iso:14812:3.5.5.2,ITS-S + - content: "{{<>,entity}} that delivers one or more {{<>,ITS-S communications service,ITS-S communication services}}" notes: [] examples: [] diff --git a/concepts/concept-3.5.5.2.yaml b/concepts/concept-3.5.5.2.yaml index 0a49cdf..372f654 100644 --- a/concepts/concept-3.5.5.2.yaml +++ b/concepts/concept-3.5.5.2.yaml @@ -11,8 +11,8 @@ eng: designation: communication service domain: ITS-S definition: - - content: performance of one or more tasks to fulfil an {{urn:iso:std:iso:14812:3.5.5.4,ITS-S - communications need,ITS-S communication need}} for an {{urn:iso:std:iso:14812:3.5.5.3,ITS-S + - content: performance of one or more tasks to fulfil an {{<>,ITS-S + communications need,ITS-S communication need}} for an {{<>,ITS-S communications user,ITS-S communication user}} notes: [] examples: [] diff --git a/concepts/concept-3.5.5.3.yaml b/concepts/concept-3.5.5.3.yaml index 670d558..48a1286 100644 --- a/concepts/concept-3.5.5.3.yaml +++ b/concepts/concept-3.5.5.3.yaml @@ -11,7 +11,7 @@ eng: designation: communication user domain: ITS-S definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.1,entity}} that has an {{urn:iso:std:iso:14812:3.5.5.4,ITS-S + - content: "{{<>,entity}} that has an {{<>,ITS-S communications need,ITS-S communication need}} to be fulfilled" notes: [] examples: [] diff --git a/concepts/concept-3.5.5.4.yaml b/concepts/concept-3.5.5.4.yaml index 4ddb0c2..da22ca3 100644 --- a/concepts/concept-3.5.5.4.yaml +++ b/concepts/concept-3.5.5.4.yaml @@ -11,9 +11,9 @@ eng: designation: communication need domain: ITS-S definition: - - content: "{{urn:iso:std:iso:14812:3.5.1.4,user need,need}} for communication functionality - that connects an {{urn:iso:std:iso:14812:3.2.7.3,ITS station,ITS-S}} to other - {{urn:iso:std:iso:14812:3.3.5.4,node,nodes}}" + - content: "{{<>,user need,need}} for communication functionality + that connects an {{<>,ITS station,ITS-S}} to other + {{<>,node,nodes}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.6.1.yaml b/concepts/concept-3.5.6.1.yaml index 72a1de0..b097f12 100644 --- a/concepts/concept-3.5.6.1.yaml +++ b/concepts/concept-3.5.6.1.yaml @@ -10,8 +10,8 @@ eng: normative_status: preferred designation: public transport service definition: - - content: "{{urn:iso:std:iso:14812:3.5.2.1,transport service}} that is publicly - accessible enabling the movement of one or more {{urn:iso:std:iso:14812:3.1.1.6,person,persons}}" + - content: "{{<>,transport service}} that is publicly + accessible enabling the movement of one or more {{<>,person,persons}}" notes: - content: A public transport service can be scheduled or on-demand. - content: A public transport service is based on the use of publicly accessible diff --git a/concepts/concept-3.5.6.2.yaml b/concepts/concept-3.5.6.2.yaml index 29643f0..662841a 100644 --- a/concepts/concept-3.5.6.2.yaml +++ b/concepts/concept-3.5.6.2.yaml @@ -7,16 +7,16 @@ eng: normative_status: preferred designation: shared transport service definition: - - content: "{{urn:iso:std:iso:14812:3.5.2.1,transport service}} that relies upon - the same {{urn:iso:std:iso:14812:3.1.6.2,resource,resources}} to fulfil the - {{urn:iso:std:iso:14812:3.5.2.4,transport need,transport needs}} of multiple - unrelated {{urn:iso:std:iso:14812:3.5.2.3,transport user,transport users}} and - where the {{urn:iso:std:iso:14812:3.5.2.2,transport provider}} has the primary + - content: "{{<>,transport service}} that relies upon + the same {{<>,resource,resources}} to fulfil the + {{<>,transport need,transport needs}} of multiple + unrelated {{<>,transport user,transport users}} and + where the {{<>,transport provider}} has the primary responsibility for the operation of the transport mode" notes: - content: A shared transport service might not be dependent upon a vehicle and/or could be multi-modal. For example, a letter courier service could rely on walking - and {{urn:iso:std:iso:14812:3.5.6.1,public transport}}. + and {{<>,public transport}}. - content: Responsibilities of the transport service can be further delegated to others. For example, a courier service relying on public transport would delegate the operation of the transport mode to the public transport operator. diff --git a/concepts/concept-3.5.6.3.yaml b/concepts/concept-3.5.6.3.yaml index a84eca5..b05e15e 100644 --- a/concepts/concept-3.5.6.3.yaml +++ b/concepts/concept-3.5.6.3.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: shared vehicle service definition: - - content: "{{urn:iso:std:iso:14812:3.5.2.1,transport service}} that {{urn:iso:std:iso:14812:3.5.9.2,sequential,sequentially}} - provides the same {{urn:iso:std:iso:14812:3.7.1.1,vehicle,vehicles}} to multiple - unrelated {{urn:iso:std:iso:14812:3.5.2.3,transport user,transport users}} and + - content: "{{<>,transport service}} that {{<>,sequential,sequentially}} + provides the same {{<>,vehicle,vehicles}} to multiple + unrelated {{<>,transport user,transport users}} and where the transport user has the primary responsibility for the operation of the vehicle" notes: diff --git a/concepts/concept-3.5.6.4.yaml b/concepts/concept-3.5.6.4.yaml index e6817ab..05b1ba0 100644 --- a/concepts/concept-3.5.6.4.yaml +++ b/concepts/concept-3.5.6.4.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: transport sharing definition: - - content: using a {{urn:iso:std:iso:14812:3.5.6.2,shared transport service}} + - content: using a {{<>,shared transport service}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.6.5.yaml b/concepts/concept-3.5.6.5.yaml index 6e8c771..1c7c359 100644 --- a/concepts/concept-3.5.6.5.yaml +++ b/concepts/concept-3.5.6.5.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: vehicle sharing definition: - - content: using a {{urn:iso:std:iso:14812:3.5.6.3,shared vehicle service}} + - content: using a {{<>,shared vehicle service}} notes: - content: This term can be specialized by replacing "vehicle" with any defined vehicle type. However, in some cases the preferred form is to consolidate terms diff --git a/concepts/concept-3.5.7.1.yaml b/concepts/concept-3.5.7.1.yaml index af631ad..5c2c1e0 100644 --- a/concepts/concept-3.5.7.1.yaml +++ b/concepts/concept-3.5.7.1.yaml @@ -10,11 +10,11 @@ eng: normative_status: preferred designation: shared mobility contract model definition: - - content: legal framework for the agreement between a {{urn:iso:std:iso:14812:3.5.1.2,service - provider}} and a {{urn:iso:std:iso:14812:3.5.3.4,user}} + - content: legal framework for the agreement between a {{<>,service + provider}} and a {{<>,user}} notes: - content: Contracts can be via a third party, implied or verbal, especially in - the case of {{urn:iso:std:iso:14812:3.5.7.5,peer-to-peer}}. + the case of {{<>,peer-to-peer}}. examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.5.7.2.yaml b/concepts/concept-3.5.7.2.yaml index a6fa8c2..639182b 100644 --- a/concepts/concept-3.5.7.2.yaml +++ b/concepts/concept-3.5.7.2.yaml @@ -7,11 +7,11 @@ eng: normative_status: preferred designation: corporate customer model definition: - - content: "{{urn:iso:std:iso:14812:3.5.7.1,contractual model}} where the {{urn:iso:std:iso:14812:3.5.3.4,user}} - is a {{urn:iso:std:iso:14812:3.5.8.2,commercial}} {{urn:iso:std:iso:14812:3.1.1.1,entity}}" + - content: "{{<>,contractual model}} where the {{<>,user}} + is a {{<>,commercial}} {{<>,entity}}" notes: [] examples: - - content: A business purchasing monthly {{urn:iso:std:iso:14812:3.5.6.1,public + - content: A business purchasing monthly {{<>,public transport}} passes for its employees. - content: A commercial entity using a commercial courier service for package delivery. language_code: eng diff --git a/concepts/concept-3.5.7.3.yaml b/concepts/concept-3.5.7.3.yaml index 21f04af..59ddde7 100644 --- a/concepts/concept-3.5.7.3.yaml +++ b/concepts/concept-3.5.7.3.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: private customer model definition: - - content: "{{urn:iso:std:iso:14812:3.5.7.1,contractual model}} where the {{urn:iso:std:iso:14812:3.5.3.4,user}} + - content: "{{<>,contractual model}} where the {{<>,user}} is an individual" notes: [] examples: [] diff --git a/concepts/concept-3.5.7.4.yaml b/concepts/concept-3.5.7.4.yaml index ae023c4..61a9a6e 100644 --- a/concepts/concept-3.5.7.4.yaml +++ b/concepts/concept-3.5.7.4.yaml @@ -7,11 +7,11 @@ eng: normative_status: preferred designation: government customer model definition: - - content: "{{urn:iso:std:iso:14812:3.5.7.1,contractual model}} where the {{urn:iso:std:iso:14812:3.5.3.4,user}} - is a governmental {{urn:iso:std:iso:14812:3.1.1.1,entity}}" + - content: "{{<>,contractual model}} where the {{<>,user}} + is a governmental {{<>,entity}}" notes: [] examples: - - content: A governmental entity using a {{urn:iso:std:iso:14812:3.5.8.2,commercial}} + - content: A governmental entity using a {{<>,commercial}} courier service for package delivery. language_code: eng entry_status: valid diff --git a/concepts/concept-3.5.7.5.yaml b/concepts/concept-3.5.7.5.yaml index 1423403..c7d82d5 100644 --- a/concepts/concept-3.5.7.5.yaml +++ b/concepts/concept-3.5.7.5.yaml @@ -8,11 +8,11 @@ eng: designation: peer-to-peer domain: transport service definition: - - content: "{{urn:iso:std:iso:14812:3.5.7.3,private customer model}} where the {{urn:iso:std:iso:14812:3.5.1.2,service + - content: "{{<>,private customer model}} where the {{<>,service provider}} is an individual" notes: - content: The customer and provider can connect and/or contract through a third-party - {{urn:iso:std:iso:14812:3.5.2.1,service}}. + {{<>,service}}. examples: - content: Ridesourcing. language_code: eng diff --git a/concepts/concept-3.5.8.1.yaml b/concepts/concept-3.5.8.1.yaml index 1157931..5f87253 100644 --- a/concepts/concept-3.5.8.1.yaml +++ b/concepts/concept-3.5.8.1.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: financial model definition: - - content: economic framework for the agreement between a {{urn:iso:std:iso:14812:3.5.1.2,service - provider}} and a {{urn:iso:std:iso:14812:3.5.3.4,user}} + - content: economic framework for the agreement between a {{<>,service + provider}} and a {{<>,user}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.8.2.yaml b/concepts/concept-3.5.8.2.yaml index 2bfbd6a..b631e40 100644 --- a/concepts/concept-3.5.8.2.yaml +++ b/concepts/concept-3.5.8.2.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: commercial definition: - - content: type of{{urn:iso:std:iso:14812:3.5.8.1,financial model}} where {{urn:iso:std:iso:14812:3.5.2.1,service,services}} + - content: type of{{<>,financial model}} where {{<>,service,services}} are provided with a profit motive notes: [] examples: [] diff --git a/concepts/concept-3.5.8.3.yaml b/concepts/concept-3.5.8.3.yaml index a2fc147..baa82d8 100644 --- a/concepts/concept-3.5.8.3.yaml +++ b/concepts/concept-3.5.8.3.yaml @@ -7,17 +7,17 @@ eng: normative_status: preferred designation: public definition: - - content: type of{{urn:iso:std:iso:14812:3.5.8.1,financial model}} where {{urn:iso:std:iso:14812:3.5.2.1,service,services}} + - content: type of{{<>,financial model}} where {{<>,service,services}} are provided by an administrative authority in an attempt to better serve societal interests notes: - - content: The {{urn:iso:std:iso:14812:3.5.2.1,transport service}} is typically + - content: The {{<>,transport service}} is typically offered to the transport consumer for less than the full capital and operating cost of providing the service, but this is not a requirement. - content: Typically, the administrative authority is a local government agency; but it could be another administrative authority, such as the national government - or a {{urn:iso:std:iso:14812:3.5.8.2,commercial}} {{urn:iso:std:iso:14812:3.1.1.1,entity}} - managing {{urn:iso:std:iso:14812:3.5.2.4,transport need,transport needs}} on + or a {{<>,commercial}} {{<>,entity}} + managing {{<>,transport need,transport needs}} on their campus. examples: [] language_code: eng diff --git a/concepts/concept-3.5.8.4.yaml b/concepts/concept-3.5.8.4.yaml index 0d6c6b9..075f952 100644 --- a/concepts/concept-3.5.8.4.yaml +++ b/concepts/concept-3.5.8.4.yaml @@ -7,11 +7,11 @@ eng: normative_status: preferred designation: cooperative definition: - - content: type of{{urn:iso:std:iso:14812:3.5.8.1,financial model}} where {{urn:iso:std:iso:14812:3.5.3.4,user,users}} - partner to defray the costs of {{urn:iso:std:iso:14812:3.5.2.1,service,services}} + - content: type of{{<>,financial model}} where {{<>,user,users}} + partner to defray the costs of {{<>,service,services}} notes: - - content: Cooperative models are exclusive {{urn:iso:std:iso:14812:3.5.8.2,commercial}} - and {{urn:iso:std:iso:14812:3.5.8.3,public}} models. + - content: Cooperative models are exclusive {{<>,commercial}} + and {{<>,public}} models. examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.5.8.5.yaml b/concepts/concept-3.5.8.5.yaml index 6088611..5d10b9b 100644 --- a/concepts/concept-3.5.8.5.yaml +++ b/concepts/concept-3.5.8.5.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: mutual benefit definition: - - content: "{{urn:iso:std:iso:14812:3.5.8.4,cooperative}} {{urn:iso:std:iso:14812:3.5.8.1,financial - model}} where {{urn:iso:std:iso:14812:3.5.3.4,user,users}} partner on a per-use + - content: "{{<>,cooperative}} {{<>,financial + model}} where {{<>,user,users}} partner on a per-use basis" notes: [] examples: [] diff --git a/concepts/concept-3.5.8.6.yaml b/concepts/concept-3.5.8.6.yaml index 3de5dc0..d074fad 100644 --- a/concepts/concept-3.5.8.6.yaml +++ b/concepts/concept-3.5.8.6.yaml @@ -8,9 +8,9 @@ eng: designation: fractional ownership domain: transport service definition: - - content: "{{urn:iso:std:iso:14812:3.5.8.4,cooperative}} {{urn:iso:std:iso:14812:3.5.8.1,financial - model}} where {{urn:iso:std:iso:14812:3.5.3.4,user,users}} partner to support - the purchase, maintenance and overhead costs associated with a {{urn:iso:std:iso:14812:3.5.2.1,service}}" + - content: "{{<>,cooperative}} {{<>,financial + model}} where {{<>,user,users}} partner to support + the purchase, maintenance and overhead costs associated with a {{<>,service}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.5.8.7.yaml b/concepts/concept-3.5.8.7.yaml index 55e5534..4b5c851 100644 --- a/concepts/concept-3.5.8.7.yaml +++ b/concepts/concept-3.5.8.7.yaml @@ -8,7 +8,7 @@ eng: designation: private domain: transport service definition: - - content: "{{urn:iso:std:iso:14812:3.5.8.1,financial model}} where {{urn:iso:std:iso:14812:3.5.2.1,service,services}} + - content: "{{<>,financial model}} where {{<>,service,services}} are provided to members of the owning organization without usage fees" notes: [] examples: diff --git a/concepts/concept-3.5.8.8.yaml b/concepts/concept-3.5.8.8.yaml index 33eb21b..6084ec4 100644 --- a/concepts/concept-3.5.8.8.yaml +++ b/concepts/concept-3.5.8.8.yaml @@ -7,15 +7,15 @@ eng: normative_status: preferred designation: membership-based definition: - - content: characteristic of a {{urn:iso:std:iso:14812:3.5.8.1,financial model}} - that requires {{urn:iso:std:iso:14812:3.5.3.4,user,users}} to enter into an - agreement prior to receiving {{urn:iso:std:iso:14812:3.5.2.1,service,services}} + - content: characteristic of a {{<>,financial model}} + that requires {{<>,user,users}} to enter into an + agreement prior to receiving {{<>,service,services}} notes: - content: The agreement can be associated with fees. - content: The agreement can be minimal, such as collecting user information for business purposes. - content: The membership can be granted as a part of a broader agreement. For example, - a university bus {{urn:iso:std:iso:14812:3.1.2.1,system}} can restrict access + a university bus {{<>,system}} can restrict access to students and faculty. examples: [] language_code: eng diff --git a/concepts/concept-3.5.8.9.yaml b/concepts/concept-3.5.8.9.yaml index 854d4df..7b1d661 100644 --- a/concepts/concept-3.5.8.9.yaml +++ b/concepts/concept-3.5.8.9.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: open-access definition: - - content: characteristic of a {{urn:iso:std:iso:14812:3.5.8.1,financial model}} - that does not require membership within an organization to receive {{urn:iso:std:iso:14812:3.5.2.1,service,services}} + - content: characteristic of a {{<>,financial model}} + that does not require membership within an organization to receive {{<>,service,services}} notes: - content: This includes models where membership is optional and can provide extra benefits. diff --git a/concepts/concept-3.5.9.1.yaml b/concepts/concept-3.5.9.1.yaml index 814b593..c11ddcb 100644 --- a/concepts/concept-3.5.9.1.yaml +++ b/concepts/concept-3.5.9.1.yaml @@ -7,10 +7,10 @@ eng: normative_status: preferred designation: operational model definition: - - content: logistical framework for the agreement between a {{urn:iso:std:iso:14812:3.5.1.2,service - provider}} and a {{urn:iso:std:iso:14812:3.5.3.4,user}} + - content: logistical framework for the agreement between a {{<>,service + provider}} and a {{<>,user}} notes: - - content: The logistical framework can set restrictions on how a {{urn:iso:std:iso:14812:3.6.2.1,passenger}} + - content: The logistical framework can set restrictions on how a {{<>,passenger}} and/or good is received, transported and/or delivered. examples: [] language_code: eng diff --git a/concepts/concept-3.5.9.2.yaml b/concepts/concept-3.5.9.2.yaml index a8805ba..1f8cf3b 100644 --- a/concepts/concept-3.5.9.2.yaml +++ b/concepts/concept-3.5.9.2.yaml @@ -7,10 +7,10 @@ eng: normative_status: preferred designation: sequential definition: - - content: "{{urn:iso:std:iso:14812:3.5.9.1,operational model}} where {{urn:iso:std:iso:14812:3.5.2.1,service,services}} - are provided to a single {{urn:iso:std:iso:14812:3.5.3.4,user}} at any one time" + - content: "{{<>,operational model}} where {{<>,service,services}} + are provided to a single {{<>,user}} at any one time" notes: - - content: A single transport consumer can request the transport of multiple {{urn:iso:std:iso:14812:3.6.2.1,passenger,passengers}}. + - content: A single transport consumer can request the transport of multiple {{<>,passenger,passengers}}. examples: - content: Traditional taxi service. language_code: eng diff --git a/concepts/concept-3.5.9.3.yaml b/concepts/concept-3.5.9.3.yaml index 500993d..f92503e 100644 --- a/concepts/concept-3.5.9.3.yaml +++ b/concepts/concept-3.5.9.3.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: concurrent definition: - - content: "{{urn:iso:std:iso:14812:3.5.9.1,operational model}} where {{urn:iso:std:iso:14812:3.5.2.1,service,services}} - can be provided to multiple {{urn:iso:std:iso:14812:3.5.3.4,user,users}} at + - content: "{{<>,operational model}} where {{<>,service,services}} + can be provided to multiple {{<>,user,users}} at any one time" notes: [] examples: [] diff --git a/concepts/concept-3.5.9.4.yaml b/concepts/concept-3.5.9.4.yaml index 39b059d..0b2f309 100644 --- a/concepts/concept-3.5.9.4.yaml +++ b/concepts/concept-3.5.9.4.yaml @@ -8,7 +8,7 @@ eng: designation: fixed route domain: transport service definition: - - content: "{{urn:iso:std:iso:14812:3.5.9.3,concurrent}} operation where transported + - content: "{{<>,concurrent}} operation where transported items can only be received or delivered at stopping points contained in a pre-defined sequence" notes: [] diff --git a/concepts/concept-3.5.9.5.yaml b/concepts/concept-3.5.9.5.yaml index 76dd3a4..f99f331 100644 --- a/concepts/concept-3.5.9.5.yaml +++ b/concepts/concept-3.5.9.5.yaml @@ -8,9 +8,9 @@ eng: designation: dynamic route domain: transport service definition: - - content: "{{urn:iso:std:iso:14812:3.5.9.3,concurrent}} operation where transported + - content: "{{<>,concurrent}} operation where transported items can only be received or delivered at stopping points within a pre-defined - {{urn:iso:std:iso:14812:3.5.2.1,service}} corridor" + {{<>,service}} corridor" notes: - content: The service corridor is defined by the provider, who may impose further restrictions on where stops are allowed. diff --git a/concepts/concept-3.5.9.6.yaml b/concepts/concept-3.5.9.6.yaml index 66daa8b..5d90160 100644 --- a/concepts/concept-3.5.9.6.yaml +++ b/concepts/concept-3.5.9.6.yaml @@ -8,9 +8,9 @@ eng: designation: paired on-demand domain: transport service definition: - - content: "{{urn:iso:std:iso:14812:3.5.9.3,concurrent}} operation where the {{urn:iso:std:iso:14812:3.5.2.2,transport + - content: "{{<>,concurrent}} operation where the {{<>,transport provider}} may choose to divert from its path to service a new request from - another {{urn:iso:std:iso:14812:3.5.2.3,transport user,transport users}} while + another {{<>,transport user,transport users}} while servicing an earlier transport user" notes: [] examples: diff --git a/concepts/concept-3.6.1.1.yaml b/concepts/concept-3.6.1.1.yaml index d0c7895..b4b0bb1 100644 --- a/concepts/concept-3.6.1.1.yaml +++ b/concepts/concept-3.6.1.1.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: traveller definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.6,person}} who is headed to a destination" + - content: "{{<>,person}} who is headed to a destination" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.6.1.2.yaml b/concepts/concept-3.6.1.2.yaml index 698735e..0ecca67 100644 --- a/concepts/concept-3.6.1.2.yaml +++ b/concepts/concept-3.6.1.2.yaml @@ -7,12 +7,12 @@ eng: normative_status: preferred designation: road user definition: - - content: mobile {{urn:iso:std:iso:14812:3.1.1.3,material entity}} within the {{urn:iso:std:iso:14812:3.3.1.2,road + - content: mobile {{<>,material entity}} within the {{<>,road reservation}} notes: [] examples: - - content: "{{urn:iso:std:iso:14812:3.6.1.3,pedestrian,Pedestrians}}, road work - personnel, {{urn:iso:std:iso:14812:3.6.2.2,vehicle occupant,vehicle occupants}}, + - content: "{{<>,pedestrian,Pedestrians}}, road work + personnel, {{<>,vehicle occupant,vehicle occupants}}, occupied and unoccupied vehicles, horses, etc." language_code: eng entry_status: valid diff --git a/concepts/concept-3.6.1.3.yaml b/concepts/concept-3.6.1.3.yaml index 8147a22..6c62f85 100644 --- a/concepts/concept-3.6.1.3.yaml +++ b/concepts/concept-3.6.1.3.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: pedestrian definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.6,person}} who is travelling on foot" + - content: "{{<>,person}} who is travelling on foot" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.6.2.1.yaml b/concepts/concept-3.6.2.1.yaml index b371ec8..9044722 100644 --- a/concepts/concept-3.6.2.1.yaml +++ b/concepts/concept-3.6.2.1.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: passenger definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.6,person}} who has a reservation to travel - or is travelling in a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} except for any - crew, staff or {{urn:iso:std:iso:14812:3.6.2.3,driver,drivers}}" + - content: "{{<>,person}} who has a reservation to travel + or is travelling in a {{<>,vehicle}} except for any + crew, staff or {{<>,driver,drivers}}" notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.6.2.2.yaml b/concepts/concept-3.6.2.2.yaml index 2ca2fd4..aa9ed7d 100644 --- a/concepts/concept-3.6.2.2.yaml +++ b/concepts/concept-3.6.2.2.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: vehicle occupant definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.6,person}} in or on a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}}" + - content: "{{<>,person}} in or on a {{<>,vehicle}}" notes: - - content: A vehicle occupant in a stationary vehicle is not necessarily a {{urn:iso:std:iso:14812:3.6.1.1,traveller}}. + - content: A vehicle occupant in a stationary vehicle is not necessarily a {{<>,traveller}}. examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.6.2.3.yaml b/concepts/concept-3.6.2.3.yaml index ff03526..6f361ca 100644 --- a/concepts/concept-3.6.2.3.yaml +++ b/concepts/concept-3.6.2.3.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: driver definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.6,person}} that is currently responsible - for the {{urn:iso:std:iso:14812:3.7.3.1,dynamic driving task}} for the {{urn:iso:std:iso:14812:3.7.1.1,vehicle}}" + - content: "{{<>,person}} that is currently responsible + for the {{<>,dynamic driving task}} for the {{<>,vehicle}}" notes: - content: The driver is typically on-board the vehicle but could be remote from the vehicle or automated logic. diff --git a/concepts/concept-3.6.2.4.yaml b/concepts/concept-3.6.2.4.yaml index 59877af..2c573e1 100644 --- a/concepts/concept-3.6.2.4.yaml +++ b/concepts/concept-3.6.2.4.yaml @@ -10,9 +10,9 @@ eng: normative_status: preferred designation: conventional driver definition: - - content: "{{urn:iso:std:iso:14812:3.6.2.3,driver}} that performs the {{urn:iso:std:iso:14812:3.7.3.1,dynamic - driving task}} using the {{urn:iso:std:iso:14812:3.7.1.1,vehicle,vehicle's}} - {{urn:iso:std:iso:14812:3.7.1.5,built-in vehicle input device,built-in input + - content: "{{<>,driver}} that performs the {{<>,dynamic + driving task}} using the {{<>,vehicle,vehicle's}} + {{<>,built-in vehicle input device,built-in input devices}} to control the longitudinal and lateral movement of the vehicle" notes: [] examples: [] diff --git a/concepts/concept-3.6.2.5.yaml b/concepts/concept-3.6.2.5.yaml index 558e26c..1a4a105 100644 --- a/concepts/concept-3.6.2.5.yaml +++ b/concepts/concept-3.6.2.5.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: remote driver definition: - - content: "{{urn:iso:std:iso:14812:3.6.2.3,driver}} that performs the {{urn:iso:std:iso:14812:3.7.3.1,dynamic - driving task}} without using the {{urn:iso:std:iso:14812:3.7.1.1,vehicle,vehicle's}} - {{urn:iso:std:iso:14812:3.7.1.5,built-in vehicle input device,built-in input + - content: "{{<>,driver}} that performs the {{<>,dynamic + driving task}} without using the {{<>,vehicle,vehicle's}} + {{<>,built-in vehicle input device,built-in input devices}} to control the longitudinal and lateral movement of the vehicle" notes: - content: A remote driver can use a variety of physical input devices, but none diff --git a/concepts/concept-3.7.1.1.yaml b/concepts/concept-3.7.1.1.yaml index 0c49634..4b90904 100644 --- a/concepts/concept-3.7.1.1.yaml +++ b/concepts/concept-3.7.1.1.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: vehicle definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.3,material entity}} designed to transport + - content: "{{<>,material entity}} designed to transport people or physical goods by changing its physical position" notes: [] examples: [] diff --git a/concepts/concept-3.7.1.2.yaml b/concepts/concept-3.7.1.2.yaml index d189328..cab2f2b 100644 --- a/concepts/concept-3.7.1.2.yaml +++ b/concepts/concept-3.7.1.2.yaml @@ -10,7 +10,7 @@ eng: normative_status: admitted designation: engine definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.3,material entity}} that converts energy + - content: "{{<>,material entity}} that converts energy into mechanical motion" notes: [] examples: [] diff --git a/concepts/concept-3.7.1.3.yaml b/concepts/concept-3.7.1.3.yaml index 247adf3..00c7dc9 100644 --- a/concepts/concept-3.7.1.3.yaml +++ b/concepts/concept-3.7.1.3.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: wheel definition: - - content: circular {{urn:iso:std:iso:14812:3.1.1.3,material entity}} that rotates - about an axle to facilitate movement of the {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} + - content: circular {{<>,material entity}} that rotates + about an axle to facilitate movement of the {{<>,vehicle}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.7.1.4.yaml b/concepts/concept-3.7.1.4.yaml index 0a585f1..6445c14 100644 --- a/concepts/concept-3.7.1.4.yaml +++ b/concepts/concept-3.7.1.4.yaml @@ -10,8 +10,8 @@ eng: normative_status: preferred designation: input device definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.3,material entity}} that can affect the - {{urn:iso:std:iso:14812:3.7.1.1,vehicle,vehicle's}} operation" + - content: "{{<>,material entity}} that can affect the + {{<>,vehicle,vehicle's}} operation" notes: - content: Input devices include those used to control the motion of the vehicle (e.g. a brake pedal), the state of vehicular equipment (e.g. headlight control), diff --git a/concepts/concept-3.7.1.5.yaml b/concepts/concept-3.7.1.5.yaml index f15cc45..7d5c114 100644 --- a/concepts/concept-3.7.1.5.yaml +++ b/concepts/concept-3.7.1.5.yaml @@ -10,11 +10,11 @@ eng: normative_status: preferred designation: built-in input device definition: - - content: "{{urn:iso:std:iso:14812:3.7.1.4,vehicle input device,input device}} - designed to be physically {{urn:iso:std:iso:14812:3.2.3.6,connected}} to a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} + - content: "{{<>,vehicle input device,input device}} + designed to be physically {{<>,connected}} to a {{<>,vehicle}} and to remain connected even when the vehicle is not in use" notes: - - content: Built-in input devices include devices that can be temporarily {{urn:iso:std:iso:14812:3.7.4.3,disconnected}} + - content: Built-in input devices include devices that can be temporarily {{<>,disconnected}} for security reasons (e.g. some radios are equipped with detachable front panels). - content: Built-in input devices are typically considered to be a part of the vehicle. - content: Built-in input devices require a maintenance operation to connect or diff --git a/concepts/concept-3.7.1.6.yaml b/concepts/concept-3.7.1.6.yaml index 79b6f11..8feb9e5 100644 --- a/concepts/concept-3.7.1.6.yaml +++ b/concepts/concept-3.7.1.6.yaml @@ -10,17 +10,17 @@ eng: normative_status: preferred designation: nomadic input device definition: - - content: "{{urn:iso:std:iso:14812:3.7.1.4,vehicle input device,input device}} - that can be carried into, or in near proximity of, a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} - and {{urn:iso:std:iso:14812:3.2.3.6,connected}} as desired" + - content: "{{<>,vehicle input device,input device}} + that can be carried into, or in near proximity of, a {{<>,vehicle}} + and {{<>,connected}} as desired" notes: - - content: NDs are often more closely associated with a {{urn:iso:std:iso:14812:3.1.1.6,person}} + - content: NDs are often more closely associated with a {{<>,person}} than they are with the vehicle. - content: Nomadic input devices do not require a maintenance operation to connect or disconnect. examples: - content: A smartphone connected to a vehicle (via USB or Bluetooth) to provide - {{urn:iso:std:iso:14812:3.6.2.3,driver}} navigation on the vehicle's large screen + {{<>,driver}} navigation on the vehicle's large screen display language_code: eng entry_status: valid diff --git a/concepts/concept-3.7.1.7.yaml b/concepts/concept-3.7.1.7.yaml index f829a24..5f9358c 100644 --- a/concepts/concept-3.7.1.7.yaml +++ b/concepts/concept-3.7.1.7.yaml @@ -10,9 +10,9 @@ eng: normative_status: preferred designation: remote input device definition: - - content: "{{urn:iso:std:iso:14812:3.7.1.4,vehicle input device,input device}} - designed to be electronically {{urn:iso:std:iso:14812:3.2.3.6,connected}} to - a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} even when the vehicle is not in + - content: "{{<>,vehicle input device,input device}} + designed to be electronically {{<>,connected}} to + a {{<>,vehicle}} even when the vehicle is not in close proximity" notes: [] examples: [] diff --git a/concepts/concept-3.7.2.1.yaml b/concepts/concept-3.7.2.1.yaml index 3300b22..5ee8097 100644 --- a/concepts/concept-3.7.2.1.yaml +++ b/concepts/concept-3.7.2.1.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: speed definition: - - content: rate of change of a {{urn:iso:std:iso:14812:3.1.1.3,material entity,material + - content: rate of change of a {{<>,material entity,material entity's}} position with respect to a frame of reference notes: - content: Speed is a function of time. diff --git a/concepts/concept-3.7.2.2.yaml b/concepts/concept-3.7.2.2.yaml index 2e8e97a..f8352f0 100644 --- a/concepts/concept-3.7.2.2.yaml +++ b/concepts/concept-3.7.2.2.yaml @@ -14,7 +14,7 @@ eng: designation: top speed domain: vehicle definition: - - content: maximum {{urn:iso:std:iso:14812:3.7.2.1,speed}} at which a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} + - content: maximum {{<>,speed}} at which a {{<>,vehicle}} is intended to operate for a sustained period of time notes: - content: The term "top speed" is defined in <> in relation diff --git a/concepts/concept-3.7.3.1.yaml b/concepts/concept-3.7.3.1.yaml index 605da70..3195887 100644 --- a/concepts/concept-3.7.3.1.yaml +++ b/concepts/concept-3.7.3.1.yaml @@ -11,10 +11,10 @@ eng: designation: DDT definition: - content: all real-time operational and tactical functions required to operate - a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} in on-road traffic + a {{<>,vehicle}} in on-road traffic notes: - content: The DDT includes lateral vehicle motion control, longitudinal vehicle - motion control, monitoring the driving {{urn:iso:std:iso:14812:3.1.3.11,environment}}, + motion control, monitoring the driving {{<>,environment}}, object and event response execution, manoeuvre planning and enhancing conspicuity. - content: The DDT excludes strategic functions such as trip scheduling and selection of destinations and waypoints. diff --git a/concepts/concept-3.7.3.10.yaml b/concepts/concept-3.7.3.10.yaml index afe0d67..f41fb87 100644 --- a/concepts/concept-3.7.3.10.yaml +++ b/concepts/concept-3.7.3.10.yaml @@ -10,8 +10,8 @@ eng: normative_status: preferred designation: Automated Driving System definition: - - content: "{{urn:iso:std:iso:14812:3.7.3.6,driving automation system}} that is - able to perform the entire {{urn:iso:std:iso:14812:3.7.3.1,dynamic driving task,DDT}} + - content: "{{<>,driving automation system}} that is + able to perform the entire {{<>,dynamic driving task,DDT}} on a sustained basis" notes: - content: The abbreviated form ("ADS") is the most preferred form and the alternative diff --git a/concepts/concept-3.7.3.11.yaml b/concepts/concept-3.7.3.11.yaml index d3826d5..ea3a4c5 100644 --- a/concepts/concept-3.7.3.11.yaml +++ b/concepts/concept-3.7.3.11.yaml @@ -13,17 +13,17 @@ eng: normative_status: preferred designation: level 3 Automated Driving System definition: - - content: "{{urn:iso:std:iso:14812:3.7.3.10,ADS}} designed with the expectation - that the {{urn:iso:std:iso:14812:3.7.3.4,fallback-ready user}} is available + - content: "{{<>,ADS}} designed with the expectation + that the {{<>,fallback-ready user}} is available to intervene" notes: - - content: Level 3 ADSs are restricted to operating within a specific {{urn:iso:std:iso:14812:3.7.3.2,operational + - content: Level 3 ADSs are restricted to operating within a specific {{<>,operational design domain,ODD}}. - - content: Other driving automation levels include "{{urn:iso:std:iso:14812:3.7.3.8,level - 1 driving automation}}", "{{urn:iso:std:iso:14812:3.7.3.9,level 2 driving automation}}", - "{{urn:iso:std:iso:14812:3.7.3.12,level 4 ADS}}", and "{{urn:iso:std:iso:14812:3.7.3.13,level + - content: Other driving automation levels include "{{<>,level + 1 driving automation}}", "{{<>,level 2 driving automation}}", + "{{<>,level 4 ADS}}", and "{{<>,level 5 ADS}}". - - content: The user can intervene due to an ADS-issued request, a {{urn:iso:std:iso:14812:3.7.3.1,dynamic + - content: The user can intervene due to an ADS-issued request, a {{<>,dynamic driving task,DDT}} performance-relevant system failure, or other reasons. examples: [] language_code: eng diff --git a/concepts/concept-3.7.3.12.yaml b/concepts/concept-3.7.3.12.yaml index a0649dc..25efa74 100644 --- a/concepts/concept-3.7.3.12.yaml +++ b/concepts/concept-3.7.3.12.yaml @@ -13,15 +13,15 @@ eng: normative_status: preferred designation: level 4 Automated Driving System definition: - - content: "{{urn:iso:std:iso:14812:3.7.3.10,ADS}} that is capable of operating - within a specific {{urn:iso:std:iso:14812:3.7.3.2,operational design domain,ODD}} - and providing its own {{urn:iso:std:iso:14812:3.7.3.3,fallback}}, without any - expectation that a human {{urn:iso:std:iso:14812:3.6.2.3,driver}} will respond + - content: "{{<>,ADS}} that is capable of operating + within a specific {{<>,operational design domain,ODD}} + and providing its own {{<>,fallback}}, without any + expectation that a human {{<>,driver}} will respond to a request to intervene" notes: - - content: Other driving automation levels include "{{urn:iso:std:iso:14812:3.7.3.8,level - 1 driving automation}}", "{{urn:iso:std:iso:14812:3.7.3.9,level 2 driving automation}}", - "{{urn:iso:std:iso:14812:3.7.3.11,level 3 ADS}}", and "{{urn:iso:std:iso:14812:3.7.3.13,level + - content: Other driving automation levels include "{{<>,level + 1 driving automation}}", "{{<>,level 2 driving automation}}", + "{{<>,level 3 ADS}}", and "{{<>,level 5 ADS}}". examples: [] language_code: eng diff --git a/concepts/concept-3.7.3.13.yaml b/concepts/concept-3.7.3.13.yaml index 5e08220..2689e76 100644 --- a/concepts/concept-3.7.3.13.yaml +++ b/concepts/concept-3.7.3.13.yaml @@ -13,15 +13,15 @@ eng: normative_status: preferred designation: level 5 Automated Driving System definition: - - content: "{{urn:iso:std:iso:14812:3.7.3.10,ADS}} that is capable of unconditional - (i.e. not {{urn:iso:std:iso:14812:3.7.3.2,operational design domain,ODD}}-specific) - operation and providing its own {{urn:iso:std:iso:14812:3.7.3.3,fallback}}, - without any expectation that a human {{urn:iso:std:iso:14812:3.6.2.3,driver}} + - content: "{{<>,ADS}} that is capable of unconditional + (i.e. not {{<>,operational design domain,ODD}}-specific) + operation and providing its own {{<>,fallback}}, + without any expectation that a human {{<>,driver}} will respond to a request to intervene" notes: - - content: Other driving automation levels include "{{urn:iso:std:iso:14812:3.7.3.8,level - 1 driving automation}}", "{{urn:iso:std:iso:14812:3.7.3.9,level 2 driving automation}}", - "{{urn:iso:std:iso:14812:3.7.3.11,level 3 ADS}}" and "{{urn:iso:std:iso:14812:3.7.3.12,level + - content: Other driving automation levels include "{{<>,level + 1 driving automation}}", "{{<>,level 2 driving automation}}", + "{{<>,level 3 ADS}}" and "{{<>,level 4 ADS}}". examples: [] language_code: eng diff --git a/concepts/concept-3.7.3.14.yaml b/concepts/concept-3.7.3.14.yaml index c2dbc65..7147974 100644 --- a/concepts/concept-3.7.3.14.yaml +++ b/concepts/concept-3.7.3.14.yaml @@ -11,8 +11,8 @@ eng: designation: automation-equipped conventional vehicle domain: driving automation definition: - - content: "{{urn:iso:std:iso:14812:3.7.1.1,vehicle}} designed to be operated by - a {{urn:iso:std:iso:14812:3.1.1.6,person}} during part or all of every _trip_." + - content: "{{<>,vehicle}} designed to be operated by + a {{<>,person}} during part or all of every _trip_." notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.7.3.15.yaml b/concepts/concept-3.7.3.15.yaml index 6da722f..546622f 100644 --- a/concepts/concept-3.7.3.15.yaml +++ b/concepts/concept-3.7.3.15.yaml @@ -16,7 +16,7 @@ eng: normative_status: deprecated designation: autonomous vehicle definition: - - content: "{{urn:iso:std:iso:14812:3.7.1.1,vehicle}} integrated with an {{urn:iso:std:iso:14812:3.7.3.10,ADS}}" + - content: "{{<>,vehicle}} integrated with an {{<>,ADS}}" notes: - content: The terms "automated vehicle" and "AV" are often used in a colloquial form. However, these terms can be used to mean either an "ADS-equipped vehicle" @@ -25,17 +25,17 @@ eng: - content: The term "autonomous vehicle" is also often used in a colloquial form and is even less well defined. The term is particularly problematic because the word "autonomous" has been used for a long time in the robotics and artificial - intelligence research communities to signify {{urn:iso:std:iso:14812:3.1.2.1,system,systems}} + intelligence research communities to signify {{<>,system,systems}} that have the ability and authority to make decisions independently and self-sufficiently. Due to its imprecise and overly broad meaning, use of the term "autonomous vehicle" is discouraged. - content: This term can be, and when possible should be, refined by identifying the level of automation. For example, the terms "level 5 ADS-equipped vehicle" and "level 5 automated vehicle" should be interpreted as "ADS-equipped vehicle - where the ADS is a {{urn:iso:std:iso:14812:3.7.3.13,level 5 ADS}}". + where the ADS is a {{<>,level 5 ADS}}". - content: This term only describes the capabilities of the vehicle, not its operational - state. In other words, the term applies as long as the ADS is {{urn:iso:std:iso:14812:3.2.3.6,connected}} - to the vehicle, whether the {{urn:iso:std:iso:14812:3.7.3.1,dynamic driving + state. In other words, the term applies as long as the ADS is {{<>,connected}} + to the vehicle, whether the {{<>,dynamic driving task,DDT}} is actively engaged or not. examples: [] language_code: eng diff --git a/concepts/concept-3.7.3.16.yaml b/concepts/concept-3.7.3.16.yaml index 6064513..b265f1f 100644 --- a/concepts/concept-3.7.3.16.yaml +++ b/concepts/concept-3.7.3.16.yaml @@ -11,8 +11,8 @@ eng: designation: driving automation dual-mode vehicle domain: driving automation definition: - - content: "{{urn:iso:std:iso:14812:3.7.3.15,ADS-equipped vehicle}} designed for - both driverless operation and operation by a {{urn:iso:std:iso:14812:3.6.2.4,in-vehicle + - content: "{{<>,ADS-equipped vehicle}} designed for + both driverless operation and operation by a {{<>,in-vehicle driver,conventional driver}} for complete _trips_" notes: [] examples: [] diff --git a/concepts/concept-3.7.3.17.yaml b/concepts/concept-3.7.3.17.yaml index 423a944..0ac3cc4 100644 --- a/concepts/concept-3.7.3.17.yaml +++ b/concepts/concept-3.7.3.17.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: ADS-dedicated vehicle definition: - - content: "{{urn:iso:std:iso:14812:3.7.3.15,ADS-equipped vehicle}} designed for + - content: "{{<>,ADS-equipped vehicle}} designed for only driverless operation for complete trips" notes: [] examples: [] diff --git a/concepts/concept-3.7.3.2.yaml b/concepts/concept-3.7.3.2.yaml index 3af3e12..5e9106a 100644 --- a/concepts/concept-3.7.3.2.yaml +++ b/concepts/concept-3.7.3.2.yaml @@ -10,17 +10,17 @@ eng: normative_status: preferred designation: ODD definition: - - content: set of operating conditions under which a given {{urn:iso:std:iso:14812:3.7.3.6,driving + - content: set of operating conditions under which a given {{<>,driving automation system}} or feature thereof is specifically designed to function notes: - content: The conditions can include environmental, geographical, time-of-day, and/or other restrictions. - content: The conditions can require the presence or absence of certain traffic - or {{urn:iso:std:iso:14812:3.3.1.3,roadway}} characteristics. + or {{<>,roadway}} characteristics. examples: - - content: "{{urn:iso:std:iso:14812:3.7.3.10,ADS}} feature designed to operate a - {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} only on fully access-controlled freeways - in low-speed traffic, under fair weather conditions and optimal {{urn:iso:std:iso:14812:3.3.5.1,road}} + - content: "{{<>,ADS}} feature designed to operate a + {{<>,vehicle}} only on fully access-controlled freeways + in low-speed traffic, under fair weather conditions and optimal {{<>,road}} maintenance conditions (e.g. good lane markings and not under construction)." - content: ADS-dedicated vehicle designed to operate only within a geographically-defined area, and only during daylight at speeds not exceeding 25 mph. diff --git a/concepts/concept-3.7.3.3.yaml b/concepts/concept-3.7.3.3.yaml index 179635d..7140aa6 100644 --- a/concepts/concept-3.7.3.3.yaml +++ b/concepts/concept-3.7.3.3.yaml @@ -11,11 +11,11 @@ eng: designation: driving automation fallback domain: driving automation definition: - - content: response by a {{urn:iso:std:iso:14812:3.1.1.6,person}} to perform the - {{urn:iso:std:iso:14812:3.7.3.1,dynamic driving task,DDT}} or by an {{urn:iso:std:iso:14812:3.7.3.10,ADS}} + - content: response by a {{<>,person}} to perform the + {{<>,dynamic driving task,DDT}} or by an {{<>,ADS}} to achieve a minimal risk condition when the response is triggered upon violation - of the defined {{urn:iso:std:iso:14812:3.7.3.2,operational design domain}} constraints - or in response to a DDT performance-relevant {{urn:iso:std:iso:14812:3.7.3.6,driving + of the defined {{<>,operational design domain}} constraints + or in response to a DDT performance-relevant {{<>,driving automation system}} failure notes: - content: This term includes the response of a person to perform the DDT in a manner diff --git a/concepts/concept-3.7.3.4.yaml b/concepts/concept-3.7.3.4.yaml index 4eb507d..634c4d4 100644 --- a/concepts/concept-3.7.3.4.yaml +++ b/concepts/concept-3.7.3.4.yaml @@ -11,10 +11,10 @@ eng: designation: DDT fallback-ready user domain: driving automation definition: - - content: "{{urn:iso:std:iso:14812:3.1.1.6,person}} who is able to operate the - {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} if the Level 3 {{urn:iso:std:iso:14812:3.7.3.11,level + - content: "{{<>,person}} who is able to operate the + {{<>,vehicle}} if the Level 3 {{<>,level 3 ADS,ADS}} issues a request to intervene or if that person otherwise identifies - a condition that requires intervention to perform the {{urn:iso:std:iso:14812:3.7.3.1,dynamic + a condition that requires intervention to perform the {{<>,dynamic driving task,DDT}}" notes: [] examples: [] diff --git a/concepts/concept-3.7.3.5.yaml b/concepts/concept-3.7.3.5.yaml index 4659652..0de9dd9 100644 --- a/concepts/concept-3.7.3.5.yaml +++ b/concepts/concept-3.7.3.5.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: DDT performance-relevant system failure definition: - - content: malfunction in a {{urn:iso:std:iso:14812:3.2.1.5,vehicle system}} that - prevents the {{urn:iso:std:iso:14812:3.7.3.6,driving automation system}} from - reliably performing its portion of the {{urn:iso:std:iso:14812:3.7.3.1,dynamic + - content: malfunction in a {{<>,vehicle system}} that + prevents the {{<>,driving automation system}} from + reliably performing its portion of the {{<>,dynamic driving task,DDT}} on a sustained basis notes: - content: The malfunction can be internal to the driving automation system or part diff --git a/concepts/concept-3.7.3.6.yaml b/concepts/concept-3.7.3.6.yaml index 661d6d8..7a31a56 100644 --- a/concepts/concept-3.7.3.6.yaml +++ b/concepts/concept-3.7.3.6.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: driving automation system definition: - - content: hardware and software {{urn:iso:std:iso:14812:3.1.2.1,system}} that is - able to perform part or all of the {{urn:iso:std:iso:14812:3.7.3.1,dynamic driving + - content: hardware and software {{<>,system}} that is + able to perform part or all of the {{<>,dynamic driving task,DDT}} on a sustained basis notes: - content: In contrast to this generic term for any level 1-5 system, the specific @@ -21,10 +21,10 @@ eng: driving automation. - content: Driving automation levels are defined in <>, which is also known as <>. - - content: Driving automation levels include "{{urn:iso:std:iso:14812:3.7.3.8,level - 1 driving automation}}", "{{urn:iso:std:iso:14812:3.7.3.9,level 2 driving automation}}", - "{{urn:iso:std:iso:14812:3.7.3.11,level 3 ADS}}", "{{urn:iso:std:iso:14812:3.7.3.12,level - 4 ADS}}" and "{{urn:iso:std:iso:14812:3.7.3.13,level 5 ADS}}". + - content: Driving automation levels include "{{<>,level + 1 driving automation}}", "{{<>,level 2 driving automation}}", + "{{<>,level 3 ADS}}", "{{<>,level + 4 ADS}}" and "{{<>,level 5 ADS}}". examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.7.3.7.yaml b/concepts/concept-3.7.3.7.yaml index 9e91399..2c6e1bc 100644 --- a/concepts/concept-3.7.3.7.yaml +++ b/concepts/concept-3.7.3.7.yaml @@ -7,12 +7,12 @@ eng: normative_status: preferred designation: driver support system definition: - - content: "{{urn:iso:std:iso:14812:3.7.3.6,driving automation system}} that is - only able to perform part of the {{urn:iso:std:iso:14812:3.7.3.1,dynamic driving + - content: "{{<>,driving automation system}} that is + only able to perform part of the {{<>,dynamic driving task,DDT}}" notes: - - content: Driver support systems include {{urn:iso:std:iso:14812:3.7.3.8,level - 1 driving automation,level 1}} and {{urn:iso:std:iso:14812:3.7.3.9,level 2 driving + - content: Driver support systems include {{<>,level + 1 driving automation,level 1}} and {{<>,level 2 driving automation}}. examples: [] language_code: eng diff --git a/concepts/concept-3.7.3.8.yaml b/concepts/concept-3.7.3.8.yaml index 52e3772..1c9ca12 100644 --- a/concepts/concept-3.7.3.8.yaml +++ b/concepts/concept-3.7.3.8.yaml @@ -10,16 +10,16 @@ eng: normative_status: preferred designation: driver assistance definition: - - content: "{{urn:iso:std:iso:14812:3.7.3.7,driver support system}} that provides - either sustained lateral or sustained longitudinal {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} - motion control within a specific {{urn:iso:std:iso:14812:3.7.3.2,operational - design domain}} with the expectation that a {{urn:iso:std:iso:14812:3.6.2.4,in-vehicle - driver,conventional driver}} completes the {{urn:iso:std:iso:14812:3.7.3.1,dynamic + - content: "{{<>,driver support system}} that provides + either sustained lateral or sustained longitudinal {{<>,vehicle}} + motion control within a specific {{<>,operational + design domain}} with the expectation that a {{<>,in-vehicle + driver,conventional driver}} completes the {{<>,dynamic driving task,DDT}}" notes: - - content: Other driving automation levels include "{{urn:iso:std:iso:14812:3.7.3.9,level - 2 driving automation}}", "{{urn:iso:std:iso:14812:3.7.3.11,level 3 ADS}}", "{{urn:iso:std:iso:14812:3.7.3.12,level - 4 ADS}}", and "{{urn:iso:std:iso:14812:3.7.3.13,level 5 ADS}}". + - content: Other driving automation levels include "{{<>,level + 2 driving automation}}", "{{<>,level 3 ADS}}", "{{<>,level + 4 ADS}}", and "{{<>,level 5 ADS}}". examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.7.3.9.yaml b/concepts/concept-3.7.3.9.yaml index 94e3179..c68807b 100644 --- a/concepts/concept-3.7.3.9.yaml +++ b/concepts/concept-3.7.3.9.yaml @@ -10,15 +10,15 @@ eng: normative_status: preferred designation: partial driving automation definition: - - content: "{{urn:iso:std:iso:14812:3.7.3.7,driver support system}} that provides - sustained lateral and longitudinal {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} - motion control within a specific {{urn:iso:std:iso:14812:3.7.3.2,operational - design domain}} with the expectation that a {{urn:iso:std:iso:14812:3.6.2.4,in-vehicle + - content: "{{<>,driver support system}} that provides + sustained lateral and longitudinal {{<>,vehicle}} + motion control within a specific {{<>,operational + design domain}} with the expectation that a {{<>,in-vehicle driver,conventional driver}} completes the object and event detection and response" notes: - - content: Other driving automation levels include "{{urn:iso:std:iso:14812:3.7.3.8,level - 1 driving automation}}", "{{urn:iso:std:iso:14812:3.7.3.11,level 3 ADS}}", "{{urn:iso:std:iso:14812:3.7.3.12,level - 4 ADS}}", and "{{urn:iso:std:iso:14812:3.7.3.13,level 5 ADS}}". + - content: Other driving automation levels include "{{<>,level + 1 driving automation}}", "{{<>,level 3 ADS}}", "{{<>,level + 4 ADS}}", and "{{<>,level 5 ADS}}". examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.7.4.1.yaml b/concepts/concept-3.7.4.1.yaml index 7475625..a927ef8 100644 --- a/concepts/concept-3.7.4.1.yaml +++ b/concepts/concept-3.7.4.1.yaml @@ -10,8 +10,8 @@ eng: normative_status: preferred designation: ITS off-grid definition: - - content: characteristic of a {{urn:iso:std:iso:14812:3.1.1.3,material entity}} - that is currently unable to send data to or receive data from {{urn:iso:std:iso:14812:3.2.3.6,connected}} + - content: characteristic of a {{<>,material entity}} + that is currently unable to send data to or receive data from {{<>,connected}} entities notes: [] examples: [] diff --git a/concepts/concept-3.7.4.2.yaml b/concepts/concept-3.7.4.2.yaml index 1198615..b3c1353 100644 --- a/concepts/concept-3.7.4.2.yaml +++ b/concepts/concept-3.7.4.2.yaml @@ -10,9 +10,9 @@ eng: normative_status: preferred designation: ITS unconnected definition: - - content: characteristic of a {{urn:iso:std:iso:14812:3.1.1.3,material entity}} + - content: characteristic of a {{<>,material entity}} that is equipped with communications equipment that is not active or is otherwise - unable to send data to or receive data from {{urn:iso:std:iso:14812:3.2.3.6,connected}} + unable to send data to or receive data from {{<>,connected}} entities notes: [] examples: [] diff --git a/concepts/concept-3.7.4.3.yaml b/concepts/concept-3.7.4.3.yaml index f2aa4be..2bec451 100644 --- a/concepts/concept-3.7.4.3.yaml +++ b/concepts/concept-3.7.4.3.yaml @@ -10,12 +10,12 @@ eng: normative_status: preferred designation: ITS disconnected definition: - - content: characteristic of a {{urn:iso:std:iso:14812:3.1.1.3,material entity}} + - content: characteristic of a {{<>,material entity}} that is or was equipped with communications equipment that is sufficiently physically disconnected such that the material entity is no longer able to send data to - or receive data from {{urn:iso:std:iso:14812:3.2.3.6,connected}} entities + or receive data from {{<>,connected}} entities notes: - - content: The vehicle on-board equipment can still be present in the {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} + - content: The vehicle on-board equipment can still be present in the {{<>,vehicle}} and can even be partially connected, but not in any operational sense. examples: [] language_code: eng diff --git a/concepts/concept-3.7.4.4.yaml b/concepts/concept-3.7.4.4.yaml index 7cb583b..56bc61d 100644 --- a/concepts/concept-3.7.4.4.yaml +++ b/concepts/concept-3.7.4.4.yaml @@ -10,9 +10,9 @@ eng: normative_status: preferred designation: ITS unequipped definition: - - content: characteristic of a {{urn:iso:std:iso:14812:3.1.1.3,material entity}} + - content: characteristic of a {{<>,material entity}} that is not and has never been equipped with communications equipment for sending - data to or receiving data from {{urn:iso:std:iso:14812:3.2.3.6,connected}} entities + data to or receiving data from {{<>,connected}} entities notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.7.5.1.yaml b/concepts/concept-3.7.5.1.yaml index 3b3a32b..ceb7baf 100644 --- a/concepts/concept-3.7.5.1.yaml +++ b/concepts/concept-3.7.5.1.yaml @@ -10,8 +10,8 @@ eng: normative_status: admitted designation: pedestrian-speed vehicle definition: - - content: "{{urn:iso:std:iso:14812:3.7.1.1,vehicle}} with a {{urn:iso:std:iso:14812:3.7.2.2,design - speed}} that does not exceed {{urn:iso:std:iso:14812:3.7.5.7,ultra-low vehicle + - content: "{{<>,vehicle}} with a {{<>,design + speed}} that does not exceed {{<>,ultra-low vehicle speed,ultra-low vehicle speeds}}" notes: - content: The term "pedestrian speed vehicle" is allowed but the preferred term diff --git a/concepts/concept-3.7.5.10.yaml b/concepts/concept-3.7.5.10.yaml index 43e542a..ff45bf3 100644 --- a/concepts/concept-3.7.5.10.yaml +++ b/concepts/concept-3.7.5.10.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: moderate vehicle speed definition: - - content: "{{urn:iso:std:iso:14812:3.7.2.1,speed}} of a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} - that exceeds {{urn:iso:std:iso:14812:3.7.5.9,moderately-low vehicle speed,moderately-low + - content: "{{<>,speed}} of a {{<>,vehicle}} + that exceeds {{<>,moderately-low vehicle speed,moderately-low vehicle speeds}} but does not reach free-flow motorway speeds" notes: - content: Local regulations for the exact speed range vary. diff --git a/concepts/concept-3.7.5.11.yaml b/concepts/concept-3.7.5.11.yaml index c626de3..b61b654 100644 --- a/concepts/concept-3.7.5.11.yaml +++ b/concepts/concept-3.7.5.11.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: moderately-high vehicle speed definition: - - content: "{{urn:iso:std:iso:14812:3.7.2.1,speed}} of a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} + - content: "{{<>,speed}} of a {{<>,vehicle}} that is typical of free-flow motorway speeds to twice that speed" notes: - content: Local regulations for the exact speed range vary. diff --git a/concepts/concept-3.7.5.12.yaml b/concepts/concept-3.7.5.12.yaml index 108b84e..efdaccd 100644 --- a/concepts/concept-3.7.5.12.yaml +++ b/concepts/concept-3.7.5.12.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: high vehicle speed definition: - - content: "{{urn:iso:std:iso:14812:3.7.2.1,speed}} of a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} + - content: "{{<>,speed}} of a {{<>,vehicle}} that exceeds free flow motorway speeds by a factor of two or more" notes: - content: Local regulations for the exact speed range vary. diff --git a/concepts/concept-3.7.5.2.yaml b/concepts/concept-3.7.5.2.yaml index 04d865d..b3d1f93 100644 --- a/concepts/concept-3.7.5.2.yaml +++ b/concepts/concept-3.7.5.2.yaml @@ -10,8 +10,8 @@ eng: normative_status: admitted designation: cycle-speed vehicle definition: - - content: "{{urn:iso:std:iso:14812:3.7.1.1,vehicle}} with a {{urn:iso:std:iso:14812:3.7.2.2,design - speed}} in the range of {{urn:iso:std:iso:14812:3.7.5.8,low vehicle speed,low + - content: "{{<>,vehicle}} with a {{<>,design + speed}} in the range of {{<>,low vehicle speed,low vehicle speeds}}" notes: - content: The term "cycle-speed vehicle" is allowed but the preferred term follows diff --git a/concepts/concept-3.7.5.3.yaml b/concepts/concept-3.7.5.3.yaml index 5f08e13..66580c1 100644 --- a/concepts/concept-3.7.5.3.yaml +++ b/concepts/concept-3.7.5.3.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: moderately low-speed vehicle definition: - - content: "{{urn:iso:std:iso:14812:3.7.1.1,vehicle}} with a {{urn:iso:std:iso:14812:3.7.2.2,design - speed}} in the range of {{urn:iso:std:iso:14812:3.7.5.9,moderately-low vehicle + - content: "{{<>,vehicle}} with a {{<>,design + speed}} in the range of {{<>,moderately-low vehicle speed,moderately-low vehicle speeds}}" notes: [] examples: diff --git a/concepts/concept-3.7.5.4.yaml b/concepts/concept-3.7.5.4.yaml index b338404..04fe55a 100644 --- a/concepts/concept-3.7.5.4.yaml +++ b/concepts/concept-3.7.5.4.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: moderate-speed vehicle definition: - - content: "{{urn:iso:std:iso:14812:3.7.1.1,vehicle}} with a {{urn:iso:std:iso:14812:3.7.2.2,design - speed}} in the range of {{urn:iso:std:iso:14812:3.7.5.10,moderate vehicle speed,moderate + - content: "{{<>,vehicle}} with a {{<>,design + speed}} in the range of {{<>,moderate vehicle speed,moderate vehicle speeds}}" notes: [] examples: diff --git a/concepts/concept-3.7.5.5.yaml b/concepts/concept-3.7.5.5.yaml index 39ac389..05cdc38 100644 --- a/concepts/concept-3.7.5.5.yaml +++ b/concepts/concept-3.7.5.5.yaml @@ -7,12 +7,12 @@ eng: normative_status: preferred designation: moderately high-speed vehicle definition: - - content: "{{urn:iso:std:iso:14812:3.7.1.1,vehicle}} with a {{urn:iso:std:iso:14812:3.7.2.2,design - speed}} in the range of {{urn:iso:std:iso:14812:3.7.5.11,moderately-high vehicle + - content: "{{<>,vehicle}} with a {{<>,design + speed}} in the range of {{<>,moderately-high vehicle speed,moderately-high vehicle speeds}}" notes: [] examples: - - content: Typical {{urn:iso:std:iso:14812:3.6.2.1,passenger}} car. + - content: Typical {{<>,passenger}} car. language_code: eng entry_status: valid sources: diff --git a/concepts/concept-3.7.5.6.yaml b/concepts/concept-3.7.5.6.yaml index a2a8750..3ca0b44 100644 --- a/concepts/concept-3.7.5.6.yaml +++ b/concepts/concept-3.7.5.6.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: high-speed vehicle definition: - - content: "{{urn:iso:std:iso:14812:3.7.1.1,vehicle}} with a {{urn:iso:std:iso:14812:3.7.2.2,design - speed}} in the range of {{urn:iso:std:iso:14812:3.7.5.12,high vehicle speed,high + - content: "{{<>,vehicle}} with a {{<>,design + speed}} in the range of {{<>,high vehicle speed,high vehicle speeds}}" notes: [] examples: diff --git a/concepts/concept-3.7.5.7.yaml b/concepts/concept-3.7.5.7.yaml index bdaf220..f99bb07 100644 --- a/concepts/concept-3.7.5.7.yaml +++ b/concepts/concept-3.7.5.7.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: ultra-low vehicle speed definition: - - content: "{{urn:iso:std:iso:14812:3.7.2.1,speed}} of a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} - that does not greatly exceed typical {{urn:iso:std:iso:14812:3.6.1.3,pedestrian}} + - content: "{{<>,speed}} of a {{<>,vehicle}} + that does not greatly exceed typical {{<>,pedestrian}} speeds" notes: - content: Local regulations for the exact speed range vary. diff --git a/concepts/concept-3.7.5.8.yaml b/concepts/concept-3.7.5.8.yaml index 0d8d045..e3efe1b 100644 --- a/concepts/concept-3.7.5.8.yaml +++ b/concepts/concept-3.7.5.8.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: low vehicle speed definition: - - content: "{{urn:iso:std:iso:14812:3.7.2.1,speed}} of a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} - that exceeds {{urn:iso:std:iso:14812:3.6.1.3,pedestrian}} speeds and is more + - content: "{{<>,speed}} of a {{<>,vehicle}} + that exceeds {{<>,pedestrian}} speeds and is more typical of pedal cycles" notes: - content: Local regulations for the exact speed range vary. diff --git a/concepts/concept-3.7.5.9.yaml b/concepts/concept-3.7.5.9.yaml index b60d0cb..b9dd684 100644 --- a/concepts/concept-3.7.5.9.yaml +++ b/concepts/concept-3.7.5.9.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: moderately-low vehicle speed definition: - - content: "{{urn:iso:std:iso:14812:3.7.2.1,speed}} of a {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} + - content: "{{<>,speed}} of a {{<>,vehicle}} that exceeds speeds typical of pedal cycles but can be reached on performance pedal cycles in short bursts or by performance riders" notes: diff --git a/concepts/concept-3.7.6.1.yaml b/concepts/concept-3.7.6.1.yaml index 7dcc1be..d1f527b 100644 --- a/concepts/concept-3.7.6.1.yaml +++ b/concepts/concept-3.7.6.1.yaml @@ -7,14 +7,14 @@ eng: normative_status: preferred designation: road vehicle definition: - - content: "{{urn:iso:std:iso:14812:3.7.1.1,vehicle}} meeting the requirements to - operate within the {{urn:iso:std:iso:14812:3.3.1.4,driving space}} of a {{urn:iso:std:iso:14812:3.3.5.1,road}}" + - content: "{{<>,vehicle}} meeting the requirements to + operate within the {{<>,driving space}} of a {{<>,road}}" notes: - content: Unless indicated otherwise, the term typically refers to vehicles that - are allowed to operate in the same driving spaces as motorized {{urn:iso:std:iso:14812:3.6.2.1,passenger}} - cars, according to the legal requirements of the local jurisdictional {{urn:iso:std:iso:14812:3.1.1.1,entity}}. - However, the term can be contextualized for other {{urn:iso:std:iso:14812:3.1.3.11,environment,environments}}. - For example, a bicycle is a "road vehicle" when the "road" is a {{urn:iso:std:iso:14812:3.3.3.2,cycleway}}. + are allowed to operate in the same driving spaces as motorized {{<>,passenger}} + cars, according to the legal requirements of the local jurisdictional {{<>,entity}}. + However, the term can be contextualized for other {{<>,environment,environments}}. + For example, a bicycle is a "road vehicle" when the "road" is a {{<>,cycleway}}. examples: [] language_code: eng entry_status: valid diff --git a/concepts/concept-3.7.6.2.yaml b/concepts/concept-3.7.6.2.yaml index 6aa0918..d53eeef 100644 --- a/concepts/concept-3.7.6.2.yaml +++ b/concepts/concept-3.7.6.2.yaml @@ -7,7 +7,7 @@ eng: normative_status: preferred designation: motorized vehicle definition: - - content: self-propelled {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} + - content: self-propelled {{<>,vehicle}} notes: [] examples: [] language_code: eng diff --git a/concepts/concept-3.7.6.3.yaml b/concepts/concept-3.7.6.3.yaml index 45d4ddc..ef93623 100644 --- a/concepts/concept-3.7.6.3.yaml +++ b/concepts/concept-3.7.6.3.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: motor vehicle definition: - - content: "{{urn:iso:std:iso:14812:3.7.6.2,motorized vehicle,motorized}} {{urn:iso:std:iso:14812:3.7.6.1,road - vehicle}} allowed to operate in the same {{urn:iso:std:iso:14812:3.3.1.4,driving - space,driving spaces}} as motorized {{urn:iso:std:iso:14812:3.6.2.1,passenger}} + - content: "{{<>,motorized vehicle,motorized}} {{<>,road + vehicle}} allowed to operate in the same {{<>,driving + space,driving spaces}} as motorized {{<>,passenger}} cars" notes: [] examples: [] diff --git a/concepts/concept-3.7.6.4.yaml b/concepts/concept-3.7.6.4.yaml index f75ceee..3bcf315 100644 --- a/concepts/concept-3.7.6.4.yaml +++ b/concepts/concept-3.7.6.4.yaml @@ -7,9 +7,9 @@ eng: normative_status: preferred designation: non-road vehicle definition: - - content: "{{urn:iso:std:iso:14812:3.7.1.1,vehicle}} not meeting the legal requirements - to be driven in {{urn:iso:std:iso:14812:3.3.1.13,traffic lane,traffic lanes}} - or {{urn:iso:std:iso:14812:3.3.3.1,cycle lane,cycle lanes}} of a {{urn:iso:std:iso:14812:3.3.5.2,road + - content: "{{<>,vehicle}} not meeting the legal requirements + to be driven in {{<>,traffic lane,traffic lanes}} + or {{<>,cycle lane,cycle lanes}} of a {{<>,road network}}" notes: [] examples: [] diff --git a/concepts/concept-3.7.6.5.yaml b/concepts/concept-3.7.6.5.yaml index 7e26029..74b379f 100644 --- a/concepts/concept-3.7.6.5.yaml +++ b/concepts/concept-3.7.6.5.yaml @@ -7,10 +7,10 @@ eng: normative_status: preferred designation: road cycle definition: - - content: "{{urn:iso:std:iso:14812:3.7.1.1,vehicle}} meeting the legal requirements - to operate in {{urn:iso:std:iso:14812:3.3.3.1,cycle lane,cycle lanes}} and {{urn:iso:std:iso:14812:3.3.3.2,cycleway,cycleways}}" + - content: "{{<>,vehicle}} meeting the legal requirements + to operate in {{<>,cycle lane,cycle lanes}} and {{<>,cycleway,cycleways}}" notes: - - content: In some countries, other special {{urn:iso:std:iso:14812:3.3.1.13,lane,lanes}} + - content: In some countries, other special {{<>,lane,lanes}} could also be open to road cycles, such as bus lanes. examples: [] language_code: eng diff --git a/concepts/concept-3.7.6.6.yaml b/concepts/concept-3.7.6.6.yaml index 153c91b..fd6cf4b 100644 --- a/concepts/concept-3.7.6.6.yaml +++ b/concepts/concept-3.7.6.6.yaml @@ -7,8 +7,8 @@ eng: normative_status: preferred designation: non-road cycle definition: - - content: human-powered {{urn:iso:std:iso:14812:3.7.1.1,vehicle}} not meeting the - legal requirements to be driven in {{urn:iso:std:iso:14812:3.3.3.1,cycle lane,cycle + - content: human-powered {{<>,vehicle}} not meeting the + legal requirements to be driven in {{<>,cycle lane,cycle lanes}} notes: [] examples: []