`<admin>` | (administrative information) within a `<termEntry>` element, contains administrative information pertaining to data management and documentation of the entry.

Attributes:

`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

Legal values:

`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: CDATA
| Values: a date in ISO standard form (yyyy-mm-dd).
| Default: %ISO-date

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

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

    <admin depend=te84.11
           type='domain'
           resp='ISO/TC 61, Plastics'>plastics</admin>

Example

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` :

    <admin depend=te84.11
           type='responsibility'
           resp='ISO/TC 61, Plastics'></admin>

Example

    <admin depend=te84.11
           type='created'
           date='1991-10-23'
           resp='SEW'></admin>
    <admin depend=te84.11
           type='updated'
           date='1992-12-15'
           resp='MSM'></admin>

Note

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.

Tagsetbase tag set for terminological data
ClassterminologyMisc
Filename`teite2n teite2f`
Content: May contain character data and phrase-level elements.
Parentsofig termEntry tig
Children#PCDATA abbr add address app att bibl biblFull biblStruct c caesura camera caption castList cit cl corr damage date dateRange dateStruct del distinct emph expan figure foreign formula fw geogName gi gloss handShift hi label lang link list listBibl m measure mentioned move name note num oRef oVar orgName orig pRef pVar persName phr placeName ptr q quote ref reg restore rs s seg sic soCalled sound space stage supplied table tag tech term text time timeRange timeStruct title unclear val view w witDetail xptr xref
Declaration

    <!ELEMENT admin         - O  (%paraContent;)                    >
    <!ATTLIST admin              %a.global
              type               CDATA               #IMPLIED
              date               CDATA               %ISO-date

              resp               CDATA               #IMPLIED       >

See 13.4.2 ; 13.4.1 ; 13.2

Back to index