ISO/IEC 19788-7:2019 情報技術—学習、教育、トレーニング—学習リソースのメタデータ—パート7：バインディング | ページ 6

3.1

conceptual

<MLR entity> the qualified entity captures the"essence" of an MLR entity defined in an ISO/IEC 19788 part and further versioned in later parts of ISO/IEC 19788 (e.g. in later editions, amendments or corrigenda)

Note 1 to entry: MLR entities are identified with MLR identifiers, and conceptual MLR entities are identified with canonical MLR identifiers.

3.2

blank node

<rdf> element from a blank node set (3.3)

Note 1 to entry: In an RDF graph (3.14) a blank node indicates the existence of a thing, without using an IRI (3.8) or a literal (3.10) to denote it. A blank node may be thought of as referring to an anonymous resource.

Note 2 to entry: In concrete RDF syntaxes, when identified, blank node identifiers are locally scoped to their container and are NOT persistent.

Note 3 to entry: The MLR standard does not use blank nodes. Each blank node is replaced by a globally unique IRI (a Skolem IRI).

Note 4 to entry: In Turtle, a concrete syntax for RDF, blank nodes in triples are expressed as _: followed by a blank node label (e.g. _:alice, _:0-34-abc).

3.3

blank node set

<rdf> infinite set disjoint from the set of all IRIs (3.8) and the set of all literals (3.10)

Note 1 to entry: Any blank node set, the set of all IRIs and the set of all literals are pairwise disjoint.

Note 2 to entry: No other conditions are imposed on a blank node set than being disjoint from IRIs and literals.

3.4

content negotiation

<web architecture> practice of providing multiple representations (3.20) available via the same URI

Note 1 to entry: Which representation is served depends on negotiation between the requesting agent and the agent serving the representations.

