Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixing reference according to metanorma syntax #24

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
2 changes: 1 addition & 1 deletion concepts/concept-3.1.1.1.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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: "{{<<urn:iso:std:iso:14812:3.1.1.6>>,person,Person}}, object, event, idea,
process, etc."
language_code: eng
entry_status: valid
Expand Down
2 changes: 1 addition & 1 deletion concepts/concept-3.1.1.2.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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: "{{<<urn:iso:std:iso:14812:3.1.1.1>>,entity}} that does not occupy three-dimensional
space"
notes: []
examples:
Expand Down
2 changes: 1 addition & 1 deletion concepts/concept-3.1.1.3.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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: "{{<<urn:iso:std:iso:14812:3.1.1.1>>,entity}} that occupies three-dimensional
space"
notes:
- content: All material entities have certain characteristics that can be described
Expand Down
2 changes: 1 addition & 1 deletion concepts/concept-3.1.1.4.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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: "{{<<urn:iso:std:iso:14812:3.1.1.3>>,material entity}} that is not and has
never been a living organism"
notes: []
examples: []
Expand Down
2 changes: 1 addition & 1 deletion concepts/concept-3.1.1.5.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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: "{{<<urn:iso:std:iso:14812:3.1.1.3>>,material entity}} that was or is a living
organism"
notes: []
examples: []
Expand Down
2 changes: 1 addition & 1 deletion concepts/concept-3.1.1.6.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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: "{{<<urn:iso:std:iso:14812:3.1.1.5>>,biological entity}} that is a human
being"
notes: []
examples: []
Expand Down
8 changes: 4 additions & 4 deletions concepts/concept-3.1.10.1.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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: "{{<<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
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 {{<<urn:iso:std:iso:14812:3.1.10.3>>,data dictionary}},
in a data specification that references the data concept or associated with
the data themselves.
examples: []
Expand Down
4 changes: 2 additions & 2 deletions concepts/concept-3.1.10.2.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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}}
notes: []
examples: []
language_code: eng
Expand Down
4 changes: 2 additions & 2 deletions concepts/concept-3.1.10.3.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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
notes: []
examples: []
language_code: eng
Expand Down
6 changes: 3 additions & 3 deletions concepts/concept-3.1.10.4.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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
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 {{<<urn:iso:std:iso:14812:3.1.10.2>>,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
Expand Down
2 changes: 1 addition & 1 deletion concepts/concept-3.1.11.1.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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. {{<<urn:iso:std:iso:14812:3.4.1.1>>,location}}] to be divisible
in another context (e.g. latitude, longitude, and elevation).
examples: []
language_code: eng
Expand Down
4 changes: 2 additions & 2 deletions concepts/concept-3.1.11.4.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<urn:iso:std:iso:14812:3.1.11.1>>,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 {{<<urn:iso:std:iso:14812:3.1.11.2>>,class,classes}}
notes:
- content: The grouping can be a set, sequence or a choice.
- content: A data frame can contain other data frames.
Expand Down
4 changes: 2 additions & 2 deletions concepts/concept-3.1.11.5.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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
and data frames that is used to convey information
notes: []
examples: []
Expand Down
4 changes: 2 additions & 2 deletions concepts/concept-3.1.12.1.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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}}
notes: []
examples: []
language_code: eng
Expand Down
2 changes: 1 addition & 1 deletion concepts/concept-3.1.12.2.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<urn:iso:std:iso:14812:3.5.3.4>>,user,user's}}
perspective to perform a task in a specified context
notes: []
examples: []
Expand Down
2 changes: 1 addition & 1 deletion concepts/concept-3.1.13.2.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<urn:iso:std:iso:14812:3.1.13.1>>,instant,instants}}
notes: []
examples: []
language_code: eng
Expand Down
2 changes: 1 addition & 1 deletion concepts/concept-3.1.2.1.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<urn:iso:std:iso:14812:3.1.3.10>>,element,elements}}
organized to achieve one or more stated purposes
notes: []
examples: []
Expand Down
6 changes: 3 additions & 3 deletions concepts/concept-3.1.2.2.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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: "{{<<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}}
from an origin to a destination"
notes:
- content: Transport systems can also include any supporting system, such as information
Expand Down
6 changes: 3 additions & 3 deletions concepts/concept-3.1.2.3.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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: "{{<<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
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 {{<<urn:iso:std:iso:14812:3.1.3.10>>,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.
Expand Down
4 changes: 2 additions & 2 deletions concepts/concept-3.1.2.4.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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: "{{<<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
transport system}}"
notes:
- content: '"Intelligent transportation system" is the American English equivalent.'
Expand Down
6 changes: 3 additions & 3 deletions concepts/concept-3.1.2.5.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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
service,ITS services}}
notes: []
examples: []
Expand Down
6 changes: 3 additions & 3 deletions concepts/concept-3.1.3.1.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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
of its design and evolution
notes: []
examples: []
Expand Down
4 changes: 2 additions & 2 deletions concepts/concept-3.1.3.10.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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}}
notes: []
examples: []
language_code: eng
Expand Down
2 changes: 1 addition & 1 deletion concepts/concept-3.1.3.11.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<urn:iso:std:iso:14812:3.1.2.1>>,system}}
notes:
- content: The environment of a system includes developmental, technological, business,
operational, organizational, political, economic, legal, regulatory, ecological
Expand Down
2 changes: 1 addition & 1 deletion concepts/concept-3.1.3.2.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<urn:iso:std:iso:14812:3.1.3.1>>,architecture}}
notes: []
examples: []
language_code: eng
Expand Down
4 changes: 2 additions & 2 deletions concepts/concept-3.1.3.3.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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}}
notes: []
examples:
- content: Generalised Enterprise Reference Architecture and Methodologies (GERAM)
Expand Down
4 changes: 2 additions & 2 deletions concepts/concept-3.1.3.4.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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}}
notes: []
examples: []
language_code: eng
Expand Down
6 changes: 3 additions & 3 deletions concepts/concept-3.1.3.5.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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}}
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 {{<<urn:iso:std:iso:14812:3.1.3.11>>,environment}},
including developmental, technological, business, operational, organizational,
political, economic, legal, regulatory, ecological and social influences.
examples: []
Expand Down
4 changes: 2 additions & 2 deletions concepts/concept-3.1.3.6.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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}}
notes: []
examples: []
language_code: eng
Expand Down
6 changes: 3 additions & 3 deletions concepts/concept-3.1.3.7.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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}}
notes: []
examples: []
language_code: eng
Expand Down
4 changes: 2 additions & 2 deletions concepts/concept-3.1.3.8.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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,
balance sheets, organization charts and state transition models.
examples: []
language_code: eng
Expand Down
4 changes: 2 additions & 2 deletions concepts/concept-3.1.3.9.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<<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
kind}}
notes: []
examples: []
Expand Down
4 changes: 2 additions & 2 deletions concepts/concept-3.1.4.1.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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: "{{<<urn:iso:std:iso:14812:3.1.3.7>>,architecture view}} from the {{<<urn:iso:std:iso:14812:3.1.4.2>>,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 {{<<urn:iso:std:iso:14812:3.1.9.4>>,ITS-S reference architecture}}.
examples: []
language_code: eng
entry_status: valid
Expand Down
4 changes: 2 additions & 2 deletions concepts/concept-3.1.4.2.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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: "{{<<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
the Open Systems Interconnection (OSI) stack and related management and security
issues"
notes: []
Expand Down
Loading
Loading