Permissible Instances: Terminology management functions (A.10.02) are directly linked to the following terminology management transactions:
a. origination
Description: A database transaction involving the creation of a term entry.
b. input
Description: A database transaction involving the recording of a term entry or related information into a database. Note: Input can be identical to origination, but does not necessarily have to be: one individual can have collected information, while another inputs it into a database.c. modification
Description: A database transaction involving the updating of a term entry.
d. check Description: A database transaction involving the checking of a term entry. e. approval Description: A database transaction involving the definitive approval of a term entry. f. withdrawal Description: A database transaction involving the removal of a term entry. g. standardization Description: A database transaction involving the standardization of a term entry. h. exportation Description: A database event involving the exportation of a term entry to an outside database or to an interchange format. i. importation Description: A database event involving the importation of a term entry from an outside database. j. userAccess Description:IATE dataCategory yet to be defined.DXLT Representation
<adminNote='transactionType'>picklist value<adminNote>
Picklist:origination, input, modification, check, approval, withdrawl, standardization, exportation, importation, responsiblity
Note 2: The content of the date is restricted to ISO data(/time) format.
DXLT Representation:
<transacGrp> <transac type="modification"> marketing department requested change from gizmo to thinger</transac> <date>1999-11-12</date> </transacGrp>
Description: The date on which an element (field, record, entry, etc.) is created.
<transacGrp> <transac type="input"></transac> <date>1999-11-12</date> </transacGrp>DXLT Example: <date>1996-05-24T16:12:02</date>
<transacGrp> <transac type="orgination"></transac> <date>1999-11-12</date> </transacGrp>
Description: The date when a field, record, etc. is edited or otherwise modified.
DXLT Example: <<transacGrp> <transac type="modification"></transac> <date>1999-11-12</date> </transacGrp>
<transacGrp><transac type="check"></transac> <date>1999-11-12</date> </transacGrp>
<transacGrp><transac type="check"></transac> <date>1999-11-12</date> </transacGrp>
<transacGrp><transac type="check"></transac> <date>1999-11-12</date> </transacGrp>
<transacGrp><transac type="standardization"></transac> <date>1999-11-12</date> </transacGrp>
<transacGrp><transac type="exportation"></transac> <date>1999-11-12</date> </transacGrp>
<transacGrp><transac type="exportation"></transac> <date>1999-11-12</date> </transacGrp>
Note:
Note: Types of responsibility can include:Description: An identifier assigned to the specific individual responsible for administering a subset of terminological records.
DXLT Example: <admin type="responsibility" target="respPerson">subset owner<admin>Description:log the number of times that users access a terminological entry.
Note 2: Items identified by subset owner in effect comprise another type of subset, but the inclusion of a separate data category for this distinction as a subset identifier would be redundant. Instances in this subset group are combinable and mutually independent, i.e., the same entry can require the inclusion of multiple subset identifiers.
DXLT Representation: <admin type="data category name" >...</admin>Description: An identifier assigned to a term or terminological record indicating its association with a specific department, division, or other unit of an enterprise.
DXLT Representation: <admin type="businessUnitSubset" >...</admin>Description: An in-house security classification of a term.
Note: A security classification can frequently be assigned to a critical term during the product development phase when secrecy is of particular importance. Security qualification can occur in conjunction with date restriction, authorization code, or any of the other subset identifiers. Permissible Instances: Types of security subset qualifiers can include:Description: Name assigned to a system user that authorizes access to a database or data entry.
Note: Passwords are unique and typically user-selected.
Description: Title assigned to a system user in a responsibility entry reflecting his or her functions with respect to database creation, maintenance, or use.
Note: Typical job titles include such items as translator, terminologist, superuser and guest.picklist values: public, confidential
10.06 administrative term qualifiers
Note 2: See DTD for where allowed.
10.06.02 sort key
Admitted name: sorting form Description: A character string used for comparisons in sorting and merging operations. Note: A terminological sort key can allow alphabetic or systematic access. Example: 2,2-Dihydropyran is sorted according to "Dihydropyran", not according to "2,2". a'-Dimethyl-g-pyrone is sorted according to "Dimethyl", not according to "a". DXLT representation Representation: <admin type="sortKey">...</admin>, where the content is unrestricted.
Description: A symbol used to designate the name of a language.
Note: The symbols specified in ISO 639 should be used. Ideally, it should be possible to include language information wherever necessary in terminology collections. Example: 2-letter symbols for common languages cited in this International Standard include: en = English fr = French (français) ru = Russian (russki) de = German (Deutsch) es = Spanish (español)Description: Markup used to identify a word, phrase, or extended text as belonging to some language other than that of the surrounding text.
DXLT representation Representation: <foreign lang="fr">Salut</foreign>DXLT representation Example: In the German text of ISO 9000-1, some terms are retained in English:
<descrip type=definition lang=de>Vertragliche Anwendung von Beurteilungs- und Genehmigungs- oder Registrierungs-Systemen <foreign>(second party)</foreign></descrip>related name: alphabetization sequence
Description: A code indicating the alphabetization convention used for sorting a file. Permissible Instances: Some types of collating sequence include: a. continuous alphabetical sequence Admitted name: letter by letter alphabetization Description: Arrangement of entries according to the [alphabetical] filing value of the entry terms taken letter by letter without reference to blanks, hyphens, apostrophes, parentheses, or the like. b. discontinuous alphabetical sequence Admitted name: word by word alphabetization Description: Arrangement of entries according to the [alphabetical] filing value of the entry terms taken word by word, resulting in the clustering of syntagmatic groups. c. special alphabetical sequence Description: Alphabetization according to conventions that pertain to a specific language or discipline. Example: Sequences for the Cyrillic alphabet or special Roman character sequences, such as Þ in Icelandic; sequences that account for special applications such as those described in 10.06.02. d. systematic sequence Description: Arrangement of entries in order based on a system of concepts. e. mixed sequence Description: Alphabetical arrangement of entries within systematically arranged sections. f. ASCII sequence Description: Arrangement of entries based on standard ASCII order.DXLT example: <admin type="collocatingSequence" target="colSeqDescrip id ref"></admin>
Description: A category with which an entry in a terminological file is associated.
Note 1: In cases where several physical records are linked to form a virtual entry, all entry types can take the form of record types. Permissible Instances: Entry types can include: a. terminological entry Admitted name: term entry Description: A data entry that lists the terms associated with a given concept in a specifically defined subject field, together with other related information. b. concept entry Description: A terminological entry identified by a concept identifier that defines a specific concept and lists the terms associated with that concept. Note: A typical concept entry can consist of or be introduced by a definition instead of by a term. c. lexicographical entry Description: A data entry that provides all the meanings associated with a given lexeme (head word). Note: Lexicographical entries are not usually included in strict terminological files, but exceptions can occur, for instance in the case of student working files or in working entries during exploratory terminology research. It has also been theoretically proposed to include both lexicographical and terminological entries in the same file. Such entries should be clearly marked to avoid problems during data interchange. d. phraseological entry Description: A terminological entry that provides definitive and descriptive information pertinent to a phraseological or collocational unit. e. collocation entry Description: An entry treating a collocation (see A.2.1.18.1). f. set phrase entry Description: An entry treating a set phrase (see A.2.1.18.2). g. standard-text entry Description: An entry that provides information on a standard text (see A.2.1.19). h. cross-reference entry Description: An entry whose sole content consists of cross-reference to another entry in a database. i. responsibility entry description: An entry containing information on an individual responsible for functions associated with a terminological element. Note 2: See also bibliographic entry, Annex B, B.2.Description: A code indicating the level of completeness and accuracy of an element (field, record, entry) within a terminological collection.
Note: Working status levels include: a. starter element Description: A truncated or incomplete initial working element. Note: A starter record or entry, for instance, can consist of nothing but a term and an empty template or form, or in some cases, a definition or foreign equivalent, but no source-language term. b. working element Description: A terminological element that is substantially complete, but that has not yet been approved by the terminologist responsible for the element. c. consolidated element Admitted name: definitive element Description: A completed terminological element that has received final approval (sign-off) by the responsible terminologist. d. archive element Description: A terminological element that has been removed from active use in a database, but is archived for the purpose of retaining database history. e. imported element Description: A terminological element that originated as the result of data exchange with another database. f. exported element Description: An element that has been exported to another database, databases or to an interchange format.Description : A database or format to which data are exported.
Description : A database or format from which data are imported.
Description: A code used to identify a terminological data record (concept record or concept entry) in order to link physical elements to form a virtual concept entry.
Example: If this data element specification were treated as a terminological entry, the position number A.10.14 could be used as a concept identifier. Note: A concept identifier is used in cases where several records can pertain to the same concept, in which instance the record identifiers for the various records will differ, necessitating the inclusion of a linking identifier in order to maintain the integrity of the overall concept entry. Concept identifiers are also essential in systematically organized terminologies, where they are used as cross-reference identifiers from alphabetical lists. They are also listed separately in environments where a stable entry identifier is needed, but the virtual entry identifier can be subject to change as a result of database management considerations.Description: A code that serves as the unique identifier of a terminological entry.
Description: A code that serves as the unique identifier of a terminological record.
Note: A separate record identifier can be necessary in cases where several physical records are linked to form a virtual entry.Description: A code that serves as the unique identifier of a file in a terminology database management system.
Note: File identifiers become valuable when data from several files are merged or when aggregate files are split into subsets during data exportation and importation.Description: A pointer field or record used in a data collection to direct the user to another related location, e.g., another record.
Note: 10.18 can only be used when it stands alone and is not part of a datcat pair.DXLT representation Representation for A.10.18: <ref type=crossReference target=Z>...</ref> gt;, where Z is the id of a termEntry or smaller element, and the content (if any) identifies a section of the reference.
or <xref type='xCrossReference' target='URI'>display-text</xref>
Description: A pointer field used in a terminology collection as a direction from one location that does not contain information to the location(s) where information can be found.
Example: With respect to the thesaurus example in Annex C, Figure C.7, an entry in a companion terminology collection might contain the inverted term "noise, engine", which would be followed by a "see" reference pointing to a primary record for "engine noise".Description: A pointer field used in a terminology collection as a direction from one location that contains information to one or more other locations where related information will be found.
Note: "See also" cross references can be directed to any entry, record or data element in the terminology collection.Description: A multiword string that has been rearranged to create a new entry so that a desired keyword appearing at the end of the string appears first for the purpose of alphabetization.
Note: An inverted term will generally be used together with a "see" cross-reference. example: term: bovine spongiform encephalopathy inverted term: encephalopathy, bovine spongiformDescription: A term whose concept constitutes the opposite of the concept represented by a second term.
Example: GO - NOGO (gauges); in tolerance - out of tolerance Note: Although few terminology databases would document finer distinctions, antonyms can be further categorized as: complements-terms whose concept constitutes the reciprocal value of the concept represented by a second term, whereby the sum of the complementary concepts constitute a kind of whole; example: yin/yang; drag coefficient/free-running characteristic contrasts-terms whose concept exhibits marked difference from or opposition to the concept represented by a second term; example: red : green; black : whiteExample 2: Wüster, Eugen. 1968. The Machine Tool. London: Technical Press.
DXLT Example: <admin type="source"></admin>
Admitted Name 1: bibliographic source identifier
Admitted Name 2: terminological source identifier Description: The code assigned to a document in a terminological collection and used as both the identifier for a bibliographic entry and as a pointer in individual term entries to reference the bibliographic entry identified with this code. DXLT representation Representation: <admin type= "sourceIdentifier" target= "bibl">...</admin>full form: uniform resource locator
Description: The unique address for a page on the World Wide Web.
Example: http://www.ttt.org Note: The "http://" prefix is frequently dropped because most browsers will add it automatically. DXLT representation Representation:<xref type='xCrossReference' target='URI'>display-text</xref>full form: Formal Public Identifier
Description: The unique identifier for a representative of a given document in the World Wide Web environment. Example: "ISO 12200:1997//DTD for MARTIF (framework) //EN" Note: The FPI is analogous to the ISBN for books-there can be many identical copies with the same ISBN or FPI. The FPI in the above example uniquely identifies a document as being a copy of the MARTIF DTD. DXLT representation Representation :<xref type='xCrossReference' target='URI'>display-text</xref>.Admitted Name 1: expert
Admitted Name 2: specialist Description: An individual treated as a source of information for the purpose of bibliographic documentation.Description: An institution (i.e., company, government agency, etc.) treated as a source of information for the purpose of bibliographic documentation.
Description:Description pending
Description:Description pending
Description: Description pending