[SOURCE:Architecture of the World Wide Web, Volume One. W3C Recommendation. Available from: http://www.w3.org/TR/2004/REC-webarch-20041215/ ]

3.5

graph store

<rdf> mutable container of RDF graphs (3.14) managed by a single service

Note 1 to entry: Graph stores are similar to RDF datasets (3.12) , but unlike an RDF dataset, named graphs can be added to or deleted from a graph store.

Note 2 to entry: A graph store can be viewed as a mutable RDF dataset.

[SOURCE:SPARQL 1.1 Update — W3C Recommendation 21 March 2013, Section 2. Available from: http://www.w3.org/TR/2013/REC-sparql11-update-20130321/ ]

3.6

information resource

<web architecture> resource which has the property that all of its essential characteristics can be conveyed in a message

[SOURCE:Architecture of the World Wide Web, Volume One. W3C Recommendation. Available from: http://www.w3.org/TR/2004/REC-webarch-20041215/ ]

3.7

Internationalized Resource Identifier

IRI

<general> sequence of characters that conforms to the syntax defined in RFC 3987

Note 1 to entry: IRIs may be written on paper, read aloud, stored or transmitted digitally. The same IRI may be represented in many different ways.

3.8

Internationalized Resource Identifier

IRI

<rdf> Unicode/ISO/IEC 10646 string that conforms to the syntax defined in RFC 3987

Note 1 to entry: IRIs in the RDF abstract syntax MUST be absolute and MAY contain a fragment identifier.

Note 2 to entry: When IRIs are used in operations that are only defined for URIs, they must first be converted according to the mapping defined in section 3.1 of RFC 3987. A notable example is retrieval over the HTTP protocol. The mapping involves UTF-8 encoding of non-ASCII characters, %-encoding of octets not allowed in URIs, and Punycode-encoding of domain names.

[SOURCE:RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February 2014, Section 3.2. Available from: http://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/ ]

3.9

language-tagged string

<rdf> literal (3.10) for which the third component is present

Note 1 to entry: Most concrete RDF syntaxes represent language-tagged strings without the datatype IRI because it always equals http://www.w3.org/1999/02/22-rdf-syntax-ns#langString.

3.10

literal

[SOURCE:RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February 2014, Section 3.3. Available from: http://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/ ]

3.11

media type

metadata for a representation (3.20) , as per IETF RFC 6838, that provides format specification and preferred interpretation for the representation

Note 1 to entry: Media types, also called Internet media types, were previously called MIME types when used essentially for email sent through the SMTP protocol.

Note 2 to entry: Registry of Internet media type is available online at http://www.iana.org/assignments/media-types .

3.12

RDF dataset

Note 1 to entry: The default graph does not have a name and MAY be empty.

Note 2 to entry: Each named graph is a pair consisting of an IRI (3.8) or a blank node (3.2) (the graph name ), and an RDF graph. Graph names are unique within an RDF dataset.

Note 3 to entry: Blank nodes can be shared between graphs in an RDF dataset.

Note 4 to entry: RDF datasets are non-mutable (immutable): adding or removing RDF triples or RDF graphs from an RDF dataset yields a different RDF dataset.

Note 5 to entry: Despite the use of the word"name" in"named graph", the graph name is not required to denote the graph. It is merely syntactically paired with the graph. RDF does not place any formal restrictions on what resource the graph name may denote, nor on the relationship between that resource and the graph.

[SOURCE:Adapted from RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February 2014, Section 4. Available from: http://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/ ]

3.13

RDF document

<rdf> document that encodes an RDF graph (3.14) or RDF dataset (3.12) in a concrete RDF syntax, such as Turtle, RDFa, JSON-LD or TriG

Note 1 to entry: RDF documents enable the exchange of RDF graphs and RDF datasets between systems.

[SOURCE:RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February 2014, Section 1.8. Available from: http://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/ ]

3.14

RDF graph

set of RDF triples (3.18)

Note 1 to entry: RDF graphs are non-mutable (immutable): adding or removing RDF triples from an RDF graph yields a different RDF graph.

3.15

RDF node set

set of subjects and objects from all the RDF triples (3.18) of an RDF graph (3.14)

3.16

RDF source

persistent and mutable source or container for RDF graphs (3.14)

Note 1 to entry: An RDF source is a resource whose state can change over time.

Note 2 to entry: Examples of RDF sources are files containing a serialization of an RDF graph using a concrete RDF syntax and triple stores (3.22).

[SOURCE:Adapted from RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February 2014, Section 1.5. Available from: http://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/ ]

3.17

RDF term

IRI (3.8) , literal (3.10) or blank node (3.2)

Note 1 to entry: IRIs, literals and blank nodes are distinct and distinguishable. For example, http://example.org/ as a string literal is neither equal to http://example.org/ as an IRI, nor to a blank node with the blank identifier http://example.org/.

[SOURCE:RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February 2014, Section 3.1. Available from: http://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/ ]

3.18

RDF triple

Note 1 to entry: Any IRI denotes an entity in the world (the"universe of discourse").

Note 2 to entry: Triples are written in the order subject, predicate, object.

[SOURCE:Adapted from RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February 2014, Section 3.1. Available from: http://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/ ]

3.19

RDF vocabulary

collection of IRIs (3.8) intended for use in RDF graphs (3.14)

[SOURCE:RDF 1.1 Concepts and Abstract Syntax — W3C Recommendation 25 February 2014, Section 1.4. Available from: http://www.w3.org/TR/2014/REC-rdf11-concepts-20140225/ ]

3.20

representation

<web architecture> data that encode information about resource state

Note 1 to entry: A resource may have more than one representation: The information resource"Turtle, Termites, and Traffic Jams" by Mitchel Resnick (ISBN 0-262-18162-2) could have textual representations (plain text, HTML, epub, portable document format (PDF), Microsoft Word, Braille, etc.), representations in various languages (English, French, etc.), audio representations, etc.

Note 2 to entry: Metadata such as character encoding (e.g. UTF-8, UTF-16, US-ASCII, ISO-8859-1) or content encoding (e.g. XML, HTML, JPEG video, JSON file) may be provided.

[SOURCE:Adapted from Architecture of the World Wide Web, Volume One. W3C Recommendation, 2004. Available from: http://www.w3.org/TR/2004/REC-webarch-20041215/ ]

3.21

simple literal

<rdf> literal (3.10) for which the datatype IRI (3.8) ishttp://www.w3.org/2001/XMLSchema#string

Note 1 to entry: Most concrete syntaxes represent simple literals without the datatype IRI because it always equals http://www.w3.org/2001/XMLSchema#string.

3.22

triple store

<rdf> specialized database for the storage and retrieval of RDF triples (3.18)

Note 1 to entry: A triple store is an RDF source (3.16) .

3.23

Web resource

information resource (3.6) that"lives on the World Wide Web"

Note 1 to entry: A Web resource can be denoted by an HTTP IRI and under normal conditions (server not down), a representation of the resource (the exact representation retrieved might depend on content negotiation) can be retrieved using that IRI and the HTTP protocol.