ISO 26324:2012 情報と文書 — デジタルオブジェクト識別システム | ページ 6

3.1

allowed value

item which may be used as a value of an element

3.2

application profile

set of DOI names that share some common characteristics

Note 1 to entry: A DOI application profile is a grouping mechanism for DOI names; the functional specification of the application profile includes a set of metadata, comprising the kernel metadata and additional information applicable to that particular genre of object and functional requirements. Each DOI name is associated with one or more application profiles.

3.3

data dictionary

repository for all data elements and allowed values of those elements used in DOI metadata specifications

3.4

DOI name

string that specifies a unique object (3.9) within the DOI system (3.6)

Note 1 to entry: Names consist of characters in a sequence specified by the DOI syntax (3.5) .

Note 2 to entry: The terms “identifier” and “number” are sometimes but not always used in the same sense and are to be avoided where ambiguity can arise. The unqualified use of “DOI” alone can also be ambiguous. Therefore “DOI” is always used in conjunction with a specific noun [e.g. DOI name (3.4) , DOI system (3.6) ] unless the meaning is sufficiently clear from an earlier mention or the specific context.

3.5

DOI syntax

rules for the form and sequence of characters comprising any DOI name (3.4) , specifically the form and character of a prefix element, separator and suffix element

3.6

DOI system

social and technical infrastructure for the assignment and administration of DOI names (3.4) as identifiers in computer-readable form through assignment, resolution, referent description, administration, etc.

3.7

interoperability

ability of independent systems to exchange meaningful information and initiate actions from each other, in order to operate together to mutual benefit

Note 1 to entry: In particular, interoperability constitutes the ability for loosely-coupled independent systems to be able to collaborate and communicate. See References [17] and [18] for further information about interoperability.

3.8

metadata

specific data associated with a referent within the DOI system (3.6) , based on a structured data model that enables the referent of the DOI name (3.4) to be associated with data of any desired degree of precision and granularity to support identification, description and services

Note 1 to entry: This can involve one or more intermediate mapping operations. The resolution might or might not return an instance of the object. Multiple resolution is the simultaneous return as output of several pieces of current information related to the object, in defined data structures.

3.9

object

entity within the scope of the DOI system (3.6) that can be digital, physical or abstract

Note 1 to entry: Digital, physical or abstract forms of an entity can be of relevance in information and documentation (e.g. resources, people or agreements).

Note 2 to entry: A particular object identified by a specific DOI name (3.4) is the referent (3.12) of that DOI name.

3.10

opaque string

syntax string that has no meaning discernible by simple inspection

Note 1 to entry: To discover meaning, metadata are required.

3.11

persistent

existence, and ability to be used in services outside the direct control of the issuing assigner, without a stated time limit

3.12

referent

particular object (3.9) identified by a DOI name (3.4)

3.13

registrant

person or organization that has requested and received the registration of a particular DOI name (3.4)

3.14

registrant code

unique string assigned to a registrant, forming part of the prefix element of the DOI syntax (3.5) but having no other implied meaning

3.15

resolution

process of submitting a DOI name (3.4) to a network service and receiving in return one or more pieces of current information related to the identified object such as metadata or a location (URL) of the object or of metadata

3.16

unique identification

specification by a DOI name (3.4) of one and only one referent (3.12)