ISO/TS 10303-18:2021 産業オートメーションシステムと統合—製品データの表現と交換—パート18：記述方法：SysMLXMIからWebサービスへの変換 | ページ 6

3.1.1.1

データ

人間またはコンピュータによる通信、解釈、または処理に適した形式的な方法で情報を表現すること。

[出典:ISO 10303-1:2021, 3.1.29]

3.1.1.2

実装方法

製品データを交換するためにコンピュータ システムで使用される技術を規定する ISO 10303 の一部

[出典:ISO 10303-1:2021, 3.1.39, 修正済み — 定義内で、「データ」の後のテキストが削除されました。]

3.1.1.3

情報

事実、概念、または指示。

[出典:ISO 10303-1:2021, 3.1.41]

3.1.1.4

情報モデル

製品データの概念モデル

注記 1: ISO 10303 では、情報モデルは、システムのさまざまな側面で表現される製品データを編成するオブジェクト関係モデリング手法に基づいています。

注記 2: ISO 10303 では、情報モデルは EXPRESS モデリング言語を使用して開発できます。

[出典:ISO 10303-1:2021, 3.1.42 修正済み — 例が変更されました。]

3.1.2.1

エンティティ.エンティティ

共通のプロパティによって定義される情報のクラス

[出典:ISO 10303-11:2004, 3.3.6, 修正 - 定義内で、冠詞「a」が削除されました。]

3.1.2.2

価値

データの単位

[出典:ISO 10303-11:2004, 3.3.22, 修正 - 定義において、冠詞「a」が削除されました。]

3.1.3.1

association

association classifies a set of tuples representing links between typed model elements

[SOURCE:ISO/TS 10303-15:2021, 3.1.3.2]

3.1.3.2

auxiliary

a stereotype applied to an abstract block (3.1.3.3) that has no properties

[SOURCE:ISO/TS 10303-15:2021, 3.1.3.3]

3.1.3.3

block

modular construct used for defining an entity (3.1.2.1)

Note 1 to entry: Used for defining objects in information models (3.1.1.4) such as Application activity model concepts, Application Data Planning objects, Application Domain Model Business Objects, Core model objects and ARM in SysML Entities. They may include reference, part, and value properties; constraints. They can be specializations of other Blocks.

[SOURCE:ISO/TS 10303-15:2021, 3.1.3.4]

3.1.3.4

composite aggregation

responsibility for the existence of composed object.

Note 1 to entry: If a composite object is deleted, all of its part instances that are objects are deleted with it

[SOURCE:ISO/TS 10303-15:2021, 3.1.3.5]

3.1.3.5

directed association

association between a collection of source model elements and a collection of target model elements that is said to be directed from the source elements to the target elements

[SOURCE:ISO/TS 10303-15:2021, 3.1.3.6]

3.1.3.6

enumeration

Value Type whose values are enumerated

[SOURCE:ISO/TS 10303-15:2021, 3.1.3.7]

3.1.3.7

enumeration literal

named value for an enumeration

[SOURCE:ISO/TS 10303-15:2021, 3.1.3.8]

3.1.3.8

data type

type whose instances are identified only by their value

[SOURCE:ISO/TS 10303-15:2021, 3.1.3.9]

3.1.3.9

generalization

directed relationship between a more general supertype and a more specific subtype

Note 1 to entry: Each Generalization relates a specific Classifier to a more general Classifier. Given a Classifier, the transitive closure of its general Classifiers is often called its generalizations, and the transitive closure of its specific Classifiers is called its specializations. The immediate generalizations are also called the Classifier’s subtype, and where the Classifier is a Class, its supertype.

[SOURCE:ISO/TS 10303-15:2021, 3.1.3.10]

3.1.3.10

part property

property that specifies a part with strong ownership and coincidental lifetime of its containing block (3.1.3.3) .

Note 1 to entry: It describes a local usage or a role of the typing Block in the context of the containing Block. Every Part Property has Composite Aggregation and is typed by a Block.

[SOURCE:ISO/TS 10303-15:2021, 3.1.3.12]

3.1.3.11

primitive type

definition of a predefined DataType, without any substructure

[SOURCE:ISO/TS 10303-15:2021, 3.1.3.11]

3.1.3.12

reference property

property that specifies a reference of its containing block (3.1.3.3) to another block

