<admin>

| ## Text Encoding Initiative
### The XML Version of the TEI Guidelines # <admin>

`<admin>` | (administrative information) within a `<termEntry>` element, contains administrative information pertaining to data management and documentation of the entry.
Attributes | (In addition to global attributes and those inherited from terminologyMisc)
`type` | identifies the administrative event or information using some typology, preferably the dictionary of data element types specified in ISO WD 12 620.
| Datatype: CDATA
| Suggested values include:
responsibility | The 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.
| Default: #IMPLIED
| Example:
Note | 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.
| Datatype: %ISO-date;
| Values: a date in ISO standard form (yyyy-mm-dd).
| Default: #IMPLIED
| Example:
Note | 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.
| Datatype: CDATA
| Values: any string of characters (usually the acronym of the agency or the initials of an individual).
| Default: #IMPLIED
| Example:
Note | Some terminological database systems treat responsibility as a cross reference to a personnel entry.

Example

    <admin depend="te84.11" type="domain"
    resp="ISO/TC 61, Plastics">plastics</admin>
    <admin depend="te84.11" type="responsibility" resp="ISO/TC 61, Plastics"/>
    <admin depend="te84.11" type="created" date="1991-10-23" resp="SEW"/>
    <admin depend="te84.11" type="updated" date="1992-12-15" resp="MSM"/>

Note

Administrative data takes widely varying forms in different terminological databases; the `type` attribute should be used to indicate the particular class of administrative information involved. For domain or other similar information, the `<admin>` element should be used to provide the domain information as the content of the element.

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` The `<admin>` element should also be used to record dates of major changes to the term entry, if these are to be recorded.

Module Declared in file teite2n; Declared in file teite2f; Base tag sets for Terminological Data: enabled by TEI.terminology
Class terminologyMisc
Data Description May contain character data and phrase-level elements.
May contain #PCDATA abbr add addSpan address alt altGrp anchor app bibl biblFull biblStruct c caesura camera caption castList cb certainty cit cl corr damage date dateRange dateStruct del delSpan distinct emph expan fLib figure foreign formula fs fsLib fvLib fw gap geogName gloss handShift hi index interp interpGrp join joinGrp label lang lb link linkGrp list listBibl m measure mentioned milestone move name note num oRef oVar orgName orig pRef pVar pb persName phr placeName ptr q quote ref reg respons restore rs s seg sic soCalled sound space span spanGrp stage supplied table tech term text time timeRange timeStruct timeline title unclear view w witDetail xptr xref
May occur within ofig termEntry tig
Declaration

    <!ELEMENT admin %om.RO;  %paraContent;>
    <!ATTLIST admin
          %a.global;
          type CDATA #IMPLIED
          date %ISO-date; #IMPLIED
          resp CDATA #IMPLIED>

See further 13.4.2 DTD Fragment for Flat Style; 13.4.1 DTD Fragment for Nested Style; 13.2 Tags for Terminological Data

Up: 35 Elements