ISO 23257:2022 ブロックチェーンと分散型台帳テクノロジー—リファレンスアーキテクチャ | ページ 6

3.1

activity

specified pursuit or set of tasks

[SOURCE:ISO/IEC 17789:2014, 3.2.1]

3.2

architecture

fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution

[SOURCE:ISO/IEC/IEEE 42010:2011, 3.2]

3.3

behavioural interoperability

interoperability so that the actual result of the exchange achieves the expected outcome

[SOURCE:ISO/IEC 19941:2017, 3.1.6]

3.4

data archiving

digital preservation process that is moving data into a managed form of storage for long-term retention

[SOURCE:ISO 5127:2017, 3.1.11.19]

3.5

data flow

sequence in which data transfer, use, and transformation are performed during the execution of a computer program

[SOURCE:ISO/IEC/IEEE 24765:2017, 3.1006]

3.6

disruption

incident, whether anticipated (e.g. hurricane) or unanticipated (e.g. power failure/outage, earthquake, or attack on information and communication technology systems/infrastructure) which disrupts the normal course of operations at an organization’s location

[SOURCE:ISO/IEC 27031:2011, 3.6]

3.7

distributed ledger technology governance

DLT governance

system for directing and controlling a distributed ledger technology system including the distribution of on-ledger and off-ledger decision rights, incentives, responsibilities and accountabilities

3.8

finality

property of a ledger that guarantees transactions in confirmed ledger records are irreversible and cannot be altered or deleted

3.9

functional component

functional building block needed to engage in an activity, backed by an implementation

[SOURCE:ISO/IEC 17789:2014, 3.2.3]

3.10

fungible

capable of mutual substitution among individual units

Note 1 to entry: The individual units can be digital assets, e.g. tokens.

3.11

governance

system of directing and controlling

[SOURCE:ISO/IEC 38500:2015, 2.8]

3.12

incident

anomalous or unexpected event, set of events, condition, or situation at any time during the life cycle of a project, product, service, or system

[SOURCE:ISO/IEC/IEEE 24748-1:2018, 3.22]

3.13

interoperability

ability of two or more systems or applications to exchange information and to mutually use the information that has been exchanged

[SOURCE:ISO/IEC 17788:2014, 3.1.5]

3.14

party

natural person or legal person, whether or not incorporated, or a group of either

[SOURCE:ISO/IEC 17789:2014, 7.2.3]

3.15

personally identifiable information

PII

information that (a) can be used to establish a link between the information and the natural person to whom such information relates, or (b) is or can be directly or indirectly linked to a natural person

Note 1 to entry: The “natural person” in the definition is the PII principal. To determine whether a PII principal is identifiable, account should be taken of all the means which can reasonably be used by the privacy stakeholder holding the data, or by any other party, to establish the link between the set of PII and the natural person.

[SOURCE:ISO/IEC 29100:2011/Amd 1:2018, 2.9]

3.16

policy interoperability

interoperability while complying with the legal, organizational and policy frameworks applicable to the participating systems

[SOURCE:ISO/IEC 19941:2017, 3.1.7]

3.17

provenance

information that documents the origin or source of an asset, any changes that have taken place since it was originated, and who has had custody of it since it was originated

[SOURCE:ISO/IEC 27050-1:2019, 3.19, modified — “Electronically Stored Information” has been replaced with “asset”.]

3.18

resilience

capability of a system to maintain its functions and structure in the face of internal and external change, and to degrade gracefully when this is necessary

[SOURCE:ISO 37101:2016, 3.33, modified — Definition replaced with text in Note 3 to entry, Notes to entry deleted.]

3.19

role

set of activities that serve a common purpose

[SOURCE:ISO/IEC 17789:2014, 3.2.7]

3.20

semantic data interoperability

interoperability so that the meaning of the data model within the context of a subject area is understood by the participating systems

[SOURCE:ISO/IEC 19941:2017, 3.1.5]

3.21

sub-role

subset of the activities of a given role

[SOURCE:ISO/IEC 17789:2014, 3.2.9]

3.22

syntactic interoperability

interoperability such that the formats of the exchanged information can be understood by the participating systems

[SOURCE:ISO/IEC 19941:2017, 3.1.4]

3.23

transport interoperability

interoperability where information exchange uses an established communication infrastructure between the participating systems

[SOURCE:ISO/IEC 19941:2017, 3.1.3]

3.24

smart contract

computer program stored in a DLT system wherein the outcome of any execution of the program is recorded on the distributed ledger

Note 1 to entry: A smart contract can represent terms in a contract in law and create a legally enforceable obligation under the legislation of an applicable jurisdiction.

[SOURCE:ISO 22739:2020, 3.72]

3.25

consensus

agreement among DLT nodes that 1) a transaction is validated and 2) the distributed ledger contains a consistent set and ordering of validated transactions

Note 1 to entry: Consensus does not necessarily mean that all DLT nodes agree.

Note 2 to entry: The details regarding consensus differ among DLT designs and this is a distinguishing characteristic between one design and another.

[SOURCE:ISO 22739:2020, 3.11]