BS ISO 8000-2:2020 pdf download.Data quality Part 2: Vocabulary.
3.5.5
application reference model
ARM
information (32,1) model that describes the information requirements (3.1.2) and constraints of an application (3.5.3) within an application protocol (3.5.4) or module
[SOURCE: ISO 10303-1:—, 3.1.18]
3.6 Terms relating to data dictionary
3.6.1
data dictionary entry
description of an entity (3.3.3) type containing, at a minimum, an unambiguous identifier (3.3.1), a term and a definition
Note 1 to entry: In the Iso 8000 data (3.2.2) architecture, a property need not be associated with a specific data type in a data dictionary (3.6.2). The association between a property and a data type can be made in a data specification (3.6.3).
Note 2 to entry: In order to exchange a value corresponding to a data dictionary entry, more information (3.2.1) than an identifier, a name and a definition could be needed. For a property, a data type is needed. Depending on the kind of property, other data elements (e.g. unit of measure, language) could also be needed. These elements can be given in the data dictionary, in a data specification that references the data dictionary entry, or directly associated with the data.
Note 3 to entry: In the ISO 13584 data architecture, the dictionary entry for a property is required to reference a specific data type. Thus, an ISO 13584 dictionary entry is a special case of the more general concept, as it includes elements of a data specification.
[SOURCE: ISO 22745-2:2010, B.2.17, modified — The spelling of “datatype” has been changed to “data type” to be consistent with other terms in this document and Note 2 to entry has been modified.]
3.6.2
data dictionary
collection of data dictionary entries (3.6.1) that allows lookup by entity (3.3.3) identifier (3.3.1)
[SOURCE: ISO 22745-2:2010, B.2.16]
3.6.3
data specification
set of requirements (3.1.2) covering the characteristics of data (3.2.2) being fit for one or more particular purposes
Note 1 to entry: 150 8000-110 requires a data specification to describe how items belong to a particular class by using entries from a data dictionary (3.6.2).
Note 2 to entry: In collaborative relationships, the supplier of data and the user of that data agree the content of the data specification in order to ensure the collaboration will be successful (i.e. the supplier can supply conforming data and the user is able to exploit the data for the intended purposes).
Note 3 to entry: An effective data specification is one where the creator of the specification intends for the requirements to be necessary and sufficient for the data to meet the particular purposes.
Note 4 to entry: All stakeholders will be able to understand the data specification more effectively if there is an explicit statement of the intended purposes for the data.
3.7 Terms relating to characteristic data
3.7.1
property value
instance of a specific value together with an identifier (3.3.1) for a data dictionary entry (3.6.1) that defines a property.BS ISO 8000-2 pdf download.