element affiliation { macro.phraseSeq }

If included, the name of an organization may be tagged using either the <name> element as above, or the more specific orgName element.

element appInfo { att.global.attributes, model.applicationLike+ }

element application
{
   att.global.attributes,
   att.typed.attributes,
   att.datable.attributes,
   attribute ident { data.name },
   attribute version { data.versionNumber },
   ( model.labelLike+, ( model.ptrLike* | model.pLike* ) )
}

This example shows an appInfo element documenting the fact that version 1.5 of the Image Markup Tool1 application has an interest in two parts of a document which was last saved on June 6 2006. The parts concerned are accessible at the URLs given as target for the two <ptr> elements.

element author
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute n { data.text }?,
   attribute role
   {
      list { ( "Annotator" | "Infrastructure" | "Transcription" )+ }
   }?,
   macro.phraseSeq
}

Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use a generally recognized name authority file to supply the content for this element. The attributes key or ref may also be used to reference canonical information about the author(s) intended from any appropriate authority, such as a library catalogue or online resource.

In the case of a broadcast, use this element for the name of the company or network responsible for making the broadcast.

Where an author is unknown or unspecified, this element may contain text such as Unknown or Anonymous. When the appropriate TEI modules are in use, it may also contain detailed tagging of the names used for people, organizations or places, in particular where multiple names are given.

element authority { att.global.attributes, macro.phraseSeq.limited }

element availability
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute status { "free" | "unknown" | "restricted" },
   ( model.availabilityPart | model.pLike )+
}

A consistent format should be adopted

element change
{
   att.ascribed.attributes,
   att.datable.attributes,
   att.docStatus.attributes,
   att.global.attributes,
   att.typed.attributes,
   attribute target { list { data.pointer+ } }?,
   macro.specialPara
}

The who attribute may be used to point to any other element, but will typically specify a <respStmt> or <person> element elsewhere in the header, identifying the person responsible for the change and their role in making it.

It is recommended that changes be recorded with the most recent first. The status attribute may be used to indicate the status of a document following the change documented.

element date
{
   att.typed.attribute.type,
   attribute when { data.temporal.iso },
   ( text | model.gLike | model.phrase | model.global )*
}

element editor
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute n { data.text }?,
   attribute role { list { "CorpusEditor"+ } }?,
   macro.phraseSeq
}

A consistent format should be adopted.

Particularly where cataloguing is likely to be based on the content of the header, it is advisable to use generally recognized authority lists for the exact form of personal names.

element editorialDecl
{
   att.global.attribute.n,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   ( model.pLike | model.editorialDeclPart )+
}

element encodingDesc
{
   att.global.attributes,
   ( ( model.encodingDescPart | model.pLike )+ )
}

A corpus is available in EXMARaLDA format. The annotations were applied with the help of the EXMARaLDA Partitur Editor in a certain version, see appInfo. Information about the minimal segmentation in the format and the normalizations of the primary data is given in segmentation and normalization. The tagsDecl lists the annotation keys and values which are available in EXMARalDA. Each namesspace has @rend with a fixed a of values which classify the annotation according to their basic functions such as 'Trancription', 'Syntactical' and 'Morphological'. This enables searching certain annotation in more than one corpus in the LAUDATIO-Repository.

element extent
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.typed.attribute.subtype,
   attribute type { "Tokens" | "Words" },
   macro.phraseSeq
}

The <measure> element may be used to supplied normalised or machine tractable versions of the size or sizes concerned.

element fileDesc
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   (
      (
         titleStmt,
         editionStmt?,
         extent?,
         publicationStmt,
         seriesStmt?,
         notesStmt?
      ),
      sourceDesc+
   )
}

The <fileDsec> refers to the whole corpus. Each corpus has one or more editors and annotators and may have some technical supporters, see editor and author. All project and institution references can be made in affiliation for person or in publicationStmt in general. All documents of a corpus are listed in sourceDesc with a technical short name.

