If only the required encoding level is specified, the MEI header of a single text looks like this: If the header describes text derived from an existing TEI-compliant document or other digital document, it may be easier to use the following element, which is specifically designed for documents that come from “digitally born” text: The schemaSpec element contains a schema specification. When this element appears in encodingDesc, it allows you to embed a TEI ODD customization file in a TEI header. Alternatively, this element can be used in the body of an ODD document. The use of SDG files and their relationship to schemas is described in detail in 22 documentation items. A strong motivation in preparing the material for this chapter was to provide a primary source of useful information for cataloguing computer files in the TEI header. The TEI header is not a library catalog entry, so it doesn`t make all the essential distinctions for standard library work. It also contains a lot of information that is usually excluded from standard bibliographic descriptions. However, the developers intend to ensure that the information required for a catalog record is retrievable from the header of the TEI file and that mapping from one to the other is as simple and straightforward as possible. If the correspondence is not obvious, it may be useful to consult one of the books that influenced the development of the content of the TEI section. These include: The TEI header provides a very large collection of metadata categories, but does not claim to be complete. Certainly, individual projects want to capture specialized metadata that does not fit into one of the predefined categories identified by the TEI header or that requires a more specific element structure than suggested here. To resolve this issue, the encoder can define additional elements by using the customization methods described in 23.3 Customization.
The TEI class system makes it easy to implement such adjustments and use in exchange. A SOAP message is an XML document that consists of a required SOAP envelope, an optional SOAP header, and a required SOAP text. This XML document is called a SOAP message for the rest of this specification. The namespace identifier for the elements and attributes defined in this section is schemas.xmlsoap.org/soap/envelope/. A SOAP message contains the following: The SOAPAction HTTP request header field can be used to specify the intent of the SOAP HTTP request. The value is a URI that identifies the intent. SOAP imposes no restrictions on the format or specificity of the URI or its resolverability. An HTTP client MUST use this header field when issuing a SOAP HTTP request. SOAP, of course, follows the HTTP request-response message model, which provides SOAP request parameters in an HTTP request and SOAP response parameters in an HTTP response.
Note, however, that SOAP intermediaries are NOT the same as HTTP intermediaries. That is, an HTTP intermediary addressed with the HTTP connection header field cannot be expected to validate or process the body of the SOAP entity contained in the HTTP request. The log consists of a list of entries, one for each change. Changes can be grouped and organized using the listChange element described in Section 11.7 Identifying Changes and Revisions or the simple list item described in Section 3.8 Lists. Alternatively, a simple sequence of change elements can be given. The attributes of when and that can be specified for each change element to indicate its date or the person responsible for it. The description of the change itself can range from a single sentence to a series of paragraphs. If a number needs to be assigned to one or more changes (for example, a revision number), the global attribute n can be used to specify it. Note that any changes in a file that are considered important, whether or not they are considered new output or simply a new revision, should be noted independently in the “Revision Description” section of the file header (see Section 2.6 Description of the Revision). The TEI header provides a very large amount of information about the text itself, its source, its encodings and revisions, as well as a wealth of descriptive information such as the languages used and the situation(s) in which it was created, as well as the attitude and identity of the participants.
This diversity and richness reflects the variety of uses for electronic texts conforming to these guidelines. It is expressly not intended that all the elements described above are present in each TEI header.