ISO/IEC 23005-3:2019 情報技術—メディアのコンテキストと制御—パート3：感覚情報 | ページ 6

3.1 用語と定義

このドキュメントの目的のために、ISO/IEC 23005-6 および以下に記載されている用語と定義が適用されます。

ISO と IEC は、次のアドレスで標準化に使用する用語データベースを維持しています。

3 Terms, definitions and abbreviated terms

3.2 Abbreviated terms

3.3 Schema documents

In the main text of this document, the syntax of description schemes and descriptors is provided whenever possible as a single schema document.

In some cases though, and in particular for Clause 5, the syntax of description schemes and descriptors is provided as a collection of schema snippets imbricated with other text. In order to form a valid schema document, these schema components should be gathered in a single document with the schema wrapper provided at the head of the clause. For better readability, the relevant schema documents are provided in Annex B.

In all cases, each schema document has a version attribute, the value of which is"ISO/IEC 23005-3". Furthermore, an informative identifier is given as the value of the id attribute of the schema component. This identifier is non-normative and used as a convention in this document to reference another schema document. In particular, it is used for the schemaLocation attribute of the include and import schema components.

3.4 Use of prefixes

For clarity, throughout this document, consistent namespace prefixes are used.

"xsi:" prefix is not normative. It is a naming convention in this document to refer to an element of the http://www.w3.org/2001/XMLSchema-instance namespace.

"xml:" and"xmlns:" are normative prefixes defined in Reference [1]. The prefix “xml:” is by definition bound to" http://www.w3.org/XML/1998/namespace ". The prefix “xmlns:” is used only for namespace bindings and is not itself bound to any namespace name.

All other prefixes used in either the text or examples of this document are not normative, e.g., “sedl:”, “sev:”, “dia:”, “si”, “mpeg7:”.

In particular, most of the informative examples in this document are provided as XML fragments without the normally required XML document declaration and, thus, miss a correct namespace binding context declaration. In these descriptions fragments, the different prefixes are bound to the namespaces as given in Table 1.

Unlike the informative descriptions examples, the normative specification of the syntax of tools in XML schema follows the namespace binding context defined in the relevant schema declaration such as the one defined in 5.3.

Bibliography