The major source of information for those seeking to create a catalogue entry or bibliographic citation for an electronic file. As such, it provides a title and statements of responsibility together with details of the publication or distribution of the file, of any series to which it belongs, and detailed bibliographic notes for matters not addressed elsewhere in the header. It also contains a full bibliographic description for the source or sources from which the electronic text was derived.

element forename
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   macro.phraseSeq
}

element idno
{
   att.global.attributes,
   att.sortable.attributes,
   attribute type { data.enumerated }?,
   ( text | model.gLike | idno )*
}

In the last case, the identifier includes a non-Unicode character which is defined elsewhere by means of a <glyph> or <char> element referenced here as #sym.

idno should be used for labels which identify an object or concept in a formal cataloguing system such as a database or an RDF store, or in a distributed system such as the World Wide Web. Some suggested values for type on idno are ISBN, ISSN, DOI, and URI.

element item
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute n { data.text },
   attribute corresp { text },
   macro.specialPara
}

May contain simple prose or a sequence of chunks.

Whatever string of characters is used to label a list item in the copy text may be used as the value of the global n attribute, but it is not required that numbering be recorded explicitly. In ordered lists, the n attribute on the item element is by definition synonymous with the use of the label element to record the enumerator of the list item. In glossary lists, however, the term being defined should be given with the label element, not n.

element label
{
   att.global.attributes,
   att.typed.attributes,
   att.placement.attributes,
   macro.phraseSeq
}

Labels are commonly used for the headwords in glossary lists; note the use of the global xml:lang attribute to set the default language of the glossary list to Middle English, and identify the glosses and headings as modern English or Latin:

Labels may also be used to record explicitly the numbers or letters which mark list items in ordered lists, as in this extract from Gibbon's Autobiography. In this usage the label element is synonymous with the n attribute on the item element:

Labels may also be used for other structured list items, as in this extract from the journal of Edward Gibbon:

Note that the label might also appear within the item rather than as its sibling. Though syntactically valid, this usage is not recommended TEI practice.

Labels may also be used to represent a label or heading attached to a paragraph or sequence of paragraphs not treated as a structural division, or to a group of verse lines. Note that, in this case, the label element appears within the p or <lg> element, rather than as a preceding sibling of it.

In this example the text of the label appears in the right hand margin of the original source, next to the paragraph it describes, but approximately in the middle of it.

If so desired the type attribute may be used to distinguish different categories of label.

element language
{
   att.global.attribute.n,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute style { "Language" | "LanguageType" | "LanguageArea" },
   attribute ident { data.language },
   macro.phraseSeq.limited
}

Particularly for sublanguages, an informal prose characterization should be supplied as content for the element.

element langUsage
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   language+
}

element list
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   att.typed.attribute.subtype,
   attribute type { "CorpusDocument" },
   (
      ( ( model.divTop ) | ( model.global ) )*,
      (
         ( item, model.global* )+
       | (
            headLabel?,
            headItem?,
            ( label, model.global*, item, model.global* )+
         )
      ),
      ( ( model.divBottom ), model.global* )*
   )
}

The following example treats the short numbered clauses of Anglo-Saxon legal codes as lists of items. The text is from an ordinance of King Athelstan (924–939):

Note that nested lists have been used so the tagging mirrors the structure indicated by the two-level numbering of the clauses. The clauses could have been treated as a one-level list with irregular numbering, if desired.

May contain an optional heading followed by a series of items, or a series of label and item pairs, the latter being optionally preceded by one or two specialized headings.

element namespace
{
   att.global.attribute.xmlid,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute rend
   {
      list
      {
         (
            "Lexical"
          | "Syntactical"
          | "Morphological"
          | "MarkUp"
          | "Graphical"
          | "Transcription"
          | "Other"
          | "Meta"
         )+
      }
   },
   attribute corresp { text }?,
   attribute name { data.text },
   tagUsage+
}

element normalization
{
   att.global.attribute.n,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   model.pLike+
}

element orgName
{
   att.global.attribute.n,
   att.typed.attribute.type,
   macro.phraseSeq
}

element p
{
   att.global.attributes,
   att.declaring.attributes,
   att.fragmentable.attributes,
   macro.paraContent
}

