This annex contains terms that are referenced by definitions in Clauses 2 to 23 but differ from the definitions adopted for ISO 22745. The definitions in this annex are included to enable understanding of the definitions that reference them. The definitions in Clauses 2 to 23 are considered normative for ISO 22745.
characteristic of an object or entity
[ISO/IEC 11179-1:2004, definition 3.1.1]
characteristic common to all members of an object class
[ISO/IEC 11179-1:2004, definition 3.3.29]
unit of knowledge created by a unique combination of characteristics
NOTE Concepts are not necessarily bound to particular languages. They are, however, influenced by the social or cultural background which often leads to different categorizations.
[ISO 1087-1:2000, definition 3.2.1]
EXAMPLE resistor, noninductive wire-wound fixed resistor, contact inductive load current rating at maximum DC voltage rating, volt per milliinch, metre, ral 3030 high reflective red, and string (the data type) are all concepts.
unit of thought
EXAMPLE "Automobile", "color", "red", and "metres" are all concepts.
[ISO 29002-5:2009, definition 3.1]
set of concepts structured according to the relations among them
[ISO 1087-1:2000, definition 3.2.11]
field of special knowledge
NOTE 1 The borderlines of a subject field are defined from a purpose-related point of view.
[ISO 1087-1:2000, definition 3.1.2]
EXAMPLE "Chemistry", "medicine", and "process plant operation and maintenance" are examples of subject fields.
NOTE 2 See ISO 704 for a discussion of subject fields and their relation to terminology.
abstraction of a property of an object or of a set of objects
NOTE Characteristics are used for describing concepts.
[ISO 1087-1:2000, definition 3.2.4]
EXAMPLE "Made of wood" is an example of a characteristic.
representation of information in a formalized manner suitable for communication, interpretation, storing or processing
[ISO 1087-2:2000, definition 2.2]
any concrete or abstract thing that exists, did exist, or might exist, including associations among these things
NOTE An entity exists whether data about it are available or not.
EXAMPLE A person, object, event, idea, process, etc.
[ISO/IEC 2382-17:1999, definition 17.02.05]
‹ information processing › knowledge concerning such things as facts, concepts, objects, events, ideas
NOTE 1 Adapted from ISO/IEC 2382-1:1993.
NOTE 2 Information is defined differently in other application areas.
[ISO 1087-2:2000, definition 2.1]
meaningful data
[ISO 9000:2005, definition 3.7.1]
NOTE 1 To be considered information, data needs to be understood by the intended recipients. This means that it needs to be in a form suitable for human understanding and interpretation and in a language that the intended recipients can understand.
NOTE 2 Sometimes individual discrete data elements do not constitute meaningful data in their own right, but become meaningful data only when grouped with other data elements. For example, under typical business practice, an invoice date only constitutes meaningful information if it is accompanied by at least three other pieces of data: invoicer, invoicee, and invoice amount. Of course, other data elements, such as invoice number, are also sometimes required within certain contexts.
body that is based on the membership of other bodies or individuals and has an established constitution and its own administration
[ISO/IEC Guide 2:2004, definition 4.2]
instance of a specific value together with an identifier for a data dictionary entry that defines a property
[ISO 8000-102:2009, definition 7.1]
description of an entity by the class to which it belongs and a set of property values
NOTE ISO 13584, ISO 15926, ISO 22745, ISO 13399, and ISO/TS 29002 all include characteristic data in their data models.
EXAMPLE The item "Hex Cap Screw - A193 Grade B7,.250-20 X 1.250" appears in a manufacturer's catalogue. It can be described as:
Class: hexagon cap screw
Property values:
[material specification, A193 Grade B7]
[diameter, 0.250 in]
[thread pitch, 20/in]
[length, 1.250 in]
In actual characteristic data, the first element of each bracketed pair would be an identifier for a data dictionary entry. The elements are shown decoded here for clarity.
[ISO 8000-102:2009, definition 7.2]
specification of the valid sentences of a formal language using a formal grammar
NOTE 1 A formal language is computer-interpretable.
NOTE 2 Formal grammars are usually Chomsky context-free grammars.
NOTE 3 Variants of Backus-Naur Form (BNF) such as Augmented Backus-Naur Form (ABNF) and Wirth Syntax Notation (WSN) are often used to specify the syntax of computer programming languages and data languages.
EXAMPLE 1 An XML document type definition (DTD) is a formal syntax.
EXAMPLE 2 ISO 10303-21, contains a formal syntax in WSN for ISO 10303 physical files.
[ISO 8000-102:2009, definition 6.1]
collection of data dictionary entries that allows lookup by entity identifier
[ISO 8000-102:2009, definition 8.1]
description of an entity type containing, at a minimum, an unambiguous identifier, a term, and a definition
NOTE 1 In the ISO 8000 data architecture, a property need not be associated with a specific datatype in a data dictionary. The association between a property and a datatype can be made in a data specification.
NOTE 2 In order to exchange a value corresponding to a data dictionary entry, more information than an identifier, a name and a definition might 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, might be needed as well. These things can be given in the data dictionary, in a data specification that references the data dictionary entry, or associated with the data themselves.
NOTE 3 In the ISO 13584 data architecture, the dictionary entry for a property is required to reference a specific datatype. Thus, an ISO 13584 dictionary entry is a special case of the more general concept defined in this clause, as it includes elements of a data specification.
[ISO 8000-102:2009, definition 8.2]
rules for describing items belonging to a particular class using entries from a data dictionary
EXAMPLE 1 An ISO/TS 22745-30 compliant identification guide is a data specification.
EXAMPLE 2 ISO 13584-501 defines a data specification.
[ISO 8000-102:2009, definition 3.3]
message used to exchange master data between organizations
NOTE There are many forms that a message can take. Some examples are:
Web Services call (master data consisting of XML data in a SOAP envelope);
e-mail message (master data consisting of an XML file attached to the e-mail);
Java remote method invocation call (master data consisting of Java objects serialized according to the Java RMI specification);
ODBC call (master data consisting of an update statement encoded according to the ODBC specification);
file of master data contained on a compact diskette delivered to an organization by a person (master data consisting of a spreadsheet).
[ISO 8000-102:2009, definition 11.2]