admin administrative information within a termEntry element, contains administrative information pertaining to data management and documentation of the entry. type identifies the administrative event or information using some dypology, preferably the dictionary of data element types specified in ISO WD 12 620. CDATA responsibilityThe admin element identifies the agency or individual responsible for the data element or entry. created The admin element describes the creation of the data element or entry. updated The admin element describes the update or modification of the data element or entry. approved The admin element describes the final approval of the data element or entry. domain The element indicates the subject area to which a concept pertains. subdomain The element indicates the subdomain of the subject area to which the concept pertains. #IMPLIED

A much fuller list of values for the type attribute may be generated from the dictionary of data element types under preparation as ISO TC 37/SC 3/WD 12 620, Computational Aids in Terminology. See ISO 12 620 for fuller details. date indicates the date of the administrative event or information marked by the element. CDATA a date in ISO standard form (yyyy-mm-dd). #IMPLIED

The date attribute should be used on the admin element to indicate the date of the administrative process (creation, update, approval, etc.) being recorded, rather than a separate date element linked to the admin element by a depend attribute. resp responsibility indicates the agency or individual responsible for the entry or data element on which the admin element depends, or for the administrative procedure recorded by the admin element. CDATA any string of characters (usually the acronym of the agency or the initials of an individual). #IMPLIED

Some terminological database systems treat responsibility as a cross reference to a personnel entry.

For domain or other similar information, the admin element should be used to provide the domain information as the content of the element:

plastics ]]>

In the case of responsibility information or information about maintenance of the entry, the admin element may have no content at all, its information all having been conveyed by the attributes type, date, and resp:

]]>
]]>

Administrative data take widely varying forms in different terminological databases; the type attribute should be used to indicate the particular class of administrative information involved. The admin element should also be used to record dates of major changes to the term entry, if these are to be recorded. base tag set for terminological data May contain character data and phrase-level elements. termEntry %paraContent; ]]> ]]> base global attributes for terminological data. defines attributes for all elements in documents which use the base tag set for terminological data. group indicates the group (term and related elements) to which this element should be associated. CDATA any string matching the n attribute value on the term element to which the group is attached. #IMPLIED

The group attribute provides a specialized pointing mechanism for use within termEntry elements. depend indicates the parent element to which this element should be associated. CDATA any string matching the n attribute value on the element to which the dependent element is attached. #IMPLIED

If no depend or group attribute is specified, the element is assumed to relate to the most recently specified term or otherForm element.

The attributes shared by this element class are used for linking elements, possibly not adjacent in the record, which are related (e.g. a grammatical annotation and the term it describes). The usual ID/IDREF-based pointing mechanisms are not used, primarily because the requirement that SGML ID values be unique within a document places an impractical burden on the encoder when terminological data from several sources are to be merged. base tag set for terminological data bibl bibliographic citation contains a loosely-structured bibliographic citation of which the sub-components may or may not be explicitly tagged. Blain, Clements and Grundy: Feminist Companion to Literature in English (Yale, 1990) ]]> The Interesting story of the Children in the Wood. In Victor E Neuberg, The Penny Histories. OUP 1968. ]]> base tag set for common core features Contains either just prose, or any combination of elements from the citation class %m.bibl.part; %m.phrase; #PCDATA ]]> ]]> bibl bibliographic elements.

base tag set for common core features bibl.full contains a fully-structured bibliographic citation, in which all components of the TEI file description are present. Blain, Virginia Clements, Patricia Grundy, Isobel The Feminist Companion to Literature in English: women writers from the middle ages to the present </title.stmt> <edition.stmt> <edition>UK edition</edition> <extent>1231 pp</extent> <publication.stmt> <creation.date>1990 <publisher>Yale University Press <place>New Haven and London <date>1990 </publication.stmt> <source.desc>No source: this is an original work</source.desc> </bibl.full> ]]> </eg></exemplum> <remarks></remarks> <part>base tag set for common core features</part> <classes names='clbibl'> <files names=""> <datadesc></datadesc> <parents> </parents> <children>edition.stmt extent notes.stmt publication.stmt series.stmt source.desc title.stmt </children> <elemdecl> <![ CDATA [ <!ELEMENT bibl.full - o (title.stmt, edition.stmt?, extent?, publication.stmt, series.stmt?, notes.stmt?, source.desc*) > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST bibl.full %a.global; > ]]> </attldecl> <xref target='CObi'> <xref target=HD3> </tagdoc> <tagdoc usage=opt id="biblstru"><gi>bibl.struct</gi> <name>structured bibliographic citation</name> <desc>contains a structured bibliographic citation, in which only bibliographic subelements appear and in a specified order. </desc> <attlist> </attlist> <exemplum><eg><![ CDATA[ <bibl.struct> <monogr> <author>Blain, Virginia <author>Clements, Patricia <author>Grundy, Isobel <title>The Feminist Companion to Literature in English: women writers from the middle ages to the present</> <imprint><publisher>Yale University Press</> <city>New Haven and London</> <date>1990</> </monogr> </bibl.struct> ]]> </eg></exemplum> <remarks></remarks> <part>base tag set for common core features</part> <classes names='clbibl'> <files names=""> <datadesc></datadesc> <parents> </parents> <children>analytic idno monogr note series </children> <elemdecl> <![ CDATA [ <!ELEMENT bibl.struct - o (analytic?, (monogr, series*)+, (note | idno)*) > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST bibl.struct %a.global; > ]]> </attldecl> <xref target='CObi'> </tagdoc> <classDoc id=biblpart type=model> <class>bibl.part <name>bibliographic citation part <desc>elements which can appear within bibliographic citations, but cannot appear freely in running text outside bibliographic citations. <attlist> </attlist> <remarks><p>This class is used in defining the content model of <gi>bibl</gi>. <part>base tag set for common core features</part> <classes> <files names=""> <xref target=CObi> </classdoc> <tagdoc usage=req id="body"><gi>body</gi> <name>text body</name> <desc>contains the whole body of a single unitary text, excluding any front or back matter.</desc> <attlist> </attlist> <exemplum><eg><![ CDATA [ ]]> </eg></exemplum> <remarks> <part>base tag set for prose texts</part> <classes> <files names=""> <parents>text </parents> <children>%m.divbot; %m.divtop; %seq; div div0 div1 </children> <elemdecl> <![ CDATA [ <!ELEMENT body - O ((%m.divtop;)*, %seq;, (div* | div0* | div1*), (%m.divbot;)*) > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST body %a.global; > ]]> </attldecl> <xref target=PR1> </tagdoc> <classdoc type=model ID=data><class>data</class> <desc>phrase-level elements containing names, dates, numbers, measures, and similar data. </desc> <attlist></attlist> <remarks><p></remarks> <part>base tag set for common core features</part> <classes names=phrase> <files names=""> <xref target=COna> </classdoc> <tagDoc id=date usage=opt> <gi>date</gi> <desc>contains a date in any format. <attlist> <attDef usage=opt> <attname>calendar <desc>indicates the system or calendar to which the date belongs. <datatype>CDATA <valdesc>Recommended values include: <term>Gregorian</term>, <term>Julian</term>, <term>Roman</term>, <term>Mosaic</term>, <term>Revolutionary</term>, <term>Islamic</term>. </valdesc> <default>#IMPLIED <eg><![ CDATA [ He was born on <date calendar=Gregorian>Feb. 22, 1732</date> (<date calendar=Julian value='1732-2-22'>Feb. 11, 1731/32, O.S.</date>). ]]> <!-- Entry on George Washington, Columbia Encyclopedia, 2d ed. --> <!-- ed. William Bridgwater and Elizabeth J. Sherwood --> <!-- (Morningside Heights: Columbia UP, 1950), p. 2111 --> </eg> </attDef> <attDef usage=opt> <attname>value <desc>gives the value of the date in some standard form, usually yyyy-mm-dd. <datatype>CDATA <valdesc>Any string representing a date in standard format; recommended form is <q>yyyy-mm-dd</q>, as defined by ISO 8601: 1988, <title>Data elements and interchange formats --- Information interchange --- Representation of dates and times. #IMPLIED 27th of May (old style). ]]>

