This document defines an XML schema for XML instance documents or fragments thereof, which represent document control information for documents that conform to the ISO guidelines for international standards. This XML schema is a building block for import into larger XML schemas, such as machine readable profiles (see DSP8028). This XML schema uses the "Venetian Blind" design pattern for the most part. In that pattern, only the XML elements intended to be used as root elements are declared as global elements in the XML schema, and all relevant XML types are declared as global types, for internal use by the XML schema. Any global types are not intended to be used by referencing XML schemas. This XML schema maintains forward compatibility with respect to its XML instance documents as follows: An updated minor version of the XML schema (for example, "m.n+1.*") shall successfully validate XML instance documents that validated successfully using the original version of the XML schema (for example, "m.n.*"). An XML instance document that successfully validates against an updated minor version of the XML schema may or may not validate against the original version of the XML schema. In other words, the XML schema may introduce additional functionality as long as it does not break existing XML instance documents. Control information for the document. Internal type representing document control information. Text registries used by the document. Text registries are supposed to be resolved when producing the output of the machine readable document. Therefore, they do not appear in normative references. Text registries define text fragments for use by the profile itself or for use by tools (for example, DSP8029). Currently, the only format of such text is XHTML, and the format of the registries is that of a standard message registry (see DSP0228). A reference to a text registry used by the document. Specifies the value of the "name" attribute of the text registry within the child elements of this element, which is to be used by DSP8029 for its own purposes. If not specified, the first child element is used by DSP8029 for its own purposes. The copyright text of the document. The XHTML may contain heading elements; if it does, the top-most heading level shall be h3 and the value of the "id" attribute of any such heading elements (which are optional but needed for linking to the heading subclause) shall start with "H-" and shall be unique across the document. The confidentiality level of the document, as a string for human consumption. If the element value is the empty string, the confidentiality level shall be considered public. The name of the organization owning the document. For documents owned by DMTF, the value shall be "DMTF". The logo of the organization owning the document. The XHTML shall not contain heading elements. Contact information for the document. An identifier for the document, for programmatic use and external reference. The value shall be unique within the organization owning the document. The value shall not include version information (that is, version number or date). The value shall not change over the lifetime of the document. The value shall be compared case sensitively. For documents owned by DMTF, the value shall be the DSP number of the document, in upper case (for example, "DSP1234"). For documents owned by other organizations, the value shall conform to any additional rules defined by that organization. The title of the document. The language of the document. The type of the document. For documents owned by DMTF, the value shall be a document type defined in DSP4004. (See the enumeration of this type for allowable values.) For documents owned by other organizations, the value shall conform to any rules defined by that organization. The status of the document. For documents owned by DMTF, the value shall be a document status defined in DSP4004. (See the enumeration of this type for allowable values.) For documents owned by other organizations, the value shall conform to any rules defined by that organization. The release date of the document, in full precision, as defined by the organization owning the document. For documents owned by DMTF, the value shall conform to the DMTF versioning rules defined in DSP0004. (See the pattern definition for the allowable format.) For documents owned by other organizations, the value shall conform to any rules defined by that organization. The release version of the document. During development of the document, this is the intended release version for the document. After the release process has been initiated for the document, this is the publicly stated release version of the document. For documents owned by DMTF, the value shall conform to the DMTF versioning rules defined in DSP0004. (See the pattern definition for the allowable format.) For documents owned by other organizations, the value shall conform to any rules defined by that organization. For documents owned by DMTF, this element represents additional information for documents with status "Work in Progress"; it shall be specified if the document status is "Work in Progress," and it shall not be specified for any other document status values. For documents owned by other organizations, this element shall not be specified. For documents owned by DMTF, this element represents additional information for documents with status "In Development"; it shall be specified if the document status is "In Development," and it shall not be specified for other document status values. For documents owned by other organizations, this element shall not be specified. Text of the "Foreword" clause. For a definition of the content of the "Foreword" clause, see the ISO Directives. A "Foreword" clause is required, as per the ISO Directives. The XHTML shall not contain heading elements. Acknowledgements for this document. Introductory text for the acknowledgements. The XHTML shall not contain heading elements. A person that is acknowledged. Name of the person, typically beginning with first name and ending with last name. Name of the organization represented by the person at the time of the contributions to the document. Any special role in which the person contributed to the document (for example, editor). Text of "Introduction" clause. For a definition of the content of the "Introduction" clause, see the ISO Directives. An "Introduction" clause is optional, as per the ISO Directives. The XHTML shall not contain heading elements. Document conventions, such as typographic and ABNF usage conventions. The XHTML may contain heading elements; if it does, the top-most heading level shall be h3 and the value of the "id" attribute of any such heading elements (which is optional but needed for linking to the heading subclause) shall start with "H-" and shall be unique across the document. Text of the "Scope" clause. For a definition of the content of the "Scope" clause, see the ISO Directives. A "Scope" clause is required, as per the ISO Directives. The XHTML may contain heading elements; if it does, the top-most heading level shall be h2 and the value of the "id" attribute of any such heading elements (which are optional but needed for linking to the heading subclause) shall start with "H-" and shall be unique across the document. The change log (change history) of the document. A change log entry. Each change log entry should represent a public release of the document. Internal type for the document type. For documents owned by DMTF. Document type "Specification", as defined in DSP4004. Document type "White Paper", as defined in DSP4004. Document type "Process", as defined in DSP4004. Document type "Tech Note", as defined in DSP4004. Document type "Presentation", as defined in DSP4004. For documents owned by other organizations. Internal type for the document status. For documents owned by DMTF. "DMTF Standard" status, as defined in DSP4004. "DMTF Draft Standard" status, as defined in DSP4004. "DMTF Informational Standard" status, as defined in DSP4004. "Informational" status, as defined in DSP4004. "Work in Progress" status, as defined in DSP4004. "In Development" status, as defined in DSP4004. For documents owned by other organizations. Internal type for additional information for documents with status "Work in Progress". Work in Progress expiration date, as defined in DSP4004. Target version after the Work in Progress document becomes finalized. Internal type for additional information for documents with status "In Development". The date on which the document was last edited during development of the document. The development version of the document (also known as the "work group version") during development of the document. Internal type defining the confidentiality level of the document. For documents owned by DMTF. Confidentiality level "DMTF Confidential", as defined in DSP4004. Public confidentiality level, as defined in DSP4004. For documents owned by other organizations. Internal type defining contact information for the document. Name of the contact. For documents owned by DMTF, this shall be the fully spelled-out name of the editing body, for example, "Profile Infrastructure Working Group". Email address of the contact. For documents owned by DMTF, this shall be the address of the mailing list of the editing body. Internal type for an entry in the change log of the document. The version of the document represented by the change log entry. The release date of the document represented by the change log entry. A description of the changes in the document represented by the change log entry, relative to the previous change log entry. Internal type representing a reference to a text registry. A name that identifies the organization owning the referenced text registry. For text registries owned by DMTF, its value shall be "DMTF". For text registries owned by other organizations, its value should include a copyrighted, trademarked, or otherwise unique name that is owned by that organization or that is a registered ID assigned to that organization by a recognized global authority. An identification of the referenced text registry, as defined by the organization owning the text registry. For text registries by DMTF, the element is required and its value shall be the DSP number of the document, in upper case (for example, "DSP1234"). For text registries owned by other organizations, the element is optional unless that organization defines a stronger requirement. The title of the referenced text registry. The version of the referenced text registry. For text registries owned by DMTF, the element is required and its value shall conform to the DMTF versioning rules defined in DSP4004 (see the pattern definition for the allowable format), and the value should specify only the major and minor version numbers (for example, "1.1"). For text registries owned by other organizations, the element is optional unless that organization defines a stronger requirement. The date of the referenced text registry. For text registries owned by DMTF, the element shall not be specified. For text registries owned by other organizations, the element is optional unless that organization defines a stronger requirement; if specified, its value shall be in one of the formats: yyyy-mm-dd, yyyy-mm, yyyy. A resolvable URL targeting the version of the referenced text registry. An identifier for the text registry reference. The value shall be unique within the document that contains the text registry reference. Values of this attribute shall begin with "TextReg_" and should conform to the following ABNF rule: "TextReg_" OwningEntity "_" ID where OwningEntity and ID are the value of the like-named element. Internal type for a name that identifies the organization owning a text registry. For text registries owned by DMTF. For text registries owned by other organizations. Internal type for the version of the referenced text registry. For text registries owned by DMTF. For text registries owned by other organizations. Internal type for the date of the referenced text registry. Internal type for the name of a text registry reference.