ISO 18876 Integration of industrial data for exchange, access, and sharing
Glossary of terms
This glossary combines the terms and definitions from Parts 1 and 2 (fifth working drafts).
- application model (AM)
- model that represents information used for some particular purpose
NOTE Some application models are also integration models.
- class
- collection to which some significance is attached
- concept
- general notion or abstract idea
- construct
- structure of data together with its intended meaning
- data
- representation of information in a formal manner suitable for communication, interpretation, or processing by human beings or computers
[ISO 10303-1]
- data model
- definition, structure, and data types for data
- derived concept
- concept in an integration model that is wholly defined in terms of primitive concepts
- foundation concept
- primitive concept that determines the underlying world viewpoint of an integration model
EXAMPLE The concepts of "class" and "individual" are foundation concepts for a general integration model.
- general concept
- primitive concept that has very wide applicability, but is a specialization of some foundation concept
NOTE The boundary between a foundation concept and a general concept may be arbitrary; some concepts may be
thought of as both foundation concepts and general concepts.
- individual
- thing that exists in space and time
NOTE This includes things that actually exist, or have existed, and things that possibly exist in the past, present or future.
EXAMPLE The pump with serial number ABC123, Battersea Power Station, Sir Joseph Whitworth, and the Starship "Enterprise" are examples of individuals.
- information
- facts, concepts, or instructions
[ISO 10303-1]
- integration
- activity that creates, modifies, or extends an integration model
- integration model (IM)
- application model that can represent the information that is represented by two or more application models
- mapping
- association of a set of elements of a model with a set of elements of another model
NOTE 1 A mapping can be uni-directional or bi-directional.
NOTE 2 A mapping is the result of apply a mapping specification to particular models.
- mapping specification
- definition of the transformations that relate elements of one model with elements of another model
NOTE 1 A mapping specification can include data structure transformations, data value transformations, data encoding transformations, and terminology transformations.
NOTE 2 Mapping specifications can be procedural, or declarative, or a combination of these.
- model
- limited representation of something suitable for some purpose
NOTE A model can be data, or a data model, or a combination of these. See Annex D of ISO 18876-2 for further discussion of the relationship between models, data, and data models.
- model context
- range of activities and viewpoints for which an application model is valid
NOTE This term is more general than application context as defined in ISO 10303-1.
- model scope
- range of information that an application model can describe
- primitive concept
- concept in an integration model that is not wholly defined in terms of other concepts
- specific concept
- primitive concept that is a specialization of some general concept and has a limited range of applicability
EXAMPLE Car, process plant, quark, purchase order, and XML document are examples of specific concepts.
NOTE The boundary between a specific concept and a general concept may be arbitrary; some concepts may be
thought of as both specific concepts and general concepts.