For simple dates, the value should give the Gregorian date in the form (yyyy-mm-dd) specified by ISO 8601. More complicated dates or special applications may require another calendar or another form; these should be documented in the std.vals element in the TEI Header. certainty indicates the degree of certainty attributed to the date. CDATA Any appropriate value, e.g. ca., approx, after, before. #IMPLIED 21 Feb 1980 ]]> Twelfth Day of June in the Year of Our Lord One Thousand Nine Hundred and Seventy-seven of the Republic the Two Hundredth and first and of the University the Eighty-Sixth. ]]> September 1990 ]]> additional tag set for common core features May contain character data and phrase-level elements. %phrase.seq; ]]> ]]> descrip description within a termEntry element, contains a definition, context or explanation used to explain or define the concept represented by a term or an other form. type classifies the description using some convenient typology, preferably the dictionary of data element types specified in ISO WD 12 620. CDATA definition The description provides all the information needed to differentiate one concept from all other related concepts in the given domain. #IMPLIED

A much fuller list of values for the type attribute may be generated from the dictionary of data element types under preparation as ISO TC 37/SC 3/WD 12 620, Computational Aids in Terminology. See ISO 12 620 for fuller details.

(optional) base tag set for terminological data May contain character data and phrase-level elements. ofig termEntry tig %paraContent; ]]> ]]> div text division contains a subdivision of the front, body or back of a text. type specifies a name for this level of subdivision, e.g. 'act', 'volume', 'book', 'section' CDATA a semi-open list of keywords #IMPLIED base tag set for prose texts any sequence of low-level structural elements, possibly grouped into lower subdivisions. body div %m.divbot; %m.divtop; %seq; div ]]> ]]> div0 level-0 text division contains the largest possible subdivision of the body of a text. type specifies a name for this level of subdivision, e.g. 'act', 'volume', 'book', 'section', 'part'. CDATA a semi-open list of keywords #IMPLIED base tag set for prose texts any sequence of low-level structural elements, possibly grouped into lower subdivisions. body %m.divbot; %m.divtop; %seq; div1 ]]> ]]> div1 level-1 text division contains a first-level subdivision of the front, body or back of a text (the largest, if div0 is not used, the second largest if it is). type specifies a name for this level of subdivision, e.g. 'chapter', 'act', 'volume', 'book', 'section' CDATA a semi-open list of keywords #IMPLIED base tag set for prose texts any sequence of low-level structural elements, possibly grouped into lower subdivisions. body div0 %m.divbot; %m.divtop; %seq; div2 ]]> ]]> div2 level-2 text division contains a second-level subdivision of the front, body or back of a text. type specifies a name for this level of subdivision, e.g. scene, part, chapter, etc. CDATA a semi-open list of keywords #IMPLIED base tag set for prose texts any sequence of low-level structural elements, possibly grouped into lower subdivisions. div1 %m.divbot; %m.divtop; %seq; div3 ]]> ]]> div3 level-3 text division contains a third-level subdivision of the front, body or back of a text. type specifies a name for this level of subdivision, e.g. subsection, canto, etc. CDATA a semi-open list of keywords #IMPLIED base tag set for prose texts any sequence of low-level structural elements, possibly grouped into lower subdivisions. div2 %m.divbot; %m.divtop; %seq; div4 ]]> ]]> div4 level-4 text division contains a fourth-level subdivision of the front, body or back of a text. type specifies a name for this level of subdivision, e.g. clause, stanza, etc. CDATA a semi-open list of keywords #IMPLIED base tag set for prose texts div3 %m.divbot; %m.divtop; %seq; div5 ]]> ]]> div5 level-5 text division contains a fifth-level subdivision of the front, body or back of a text. type specifies a name for this level of subdivision, e.g. clause, stanza, etc. CDATA a semi-open list of keywords #IMPLIED base tag set for prose texts div4 %m.divbot; %m.divtop; %seq; div6 ]]> ]]> div6 level-6 text division contains a sixth-level subdivision of the front, body or back of a text. type specifies a name for this level of subdivision, e.g. clause, stanza, etc. CDATA a semi-open list of keywords #IMPLIED base tag set for prose texts div5 %m.divbot; %m.divtop; %seq; div7 ]]> ]]> div7 level-7 text division contains the smallest possible subdivision of the front, body or back of a text, larger than a paragraph. type specifies a name for this level of subdivision, e.g. clause, stanza, etc. CDATA a semi-open list of keywords #IMPLIED base tag set for prose texts div6 %m.divbot; %m.divtop; %seq; ]]> ]]> figure denotes the location of a graphic, illustration, or figure.

