ISO 19118:2011 地理情報—エンコーディング | ページ 6

4.1

application schema

conceptual schema (4.5) for data (4.8) required by one or more applications

[SOURCE:ISO 19101:2002, 4.2]

Note 1 to entry: An application schema describes the content, the structure and the constraints applicable to information (4.22) in a specific application domain.

4.2

character

member of a set of elements that is used for the representation, organization, or control of data (4.8)

[SOURCE:ISO/IEC 2382-1:1993, 01.02.11]

4.3

code

representation of a label according to a specified scheme

4.4

conceptual model

model (4.27) that defines concepts of a universe of discourse (4.33)

[SOURCE:ISO 19101:2002, 4.4]

4.5

conceptual schema

formal description of a conceptual model (4.4)

[SOURCE:ISO 19101:2002, 4.5]

4.6

conceptual schema language

formal language based on a conceptual formalism for the purpose of representing conceptual schemas (4.5)

[SOURCE:ISO 19101:2002, 4.6]

Note 1 to entry: A conceptual schema language may be lexical or graphical.

4.7

conversion rule

rule for converting instances in the input data (4.8) structure to instances in the output data structure

4.8

data

reinterpretable representation of information (4.22) in a formalized manner suitable for communication, interpretation, or processing

[SOURCE:ISO/IEC 2382-1:1993, 01.01.02]

4.9

data interchange

delivery, receipt and interpretation of data (4.8)

4.10

data transfer

movement of data (4.8) from one point to another over a medium (4.26)

Note 1 to entry: Transfer of information (4.22) implies transfer of data.

4.11

data type

specification of a value domain (4.34) with operations allowed on values in this domain

[SOURCE:ISO/TS 19103:2005, 4.1.5]

Note 1 to entry: A data type is identified by a term, e.g. Integer. Values of the data types are of the specified value domain, e.g. all integer numbers between -65537 and 65536. The set of operations can be +, -, * and/ and is semantically well defined. A data type can be simple or complex. A simple data type defines a value domain where values are considered atomic in a certain context, e.g. Integer. A complex data type is a collection of data types that are grouped together. A complex data type may represent an object and can, thus, have identity.

4.12

dataset

identifiable collection of data (4.8)

[SOURCE:ISO 19115:2003, 4.2]

4.13

encoding

conversion of data (4.8) into a series of codes (4.3)

4.14

encoding rule

identifiable collection of conversion rules (4.7) that define the encoding (4.13) for a particular data (4.8) structure

Note 1 to entry: An encoding rule specifies the types of data being converted as well as the syntax, structure and codes (4.3) used in the resulting data structure.

4.15

encoding service

software component that has an encoding rule (4.14) implemented

4.16

feature

abstraction of real world phenomena

[SOURCE:ISO 19101:2002, 4.11]

Note 1 to entry: A feature may occur as a type or an instance. Feature type or feature instance is used when only one is meant.

4.17

file

named set of records stored or processed as a unit

[SOURCE:ISO/IEC 2382-1:1993, 01.08.06]

4.18

geographic data

data (4.8) with implicit or explicit reference to a location relative to the Earth

[SOURCE:ISO 19109:2005, 4.12]

4.19

geographic information

information (4.22) concerning phenomena implicitly or explicitly associated with a location relative to the Earth

[SOURCE:ISO 19101:2002, 4.16]

4.20

identifier

linguistically independent sequence of characters (4.2) capable of uniquely and permanently identifying that with which it is associated

[SOURCE:ISO 19135:2005, 4.1.5]

4.21

identification convention

set of rules for creating identifiers (4.20)

4.22

information

knowledge concerning objects, such as facts, events, things, processes, or ideas, including concepts, that within a certain context has a particular meaning

[SOURCE:ISO/IEC 2382-1:1993, 01.01.01]

4.23

instance model

representation model (4.27) for storing data (4.8) according to an application schema (4.1)

4.24

interface

named set of operations that characterize the behaviour of an element

[SOURCE:ISO/IEC 19501]

4.25

interoperability

capability to communicate, execute programs, or transfer data (4.8) among various functional units in a manner that requires the user to have little or no knowledge of the unique characteristics of those units

[SOURCE:ISO/IEC 2382-1:1993, 01.01.47]

4.26

medium

substance or agency for storing or transmitting data (4.8)

4.27

model

abstraction of some aspects of reality

[SOURCE:ISO 19109:2005, 4.14]

4.28

schema

formal description of a model (4.27)

[SOURCE:ISO 19101:2002, 4.25]

4.29

schema model

representation model (4.27) for storing schemas (4.28)

4.30

stereotype

new type of modelling element that extends the semantics of the metamodel

[SOURCE:ISO/IEC 19501]

Note 1 to entry: It is necessary that stereotypes be based on certain existing types or classes in the metamodel. Stereotypes may extend the semantics, but not the structure, of pre-existing types and classes. Certain stereotypes are predefined in the UML, others may be user-defined. Stereotypes are one of three extensibility mechanisms in UML; the others are constraint and tagged value.

4.31

transfer protocol

common set of rules for defining interactions between distributed systems

4.32

transfer unit

collection of data (4.8) for the purpose of a data transfer (4.10)

Note 1 to entry: A transfer unit does not have to be identifiable like a dataset (4.12) .

4.33

universe of discourse

view of the real or hypothetical world that includes everything of interest

[SOURCE:ISO 19101:2002, 4.29]

4.34

value domain

set of accepted values

[SOURCE:ISO/TS 19103:2005, 4.1.15]