ISO/IEC TR 22250-1:2002 情報技術—ドキュメントの説明と処理言語— XMLの正規言語の説明（RELAX）—パート1：RELAXコア | ページ 2

Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.

International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, 3.

The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote.

In exceptional circumstances, the joint technical committee may propose the publication of a Technical Report of one of the following types:

• type 1, when the required support cannot be obtained for the publication of an International Standard, despite repeated efforts;
• type 2, when the subject is still under technical development or where for any other reason there is the future but not immediate possibility of an agreement on an International Standard;
• type 3, when the joint technical committee has collected data of a different kind from that which is normally published as an International Standard (“state of the art”, for example).

Technical Reports of types 1 and 2 are subject to review within three years of publication, to decide whether they can be transformed into International Standards. Technical Reports of type 3 do not necessarily have to be reviewed until the data they provide are considered to be no longer valid or useful.

Attention is drawn to the possibility that some of the elements of this part of ISO/IEC TR 22250 may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.

ISO/IEC TR 22250-1, which is a Technical Report of type 3, was prepared by JISC (as JIS/TR X 0029) and was adopted, under a special “fast-track procedure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval by national bodies of ISO and IEC.

ISO/IEC TR 22250 consists of the following parts, under the general title Information technology — Document description and processing languages — Regular Language Description for XML (RELAX):

• Part 1: RELAX Core
• Part 2: RELAX Namespace

1 Scope

This Technical Report gives mechanisms for formally specifying the syntax of XML-based languages. For example, the syntax of XHTML 1.0 can be specified in RELAX.

Compared with DTDs, RELAX provides the following advantages:

• - Specification in RELAX uses XML instance (i.e., document) syntax,
• - RELAX provides rich datatypes, and
• - RELAX is namespace-aware.

The RELAX specification consists of two parts, RELAX Core and RELAX Namespace. This part of the Technical Report gives RELAX Core, which may be used to describe markup languages containing a single XML namespace. 2 of this Technical Report gives RELAX Namespace, which may be used to describe markup languages containing more than a single XML namespace, consisting of more than one RELAX Core document.

Given a sequence of elements, a software module called the RELAX Core processor compares it against a specification in RELAX Core and reports the result. The RELAX Core processor can be directly invoked by the user, and can also be invoked by another software module called the RELAX Namespace processor.

RELAX may be used in conjunction with DTDs. In particular, notations and entities declared by DTDs can be constrained by RELAX.

This part of the Technical Report also gives a subset of RELAX Core, which is restricted to DTD features plus datatypes. This subset is very easy to implement, and with the exception of datatype information, conversion between this subset and XML DTDs results in no information loss.

2 References

3 Terms and definitions

3.1 XML 1.0

For the purposes of this part of the Technical Report, the following terms and definitions given in XML 1.0 apply.

• a) start tag
• b) end tag
• c) empty-element tag
• d) attribute
• e) attribute name
• f) content
• g) content model
• h) attribute-list declaration
• i) DTD
• j) XML processor
• k) validity
• l) validating processor
• m) non-validating processor
• n) whitespace
• o) child
• p) parameter entity
• q) match

3.2 Name Spaces in XML

For the purposes of this part of the Technical Report, the following terms and definitions given in “Name Spaces in XML” apply.

• a) namespace
• b) namespace name

3.3 XML Schema 2

For the purposes of this part of the Technical Report, the following terms and definitions given in"XML Schema 2" apply.

• a) lexical representation
• b) facet
• c) datatype
• d) built-in datatype

3.4 XML Information Set

For the purposes of this part of the Technical Report, the following terms and definitions given in “XML Information Set” apply.

• a) information set
• b) document information item
• c) element information item
• d) property
• e) core property
• f) reference to skipped entity information item
• g) entity information item
• h) notation information item

3.5 Definitions specific to RELAX Core

Bibliography