This tag documentation is a temporary standin for the full documentation, which will be prepared with chapter FT on Formulas and Tables. base tag set for graphics Empty; the graphic or figure is stored externally. EMPTY ]]> ]]> formula contains a mathematical or other formula.

This tag documentation is a temporary standin for the full documentation, which will be prepared with chapter FT on Formulas and Tables. base tag set for formulae Contains only specialized formula elements. %formulaContent; ]]> ]]> global defines attributes common to all elements in the TEI encoding scheme. id identifier provides a unique identifier for the element bearing the ID value. ID any valid SGML name (in the reference concrete syntax, a name must begin with a letter and contain only letters, numeric digits, hyphen, and full stop). #IMPLIED Paragraph with the ID names....

Paragraph with the ID dates.... ]]>

The id attribute may be used to specify a canonical reference for an element; see section . n number, name, etc. gives a number (or other label) for an element, which is not necessarily unique within the document. CDATA any string of characters; often, but not necessarily, numeric. #IMPLIED

The n attribute may be used to specify the numbering of chapters, sections, list items, etc.; it may also be used in the specification of a standard reference system for the text. lang language indicates the language of the element content, usually using a two- or three-letter code from ISO 639. IDREF The value must be the identifier specified for a writing system declaration declared in the TEI header, as described in section . %INHERITED The only surviving work by Ari (died 1148) is the ten-page Íslendingabók</> (<title lang=LA>Libellus Islandorum</>), written in the early twelfth century. ]]> <!-- Carol J. Clover, The Medieval Saga (Ithaca: Cornell --> <!-- University Press, 1982), p. 149. --> </eg> <remarks><p>If no value is specified for <att>lang</att>, the <att>lang</att> value for the immediately enclosing element is inherited; for this reason, a value should always be specified on the outermost element (<gi>TEI.2</gi>). </attDef> <!-- ................................................... rend --> <attDef usage=opt> <attname>rend <name>rendition or presentation <desc>indicates how the element in question was rendered or presented in the source text. <datatype>CDATA <valdesc>any string of characters; if the typographic rendition of a text is to be systematically recorded, a systematic set of values for the <att>rend</att> attribute should be defined. <default>#IMPLIED <eg><![ CDATA [ ]]> </eg> </attDef> </attlist> <remarks><p> <part>base tag set for common core features</part> <classes> <files names=""> <xref target=STga> </classdoc> <tagDoc id=gram usage=opt> <gi>gram</gi> <name>grammatical information <desc>within a <gi>termEntry</gi> element, contains grammatical information relating to a <gi>term</gi> or to an <gi>otherForm</gi>. <attlist> <!-- ................................................... type --> <attDef usage=opt> <attname>type <desc>classifies the grammatical information given according to some convenient typology, preferably the dictionary of data element types specified in ISO WD 12 620. <datatype>CDATA <vallist type=semi> <val>pos <desc>part of speech (any of the word classes to which a words may be assigned in a given language, based on form, meaning, or a combination of features, e.g. noun, verb, adjective, etc.) <val>gen <desc>gender (formal classification by which nouns and pronouns, and often accompanying modifiers, are grouped and inflected, or changed in form, so as to control certain syntactic relationships) <val>num <desc>number (e.g. singular, plural, dual, ...) <val>animate <desc>animate or inanimate <val>proper <desc>proper noun or common noun </vallist> <default>#IMPLIED <eg><![ CDATA [ ]]> </eg> <remarks><p>A much fuller list of values for the <att>type</att> attribute may be generated from the dictionary of data element types under preparation as ISO TC 37/SC 3/WD 12 620, Computational Aids in Terminology. See ISO 12 620 for fuller details.</remarks> </attDef> </attlist> <exemplum><eg><![ CDATA [ ]]> </eg></exemplum> <remarks><p>The <gi>gram</gi> element usually refers to the most recently specified <gi>term</gi> or <gi>otherform</gi> element. In flat term entries, the <att>group</att> and <att>depend</att> attributes may be used to indicate exceptions to this general rule. <part>base tag set for terminological data</part> <classes> <files names=" teite2f"> <datadesc>May contain character data and phrase-level elements. <parents>ofig termEntry tig </parents> <children>%paraContent; </children> <elemdecl> <![ CDATA [ <!ELEMENT gram - O (%paraContent;) > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST gram %a.global; type CDATA #IMPLIED > ]]> </attldecl> <xref type=div1 target=TEta> </tagdoc> <classdoc type=model ID=hqphrase><class>hqphrase</class> <desc>phrase-level elements related to highlighting. </desc> <attlist></attlist> <remarks><p></remarks> <part>base tag set for common core features</part> <classes names='phrase'> <files names=""> <xref target=COhq> </classdoc> <classDoc id=inter type=model> <class>inter <desc>elements of the intermediate (inter-level) class, which can occur both within paragraphs and between paragraphs.</desc> <attlist> </attlist> <remarks><p>This element class contains a subset of those elements which can appear in the unstructured <soCalled>soup</soCalled> with which paragraph and other elements at the lowest level of crystal structures are filled: specifically all the elements which can also occur as structural elements in their own right. In prose, this means the elements in this class can appear both within and between paragraphs. This class is thus distinct from the purely phrase-level elements which can appear only within soup, and not on their own; the latter class, in keeping with this metaphor, is called <soCalled>broth</soCalled>; it is represented by the class <term>phrase</term>. Cf. also the class <term>chunks</term>. <part>base tag set for common core features</part> <classes> <files names=""> <xref target=STec> </classdoc> <classdoc type=both ID=loc><class>loc</class> <desc>elements used for purposes of location and reference</desc> <attlist> <attdef usage=opt><attname>type</attname> <desc>categorizes the pointer in some respect, using any convenient set of categories.</desc> <datatype>CDATA </datatype> <valdesc>The type should indicate the intended function of the pointer, or the rhetorical relationship between its source and target. </valdesc> <default>#IMPLIED</default> </attdef> <attdef usage=opt><attname>resp</attname> <!-- was author, then ed --> <desc>specifies the creator of the pointer.</desc> <datatype>CDATA </datatype> <valdesc>any string of characters, usually the initials or name of the creator.</valdesc> <default>#IMPLIED</default></attdef> <attdef usage=opt><attname>crdate</attname> <!-- was cre.date --> <desc>specifies when the pointer was created.</desc> <datatype>CDATA</datatype> <valdesc>any string representing a date.</valdesc> <default>#IMPLIED</default></attdef> <attdef usage=opt><attname>targType</attname> <!-- added by LB --> <desc>specifies the kinds of elements to which this pointer may point. </desc> <datatype>NAMES </datatype> <valdesc>A list of names of SGML elements defined in the DTD of the current document.</valdesc> <default>#IMPLIED</default> <remarks><p>If this attribute is supplied, every element specified as a target must be of one or the other of the types specified. An application may choose whether or not to report failures to satisfy this constraint as errors, but may not access an element of the right identifier but the wrong type. </attdef> <attdef usage=opt><attname>targOrder</attname> <!-- added by LB --> <desc>where more than one identifier is supplied as the value of the <att>target</att> attribute, this attribute specifies whether the order in which they are supplied is significant.</desc> <datatype>(Y | N | U)</datatype> <vallist type=closed><val>Y<desc>Yes: the order in which IDREFs are specified as the value of a <att>target</att> attribute should be followed when combining the targeted elements. <val>N <desc>No: the order in which IDREFs are specified as the value of a <att>target</att> attribute has no significance when combining the targeted elements. <val>U <desc>Unspecified: the order in which IDREFs are specified as the value of a <att>target</att> attribute may or may not be significant. </vallist> <default>U</default> </attdef> <attdef usage=opt><attname>evaluate</attname> <!-- added by LB --> <desc>specifies the intended meaning when the target of a pointer is itself a pointer.</desc> <datatype>(all | one | none)</datatype> <vallist> <val>all<desc>if the element pointed to is itself a pointer, then the target of that pointer will be taken, and so on, until an element is found which is not a pointer. <val>one <desc>if the element pointed to is itself a pointer, then its target (whether a pointer or not) is taken as the target of this pointer. <val>none<desc>no further evaluation of targets is carried out beyond that needed to find the element specified in the pointer's target. </vallist> <default>#IMPLIED</default> <remarks><p>If no value is given, the application program is responsible for deciding (possibly on the basis of user input) how far to trace a chain of pointers. </attdef> </attlist> <remarks><p></remarks> <part>base tag set for common core features</part> <classes><files names=""> <xref target=COxr> </classdoc> <tagDoc id=note usage=rec> <gi>note</gi> <desc>contains a note or annotation. <attlist> <attDef usage=opt> <attname>n <name>number or symbol <desc>indicates the symbol or number used to mark the note's point of attachment to the main text. <datatype>CDATA <valdesc>any string of characters <default>#IMPLIED <eg><![ CDATA [ Mevorakh b. Saadya's mother, the matriarch of the family during the second half of the eleventh century, <note n=126> The alleged mention of Judah Nagid's mother in a letter from 1071 is, in fact, a reference to Judah's children; cf. above, nn. 111 and 54. </note> is well known from Geniza documents published by Jacob Mann. ]]> </eg> <remarks><p>If notes are numbered in sequence and their numbering can be reconstructed automatically by processing software, it may not be considered necessary to record the note numbers. </attDef> <attDef usage=opt> <attname>type <desc>describes the type of note. <datatype>CDATA <valdesc>Values can be taken from any convenient typology of annotation suitable to the work in hand; e.g. annotation, gloss, citation, digression, preliminary, temporary, ... <default>#IMPLIED </attDef> <attDef usage=rwa> <attname>resp <name>responsible <desc>indicates who is responsible for the annotation: author, editor, translator, etc. <datatype>CDATA <vallist type=open> <val>auth[or] <desc>note originated with the author of the text. <val>ed[itor] <desc>note added by the editor of the text. <val>comp[iler] <desc>note added by the compiler of a collection. <val>tr[anslator] <desc>note added by the translator of a text. <val>transcr[iber] <desc>note added by the transcriber of a text into electronic form. <val>(initials) <desc>note added by the individual indicated by the initials. </vallist> <default>#IMPLIED <remarks><p>For specialized types of editorial annotation (e.g. for marking corrections, normalizations, cruxes, etc.), see chapter <xref type=div1 target=TC>. </attDef> <attDef usage=opt> <attname>place <desc>indicates where the note appears in the source text. <datatype>CDATA <vallist type=open> <val>foot <desc>note appears at foot of page. <val>end <desc>note appears at end of chapter or volume. <val>inline <desc>note appears as a marked paragraph in the body of the text. <val>left <desc>note appears in left margin. <val>right <desc>note appears in right margin. <val>interlinear <desc>note appears between lines of the text. <val>app[aratus] <desc>note appears in the apparatus at the foot of the page. </vallist> <default>'unspecified' <eg><![ CDATA [ ]]> </eg> <remarks><p>For pages with multiple apparatus, values such as <term>app1</term> and <term>app2</term> can be used. <p>The <att>place</att> attribute can be used to indicate to text formatting software where a note should be printed. If the locations indicated do not agree with those in the copy text, that fact should be indicated in the TEI header. </attDef> <attDef usage=opt> <attname>anchored <desc>indicates whether the copy text shows the exact place of reference for the note. <datatype>(yes | no) <vallist type=closed> <val>yes <desc>copy text indicates the place of attachment for the note. <val>no <desc>copy text indicates no place of attachment for the note. </vallist> <default>yes <remarks><p>In modern texts, notes are usually anchored by means of explicit footnote or endnote symbols. An explicit indication of the phrase or line annotated may however be used instead (e.g. <q>page 218, lines 3-4</q>). The <att>anchored</att> attribute indicates whether any explicit location is given, whether by symbol or by prose cross-reference. If the specific symbols used are to be recorded, use the <att>n</att> attribute. </attDef> <attDef usage=rwa> <attname>target <desc>indicates the point of attachment of a note, or the beginning of the span to which the note is attached. <datatype>IDREF <valdesc>reference to the <att>id</att> of an element which begins at the location in question (e.g. the <att>id</att> of an <gi>anchor</gi> element). <default>#IMPLIED <eg><![ CDATA [ ]]> </eg> <remarks><p>If <att>target</att> and <att>target.end</att> are to be used to indicate where notes attach to the text, then elements at the appropriate locations (<gi>anchor</gi> elements if necessary) must be given <att>id</att> values to be pointed at. </attDef> <attDef usage=rwa> <attname>target.end <desc>points to the end of the span to which the note is attached, if the note is not embedded in the text at that point. <datatype>IDREF <valdesc>reference to the <att>id</att> of an element which <emph>ends</emph> at the location in question, or to an empty element at the point in question. <default>#IMPLIED <eg><![ CDATA [ ]]> </eg> <remarks><p> </attDef> </attlist> <exemplum><eg><![ CDATA [ And yet it is not only in the great line of Italian renaissance art, but even in the painterly <note resp=Tr><term lang=DE>Malerisch</term>. This word has, in the German, two distinct meanings, one objective, a quality residing in the object, the other subjective, a mode of apprehension and creation. To avoid confusion, they have been distinguished in English as <cited>picturesque</cited> and <cited>painterly</cited> respectively. (Tr.)</note> style of the Dutch genre painters of the seventeenth century that drapery has this psychological significance. ]]> </eg> </exemplum> <remarks><p> <part>additional tag set for common core features</part> <classes names='notes biblpart'> <files names=""> <datadesc>May contain character data and phrase-level elements. <parents>bibl.struct termEntry </parents> <children>%specialPara; </children> <elemdecl> <![ CDATA [ <!ELEMENT note - O (%specialPara;) > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST note %a.global; n CDATA #IMPLIED type CDATA #IMPLIED resp CDATA #IMPLIED place CDATA 'unspecified' anchored (yes | no) yes target IDREF #IMPLIED target.end IDREF #IMPLIED > ]]> </attldecl> <xref type=div2 target=COno> </tagdoc> <classdoc type=model ID=notes><class>notes</class> <desc>note-like elements. </desc> <attlist></attlist> <remarks><p></remarks> <part>base tag set for common core features</part> <classes names=inter> <files names=""> <xref target=COno> </classdoc> <tagDoc id=ofig usage=rwa> <gi>ofig</gi> <name>other-form information group <desc>within a <gi>tig</gi> element, contains information elements relating to a single <gi>otherForm</gi>. <attlist> <!-- ................................................... type --> <attDef usage=opt> <attname>type <desc>classifies the other-form information group according to some convenient typology, preferably the dictionary of data element types specified in ISO WD 12 620. <datatype>CDATA <valdesc>any string identifying a class of <gi>ofig</gi> <default>#IMPLIED <eg><![ CDATA [ ]]> </eg> <remarks><p>A much fuller list of values for the <att>type</att> attribute may be generated from the dictionary of data element types under preparation as ISO TC 37/SC 3/WD 12 620, Computational Aids in Terminology. See ISO 12 620 for fuller details.</remarks> </attDef> </attlist> <exemplum><eg><![ CDATA [ ]]> </eg></exemplum> <remarks><p> (optional) <part>base tag set for terminological data</part> <classes> <files names=""> <datadesc>May contain an <gi>otherForm</gi> element and any data elements relating to the <gi>otherForm</gi> or to one of its related elements. <parents>tig </parents> <children>descrip gram otherForm </children> <elemdecl> <![ CDATA [ <!ELEMENT ofig - O (otherForm, gram*, descrip*) > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST ofig %a.global; type CDATA #IMPLIED > ]]> </attldecl> <xref type=div1 target=TEta> </tagdoc> <tagDoc id=othform usage=rec> <gi>otherForm</gi> <name>other form <desc>within a term information group (<gi>tig</gi>), contains an alternate designation, such as a synonym, for the concept treated by the term entry. <attlist> <!-- ................................................... type --> <attDef usage=opt> <attname>type <desc>classifies the <gi>otherForm</gi> using some typology, preferably the dictionary of data element types specified in ISO WD 12 620. <datatype>CDATA <valdesc>any string of characters; for serious terminological work, values should be taken from the dictionary of data element types specified in ISO WD 12 620. <default>#IMPLIED <eg><![ CDATA [ ]]> </eg> </attDef> </attlist> <exemplum><eg><![ CDATA [ ]]> </eg></exemplum> <remarks><p>In nested term entries, the <gi>otherForm</gi> belongs to the same terminological information group as the term for which it is an alternate. <part>base tag set for terminological data</part> <classes> <files names=" teite2f"> <datadesc>May contain character data and phrase-level elements. <parents>ofig </parents> <children>%paraContent; </children> <elemdecl> <![ CDATA [ <!ELEMENT otherForm - O (%paraContent;) > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST otherForm %a.global; type CDATA #IMPLIED > ]]> </attldecl> <xref type=div1 target=TEta> </tagdoc> <classDoc id=phrase type=model> <class>phrase</class> <desc>includes elements which can occur at the level of individual words or phrases.</desc> <attlist> </attlist> <remarks><p>This class of elements can occur only within larger elements of the class <term>inter</term> or <term>chunk</term>. In prose, this means these elements can occur within paragraphs, list items, lines of verse, etc. <part>base tag set for common core features</part> <classes> <files names=""> <xref target=STec> </classdoc> <tagdoc usage=opt id="ptr"><gi>ptr</gi> <desc>defines a pointer to another location in the current document. </desc> <attlist> <attdef usage=req><attname>target</attname> <desc>specifies the destination of the pointer as one or more SGML identifiers</desc> <datatype>IDREFS </datatype> <valdesc>Each value specified must be the same as that specified as value for an <att>ID</att> attribute for some other element in the current SGML document.</valdesc> <default>#REQUIRED</default> </attdef> </attlist> <exemplum><eg><![ CDATA [ <ptr target="P2 P5" resp=LB type=s> <ptr target='D1' type='defn'> ]]> </eg></exemplum> <remarks></remarks> <part>base tag set for common core features</part> <classes names=loc> <files names=""> <parents> </parents> <children>EMPTY </children> <elemdecl> <![ CDATA [ <!ELEMENT ptr - o EMPTY > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST ptr %a.global; %a.loc; target IDREFS #REQUIRED > ]]> </attldecl> <xref target=COXR> </tagdoc> <tagdoc usage=opt id="ref"><gi>ref</gi> <desc>defines a reference to another location in the current document, in terms of one or more identifiable elements, possibly modified by additional text or comment.</desc> <attlist> <attdef usage=opt><attname>target</attname> <desc>specifies the destination of the reference as one or more SGML identifiers</desc> <datatype>IDREFS </datatype> <valdesc>Each value specified must be the same as that specified as value for an <att>ID</att> attribute for some other element in the current SGML document.</valdesc> <default>#IMPLIED</default> </attdef> </attlist> <exemplum><eg><![ CDATA [ <ref target="P2 P5" resp=LB type=s> See especially the second sentence</ref> <ref>see also s.v. <term>locution</term></ref> ]]> </eg></exemplum> <remarks></remarks> <part>base tag set for common core features</part> <classes names=loc> <files names=""> <parents> </parents> <children>%phrase.seq </children> <elemdecl> <![ CDATA [ <!ELEMENT ref - - (%phrase.seq) > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST ref %a.global; %a.loc; target IDREFS #IMPLIED > ]]> </attldecl> <xref target=COXR> </tagdoc> <entDoc id=seqte type=pe> <entName>seq <name>sequence</name> <desc>defines a sequence of elements (such as paragraphs) which can occur directly within text divisions and in similar positions. <remarks><p>This parameter entity is used in each base tag set to define the content of <gi>div</gi> and other elements. <!-- files names='teipros2'> --> <string>'(%m.common; | %m.terminology;)* ' </string> <xref target=TEdt> </entDoc><tagDoc id=table usage=rwa> <gi>table</gi> <desc>contains text displayed in tabular form, in rows and columns.</desc> <attlist> </attlist> <exemplum><eg><![ CDATA [ ]]> </eg></exemplum> <remarks><p>This tag documentation is a temporary standin for the full documentation, which will be prepared with chapter FT on Formulas and Tables. <part>base tag set for tables</part> <classes> <files names=""> <datadesc>May contain a heading and a series of rows. <parents> </parents> <children>head row </children> <elemdecl> <![ CDATA [ <!ELEMENT table - - (head*, row+) > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST table %a.global; > ]]> </attldecl> <xref type=div1 target=FT> </tagdoc> <tagdoc id=term usage=rwa> <gi>term</gi> <desc>contains a single-word, multi-word or symbolic designation which is regarded as a technical term. <attlist> <!-- ................................................... type --> <attDef usage=opt> <attname>type <desc>classifies the term using some typology. <datatype>CDATA <valdesc>any string of characters; for serious terminological work, values should be taken from the dictionary of data element types specified in ISO WD 12 620. <default>#IMPLIED <eg><![ CDATA [ ]]> </eg> </attDef> </attlist> <exemplum><eg><![ CDATA [ A computational device that infers structure from grammatical strings of words is known as a <term>parser</term>, and much of the history of NLP over the last 20 years has been occupied with the design of parsers. ]]> </eg></exemplum> <exemplum><eg><![ CDATA[ We may define <term rend=sc id=tdpv>discoursal point of view</term> as <gloss target=tdpv>the relationship, expressed through discourse structure, between the implied author or some other addresser, and the fiction.</gloss> ]]> </eg></exemplum> <remarks><p>In formal terminological work, there is frequently discussion over whether terms must be atomic or may include mullti-word lexical items, symbolic designations, or phraseological units. The <gi>term</gi> element may be used to mark any of these. No position is taken on the philosophical issue of what a term can be; the looser definition simply allows the <gi>term</gi> element to be used by practitioners of any persuasion. </remarks> <part>base tag set for common core features</part> <classes names=hqphrase> <files names=""> <datadesc>free prose <parents>termEntry tig </parents> <children>%phrase.seq; </children> <elemdecl> <![ CDATA [ <!ELEMENT term - - (%phrase.seq;) > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST term %a.global; type CDATA #IMPLIED > ]]> </attldecl> <xref target=COhqu> </tagdoc> <tagDoc id=termEntN usage=mwa> <gi>termEntry</gi> <name>terminological entry <desc>contains a single complete entry for one concept expressed in one language and comprising one or more terms and their associated descriptive and administrative data, or, in bilingual and multilingual terminology work, two or more very closely related concepts comprising one or more terms in each language and their associated descriptive and administrative data. <attlist> <!-- ................................................... type --> <attDef usage=opt> <attname>type <desc>classifies the term entry using some typology, preferably the dictionary of data element types specified in ISO WD 12 620. <datatype>CDATA <valdesc>any string of characters; for serious terminological work, values should be taken from the dictionary of data element types specified in ISO WD 12 620. <default>#IMPLIED <eg><![ CDATA [ ]]> </eg> </attDef> </attlist> <exemplum><eg><![ CDATA [ ]]> </eg></exemplum> <remarks><p>Often but not always a term entry describes all terms in a term bank denoting a given concept. In the case of a term entry documenting a concept for which no standard term exists, the term entry will have to contain a <soCalled>dummy</soCalled> <gi>tig</gi>, which contains a empty term element of the form <tag>term</tag><tag>/term</tag>. <part>base tag set for terminological data</part> <classes names='terminol'> <files names=""> <datadesc>May contain character data and phrase-level elements. <parents> </parents> <children>admin descrip note tig </children> <elemdecl> <![ CDATA [ <!ELEMENT termEntry - O (descrip*, tig+) +(admin | note)> ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST termEntry %a.global; type CDATA #IMPLIED > ]]> </attldecl> <xref type=div1 target=TEta> </tagdoc> <tagDoc id=termEntF usage=mwa> <gi>termEntry</gi> <name>terminological entry (flat structure) <desc>contains a single complete entry for one or more terms and their associated descriptive and administrative data. <attlist> <!-- ................................................... type --> <attDef usage=opt> <attname>type <desc>classifies the term entry using some typology, preferably the dictionary of data element types specified in ISO WD 12 620. <datatype>CDATA <valdesc>any string of characters; for serious terminological work, values should be taken from the dictionary of data element types specified in ISO WD 12 620. <default>#IMPLIED <eg><![ CDATA [ ]]> </eg> <remarks><p> </attDef> </attlist> <exemplum><eg><![ CDATA [ ]]> </eg></exemplum> <remarks><p>Often but not always a term entry describes all terms in a term bank denoting a given concept. In the case of a term entry documenting a concept for which no standard term exists, the term entry will have to contain an empty <soCalled>dummy</soCalled> <gi>term</gi>, of the form <tag>term</tag><tag>/term</tag>. <part>base tag set for terminological data</part> <classes names='terminol'> <files names=""> <datadesc>May contain character data and phrase-level elements. <parents> </parents> <children>%m.inter; admin descrip gram note otherform term </children> <elemdecl> <![ CDATA [ <!ELEMENT termEntry - O ( (descrip | otherform | gram | %m.inter;)*, (term, (descrip | otherform | gram | %m.inter;)* )+ ) +(admin | note)> ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST termEntry %a.global; type CDATA #IMPLIED > ]]> </attldecl> <xref type=div1 target=TEta> </tagdoc> <classDoc id=terminol type=model> <class>terminol</class> <desc>chunk-level and inter-level elements unique to the base tag set for terminological data. <attlist> </attlist> <remarks><p> (optional) <part>base tag set for terminological data</part> <classes> <files names=" teiterm2"> <xref target=TEba> <xref target=STec> </classdoc> <entDoc id=termtn type=pe> <entName>termtags</entName> <desc>system entity with definitions for basic terminology tags. <remarks><p>The default definition of this entity is used to invoke the element declarations for the <soCalled>nested</soCalled> style of terminological markup. To invoke the alternative <soCalled>flat</soCalled> style declarations, this entity should be defined as <q>system 'teite2f.dtd'</q>. <string>system 'teite2n.dtd'</string> <xref target=TEdt> </entDoc><tagdoc usage=req id="text"><gi>text</gi> <desc>contains a single text of any kind, whether unitary or composite, for example a poem, drama, collection of essays, or novel. </desc> <attlist> </attlist> <exemplum><eg><![ CDATA [ ]]> </eg></exemplum> <remarks></remarks> <part>base tag set for common core features</part> <classes> <files names=""> <parents> </parents> <children>back body front group </children> <elemdecl> <![ CDATA [ <!ELEMENT text - - (front?, (body | group), back?) > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST text %a.global; > ]]> </attldecl> <xref target=PR> </tagdoc> <tagDoc id=tig usage=opt> <gi>tig</gi> <name>term information group <desc>within a <gi>termEntry</gi> element, contains information elements associated with a single term. <attlist> <!-- ................................................... type --> <attDef usage=opt> <attname>type <desc>classifies the <gi>tig</gi> using some typology, preferably the dictionary of data element types specified in ISO WD 12 620. <datatype>CDATA <valdesc>any string of characters; for serious terminological work, values should be taken from the dictionary of data element types specified in ISO WD 12 620. <default>#IMPLIED <eg><![ CDATA [ ]]> </eg> </attDef> </attlist> <exemplum><eg><![ CDATA [ ]]> </eg></exemplum> <remarks><p>The <gi>tig</gi> element occurs only when the <soCalled>nested</soCalled> form of the terminology base is used. In the case of a term entry documenting a concept for which no standard term exists, the term entry will have to contain a <soCalled>dummy</soCalled> <gi>tig</gi>, which contains a empty term element of the form <tag>term</tag><tag>/term</tag>. <part>base tag set for terminological data</part> <classes> <files names=""> <datadesc>May contain a <gi>term</gi> element, followed by zero or more <gi>descrip</gi> elements describing the term, followed in turn by zero or more <gi>otherform</gi> or <gi>ofig</gi> elements. <parents>termEntry </parents> <children>descrip gram ofig otherform term </children> <elemdecl> <![ CDATA [ <!ELEMENT tig - O (term, gram*, descrip*, (otherform | ofig)*) > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST tig %a.global; type CDATA #IMPLIED > ]]> </attldecl> <xref type=div1 target=TEta> </tagdoc> <tagdoc usage=opt id="xptr"><gi>xptr</gi> <name>extended pointer</name> <desc>defines a pointer to another location in the current document or an external document. </desc> <attlist> <attdef usage=req><attname>doc</attname> <desc>specifies the document within which the required location is to be found.</desc> <datatype>ENTITY</datatype> <valdesc>The name of a system entity identifying the document within which the target of this pointer is to be found, by default the current document. </valdesc> <default>#IMPLIED</default> </attdef> <attdef usage=opt><attname>from</attname> <desc>specifies the start of the destination of the pointer as an expression in the TEI extended pointer notation. </desc> <datatype>CDATA</datatype> <valdesc>The value specified must be a valid expression in the TEI extended pointer notation defined in section <xref target=SAxr>. </valdesc> <default>#IMPLIED</default> <remarks><p>If no value is specified, the target is the whole of the document identified by the <att>doc</att> attribute.</remarks> </attdef> <attdef usage=opt><attname>to</attname> <desc>specifies the endpoint of the destination of the pointer as an expression in the TEI extended pointer notation. </desc> <datatype>CDATA</datatype> <valdesc>The value specified must be a valid expression in the TEI extended pointer notation defined in section <xref target=SAxr>. </valdesc> <default>#IMPLIED</default> <remarks><p>This attribute may only be supplied if the <att>to</att> attribute is also supplied, in which case the destination is defined to extend from the beginning of the location specified by the <att>from</att> attribute, up to the end of the location specified by the <att>to</> attribute. It is an error for <att>to</> to specify a location whose end precedes the beginning of the location specified by <att>from</>; it is not an error for the scopes to overlap. </remarks> </attdef> </attlist> <exemplum><eg><![ CDATA [ ]]> </eg></exemplum> <remarks></remarks> <part>additional tag set for analysis and interpretation</part> <classes names=loc> <files names=""> <parents> </parents> <children>EMPTY </children> <elemdecl> <![ CDATA [ <!ELEMENT xptr - o EMPTY > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST xptr %a.global; %a.loc; doc ENTITY #IMPLIED from CDATA #IMPLIED to CDATA #IMPLIED > ]]> </attldecl> <xref target=SAxr> </tagdoc> <tagdoc usage=opt id="xref"><gi>xref</gi> <name>extended reference</name> <desc>defines a reference to another location in the current document, or an external document, using an extended pointer notation, possibly modified by additional text or comment.</desc> <attlist> <attdef usage=req><attname>doc</attname> <desc>specifies the document within which the required location is to be found.</desc> <datatype>ENTITY</datatype> <valdesc>The name of a system entity identifying the document within which the target of this pointer is to be found, by default the current document. </valdesc> <default>#IMPLIED</default> </attdef> <attdef usage=opt><attname>from</attname> <desc>specifies the start of the destination of the pointer as an expression in the TEI extended pointer notation. </desc> <datatype>CDATA</datatype> <valdesc>The value specified must be a valid expression in the TEI extended pointer notation defined in section <xref target=SAxr>. </valdesc> <default>#IMPLIED</default> <remarks><p>If no value is specified, the target is the whole of the document identified by the <att>doc</att> attribute.</remarks> </attdef> <attdef usage=opt><attname>to</attname> <desc>specifies the endpoint of the destination of the pointer as an expression in the TEI extended pointer notation. </desc> <datatype>CDATA</datatype> <valdesc>The value specified must be a valid expression in the TEI extended pointer notation defined in section <xref target=SAxr>. </valdesc> <default>#IMPLIED</default> <remarks><p>This attribute may only be supplied if the <att>to</att> attribute is also supplied, in which case the destination is defined to extend from the beginning of the location specified by the <att>from</att> attribute, up to the end of the location specified by the <att>to</> attribute. It is an error for <att>to</> to specify a location whose end precedes the beginning of the location specified by <att>from</>; it is not an error for the scopes to overlap. </remarks> </attdef> </attlist> <exemplum><eg><![ CDATA [ ]]> </eg></exemplum> <remarks></remarks> <part>additional tag set for analysis and interpretation</part> <classes names=loc> <files names=""> <parents> </parents> <children>EMPTY </children> <elemdecl> <![ CDATA [ <!ELEMENT xref - o EMPTY > ]]> </elemdecl> <attldecl> <![ CDATA [ <!ATTLIST xref %a.global; %a.loc; doc ENTITY #IMPLIED from CDATA #IMPLIED to CDATA #IMPLIED > ]]> </attldecl> <xref target=SAxr> </tagdoc>