[SOURCE:ISO/TS 10303-15:2021, 3.1.3.13]

3.1.3.13

stereotype

limited kind of metaclass that cannot be used by itself but must always be used in conjunction with one of the metaclasses it extends

[SOURCE:ISO/TS 10303-15:2021, 3.1.3.14]

3.1.3.14

value property

property of a block (3.1.3.3) that is typed with a ValueType

[SOURCE:ISO/TS 10303-15:2021, 3.1.3.15]

3.1.4.1

openapi

<OpenAPI> semantic version number field of the OpenAPI specification version

Note 1 to entry: A required fixed field in an OpenAPI schema.

Note 2 to entry: The full definition is provided in OpenAPI specification.

3.1.4.2

info

<OpenAPI> metadata about the schema field

Note 1 to entry: A required fixed field in an OpenAPI schema.

Note 2 to entry: The full definition is provided in OpenAPI specification.

3.1.4.3

servers

<OpenAPI> connectivity information to one or more target servers field

Note 1 to entry: A fixed field in an OpenAPI schema.

Note 2 to entry: The full definition is provided in OpenAPI specification.

3.1.4.4

tags

<OpenAPI> metadata representing logical grouping field.

Note 1 to entry: The full definition is provided in OpenAPI specification.

3.1.4.5

paths

<OpenAPI> available relative paths to the individual endpoints field

Note 1 to entry: A required fixed field in an OpenAPI schema.

Note 2 to entry: The full definition is provided in OpenAPI specification.

3.1.4.6

components

<OpenAPI> container for holding various schemas

Note 1 to entry: The full definition is provided in OpenAPI specification.

3.1.4.7

response object

<OpenAPI> description of a single response from an operation

Note 1 to entry: A response object may include design-time, static links to operations based on the response.

Note 2 to entry: The full definition is provided in OpenAPI specification.

3.1.4.8

responses

<OpenAPI> reusable response objects (3.1.4.7) field

Note 1 to entry: A fixed field in the field components in an OpenAPI schema.

Note 2 to entry: The full definition is provided in OpenAPI specification.

3.1.4.9

schema object

<OpenAPI> input and output data types definition

Note 1 to entry: The full definition is provided in OpenAPI specification.

3.1.4.10

schemas

<OpenAPI> reusable schema objects (3.1.4.9)

Note 1 to entry: A fixed field in the field components (3.1.4.6) in an OpenAPI schema.

Note 2 to entry: The full definition is provided in OpenAPI specification.

3.1.5.1

resource

<HTTP> HTTP request target

Note 1 to entry: HTTP does not limit the nature of a resource; it merely defines an interface that might be used to interact with resources. Each resource is identified by a uniform resource identifier (URI).

Note 2 to entry: The full definition is provided in RFC 7231:2014, 2.

3.1.5.2

representation

<HTTP> information reflecting a past, current, or desired state of a given resource (3.1.5.1) .

Note 1 to entry: the representation is in a format that can be readily communicated via the protocol, and that consists of a set of representation metadata and a potentially unbounded stream of representation data

Note 2 to entry: The full definition is provided in RFC 7231:2014, 3.

3.1.5.3

response status code

<HTTP> result of the attempt to realise the request represented as a three-digit integer code

Note 1 to entry: only the response status codes starting with 2 (Successful), 4 (Client error) and 5 (Server error) are used.

Note 2 to entry: The full definition is provided in RFC 7231:2014, 6.

3.1.5.4

POST

method that requests that the target resource (3.1.5.1) process the representation (3.1.5.2) contained in the request

Note 1 to entry: The full definition is provided in RFC 7231:2014, 4.3.3.

3.1.5.5

GET

method that requests a representation (3.1.5.2) for the target resource (3.1.5.1) is transferred

Note 1 to entry: The full definition is provided in RFC 7231:2014, 4.3.1.

3.1.5.6

PATCH

method that requests that a set of changes described in the request entity be applied to the resource (3.1.5.1)

Note 1 to entry: The full definition is provided in RFC 6902:2013, 1.

3.1.5.7

PUT

method that requests that the target resource (3.1.5.1) state be created or replaced with the state defined by the representation (3.1.5.2) contained in the request

Note 1 to entry: The full definition is provided in RFC 7231:2014, 4.3.4.