ISO/IEC 15444-9:2023 情報技術 — JPEG 2000 画像コーディング システム — Part 9: インタラクティブ ツール、API、およびプロトコル | ページ 6

3.1.1

J2KI

ITU-T T.815 | で指定されている「j2ki」ブランドに準拠するファイル。 ISO/IEC 15444-1

3.1.2

J2KS

ITU-T T.815 | Rec. で指定されている「j2ks」ブランドに準拠するファイル。 ISO/IEC 15444-1

3.1.3

JPH

ITU-T T.814 | で指定されているファイル形式。 ISO/IEC 15444-15: 高スループット JPEG 200

3.1.4

JPEG 2000 コードストリーム

ITU-TT800 | Rec. の仕様に準拠したコード ストリーム。 ISO/IEC 15444-他の場所で指定された機能が含まれる可能性があります。

3.1.5

JPEG 2000 ファミリ ファイル

ITU-T T.8xx | Rec. で定義されているファイル形式のいずれかに準拠するファイル。 ISO/IEC 15444-x ファミリの推奨事項 |標準。

3.1.6

JPM

ITU-T T.805 | で指定されているファイル形式。 ISO/IEC 15444-

3.1.7

メタデータ

JPEG 2000 ファミリ ファイルからの「ボックス」のコレクション。

3.1.8

MJ2

ITU-T T.802 | で指定されているファイル形式。 ISO/IEC 15444-

3.2.1

connection

Transport layer virtual circuit established between two programs for the purpose of communication.

3.2.2

entity

The information transferred as the payload of a request or response.

Note 1 to entry: An entity consists of metainformation in the form of entity-header fields and content in the form of an entity-body.

3.2.3

proxy

An intermediary program which acts as both a server and a client for the purpose of making requests on behalf of other clients.

Note 1 to entry: Requests are serviced internally or by passing them on, with possible translation, to other servers.

3.3.1

cache (client-side)

Cache managed by the Client for storing JPIP data-bins.

Note 1 to entry: The Client might have a limited cache and might have to purge cached JPIP data-bins from time to time.

3.3.2

cacheable response

Response that may be stored within a cache for use in answering subsequent requests.

Note 1 to entry: Even if a resource is cacheable, there might be additional constraints on whether a cache can use the cached copy for a particular request.

3.3.3

cache-model (server-side)

Server-side estimation of the data-bins or portions of data-bins that are available in the client's cache.

Note 1 to entry: The server can add items to its estimation of the client's cache because it assumes successfully delivery, or because it has received acknowledgements of transmitted data, or because of cache-model update statements.

3.3.4

channel

Mechanism for grouping requests and responses such that only one request/response is active at a time within the group.

Note 1 to entry: Multiple channels can be used to issue multiple requests and receive multiple responses concurrently.

3.3.5

client

Program that establishes connections for the purpose of sending requests.

3.3.6

codestream image region

Intersection between the image and the region defined by the Offset and Region Size.

Note 1 to entry: The codestream image region can be empty (no area).

3.3.7

data-bin

Set of bytes of the same type of data which can be partially delivered.

3.3.8

incremental-codestream

Representation of the codestream as a collection of data-bins (main header, tile header, precinct or tile data-bins) having the same codestream identifier.

3.3.9

JPIP index table

File format box which provides information about the location of portions of a file or codestream.

3.3.10

JPEG 2000 family target

Target that corresponds to a JPEG 2000 family file.

3.3.11

logical target

Specific representation of specific original named resource, or a byte range from that specific original named resource, to which the JPIP request is directed.

Note 1 to entry: The specific representation might be transcoded from the original named resource.

3.3.12

message

Set of bytes from a single data-bin and the header identifying those bytes and the data-bin.

3.3.13

raw codestream

Representation of the codestream as a single metadata-bin.

3.3.14

request

Group of fields and values sent from the client to the server to obtain portions of an image or metadata.

3.3.15

resource

Network data object or service that can be identified by a URI.

3.3.16

response

Bytes sent from the server to the client after receiving a request.

3.3.17

server

Application program that accepts connections in order to service requests by sending back responses.

Note 1 to entry: Any given program might be capable of being both a client and a server; use of these terms refers only to the role being performed by the program for a particular connection, rather than to the program's capabilities in general.

3.3.18

session

Collection of requests and responses applying to the same resource for which the server maintains a cache model.

3.3.19

session-based

Where the server maintains a cache model.

3.3.20

stateless

Single request where the server does not make use of a cache-model in determining the response.

3.3.21

target

Logical identification of JPIP data.

Note 1 to entry: This is the name of the main target and is often the name of a file on the server.

Note 2 to entry: JPEG 2000 files or codestreams might be available in multiple representations (e.g., return type, precinct size) or vary in other ways, each identified by a unique logical target.

3.3.22

tile header

All tile-part headers for a specific tile.

3.3.23

view-window

The portion of the image data that the client desires, as expressed by the combination of the following fields that appear in the request: Region Size, Offset, Frame Size, Codestream, Codestream Context, Sampling Rate, ROI and Layers.

Note 1 to entry: The view-window is often smaller than the whole image data.

3.3.24

slice

Subset of voxels in a volumetric image with the same Z coordinate.

3.3.25

profile

Set of request fields that a server is expected to support and implement and a client communicating with a server in this profile may issue, with the expectation that the server supports them.

Note 1 to entry: Conformance is structured according to profiles.

Note 2 to entry: See Annex J.

3.3.26

variant

Collection of operating modes and features of the JPIP standard that a client and a server use to exchange requests and data.

Note 1 to entry: Clients and servers interoperate by employing a common subset of all variants.