element persName { macro.phraseSeq }

element profileDesc
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   ( model.profileDescPart* )
}

Although the content model permits it, it is rarely meaningful to supply multiple occurrences for any of the child elements of profileDesc unless these are documenting multiple texts.

In earlier versions of these Guidelines, it was required that the <creation> element appear first.

element projectDesc
{
   att.global.attributes,
   att.declarable.attributes,
   model.pLike+
}

element publicationStmt
{
   att.global.attributes,
   (
      (
         ( model.publicationStmtPart.agency ),
         model.publicationStmtPart.detail*
      )+
    | model.pLike+
   )
}

Where a publication statement contains several members of the model.publicationStmtPart classes rather than one or more paragraphs or anonymous blocks, care should be taken to ensure that the repeated elements are presented in a meaningful order. It is a conformance requirement that elements supplying information about publication place, address, identifier, availability, and date be given following the name of the publisher, distributor, or authority concerned, and preferably in that order.

element ref
{
   att.global.attributes,
   att.pointing.attributes,
   att.internetMedia.attributes,
   att.typed.attributes,
   att.declaring.attributes,
   att.cReferencing.attributes,
   macro.paraContent
}

The target and cRef attributes are mutually exclusive.

element revisionDesc
{
   att.global.attribute.n,
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   ( list | listChange | change+ )
}

If present on this element, the status attribute should indicate the current status of the document. The same attribute may appear on any change to record the status at the time of that change. Conventionally change elements should be given in reverse date order, with the most recent change at the start of the list.

element segmentation
{
   att.global.attribute.n,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   model.pLike+
}

element sourceDesc
{
   att.global.attributes,
   att.declarable.attributes,
   (
      model.pLike+
    | ( model.biblLike | model.sourceDescPart | model.listLike )+
   )
}

element surname
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   macro.phraseSeq
}

element tagsDecl
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute partial { data.truthValue }?,
   ( rendition*, namespace* )
}

element tagUsage
{
   att.global.attributes,
   attribute gi { data.text },
   attribute occurs { data.count }?,
   attribute withId { data.count }?,
   attribute render { list { data.pointer+ } }?,
   macro.limitedContent
}

element TEI
{
   att.global.attributes,
   attribute version { data.version }?,
   ( teiHeader, ( ( model.resourceLike+, text? ) | text ) )
}

This element is required. It is customary to specify the TEI namespace http://www.tei-c.org/ns/1.0 on it, using the xmlns attribute.

element teiHeader
{
   att.global.attribute.n,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute type { "CorpusHeader" | "DocumentHeader" | "PreparationHeader" },
   ( fileDesc, model.teiHeaderPart*, revisionDesc? )
}

One of the few elements unconditionally required in any TEI document.

element text
{
   att.global.attributes,
   att.declaring.attributes,
   att.typed.attributes,
   (
      model.global*,
      ( front, model.global* )?,
      ( body | group ),
      model.global*,
      ( back, model.global* )?
   )
}

The body of a text may be replaced by a group of nested texts, as in the following schematic:

This element should not be used to represent a text which is inserted at an arbitrary point within the structure of another, for example as in an embedded or quoted narrative; the <floatingText> is provided for this purpose.

element title
{
   att.global.attribute.xmlbase,
   att.global.attribute.xmlspace,
   att.global.rendition.attribute.rend,
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   attribute type { "Corpus" }?,
   macro.paraContent
}

The attributes key and ref, inherited from the class att.canonical may be used to indicate the canonical form for the title; the former, by supplying (for example) the identifier of a record in some external library system; the latter by pointing to an XML element somewhere containing the canonical form of the title.

element titleStmt
{
   att.global.responsibility.attribute.cert,
   att.global.responsibility.attribute.resp,
   ( title+, model.respLike* )
}

Note that this element class does not include members of the model.inter class, which can appear either within or between paragraph-level items.

A superset of the naming elements that may appear in datelines, addresses, statements of responsibility, etc.

This class is used in the content model of elements which reference names of people or organizations.

This class of elements can occur within paragraphs, list items, lines of verse, etc.