ISO/TS 18876-1:2003 産業オートメーションシステムと統合—交換、アクセス、共有のための産業データの統合—パート1：アーキテクチャの概要と説明 | ページ 6

3.1.1

application model (AM)

model that represents information used for some particular purpose

Note 1 to entry: Some application models are also integration models (see 3.1.12).

3.1.2

class

category or division of things

Note 1 to entry: There are a number of ways that class can be defined. This definition is intended to be as broad as possible, and is broader than that used in ISO 15926-2.

3.1.3

concept

general notion or idea of something

3.1.4

data

representation of information in a formal manner suitable for communication, interpretation, or processing by human beings or computers

[SOURCE:ISO 10303-1]

3.1.5

data model

set of constructs that provides the definition, structure, and format of data, whether physical or abstract in the sense of being bound to some recording medium

3.1.6

derived concept

concept in an integration model that is wholly defined in terms of primitive concepts

3.1.7

encoding transformation

transformation of the way data elements are represented for computer processing

3.1.8

foundation concept

primitive concept that determines the underlying world viewpoint of an integration model

Note 1 to entry: There can be a number of integration models. Each will have its own modelling paradigm which is characterised by the foundation concepts that it contains.

3.1.9

general concept

primitive concept that has very wide applicability, but is a specialization of some foundation concept

Note 1 to entry: A concept may be considered to be a foundation concept by one community, while it is considered to be a general concept by another.

3.1.10

individual

thing that exists in space and time

Note 1 to entry: This includes things that actually exist, or have existed, and things that possibly exist (past, present, and future) in space and time.

3.1.11

information

facts, concepts, or instructions

[SOURCE:ISO 10303-1]

3.1.12

integration

activity that creates, modifies, or extends an integration model

3.1.13

integration model (IM)

application model that can represent the information that is represented by two or more application models

Note 1 to entry: Being an integration model is about the role one model plays with respect to one or more application models.

3.1.14

mapping

correspondence between instances of one model and instances of another model that represent the same meaning

Note 1 to entry: A mapping can be uni-directional or bi-directional.

3.1.15

mapping specification

definition of the transformations necessary to take information according to one data model and represent the same information according to another data model

Note 1 to entry: A mapping specification can include data structure transformations, data value transformations, data encoding transformations, and terminology transformations.

Note 2 to entry: Mapping specifications can be procedural, or declarative, or a combination of these.

3.1.16

model

limited information representation of something suitable for some purpose

3.1.17

model context

sum of implicit concepts and constraints that limit the possible extension of a model without changing any existing declarations

Note 1 to entry: The model context is therefore the class of all possible extensions to a model.

Note 2 to entry: This term is more general than application context as defined in ISO 10303-1.

3.1.18

model scope

range of information that an application model can describe

3.1.19

primitive concept

concept in an integration model that is not wholly defined in terms of other concepts

3.1.20

specific concept

primitive concept that is a specialization of some general concept and has a limited range of applicability

Note 1 to entry: The boundary between a general concept and a specific concept may be arbitrary; some concepts may be thought of as both general concepts and specific concepts.

3.1.21

structural transformation

type of mapping specification that is a transformation to the structure of data

Note 1 to entry: The change in structure could be due to the rearranging of attributes, the splitting of attributes across entity types, or the creation of new attributes.

3.1.22

terminology transformation

transformation of the term used to refer to a thing

Note 1 to entry: This could be between synonyms in one language, or between different languages.

3.1.23

transformation

change of form

3.1.24

view

constrained representation of a data model