10.1 terminology management transactions - disallowed (reason B) - use A.10.2.* instead.
10.2 terminology management fuctions
 10.2.1 date
10.2.1.1 origination date
10.2.1.2 input date
10.2.1.3 modification date
10.2.1.4 check date
10.2.1.5 approval date
10.2.1.6 withdrawal date
10.2.1.7 standardization date
10.2.1.8 exportation date
10.2.1.9 importation date
10.2.2
responsibility
10.2.2.1 originator
10.2.2.2 inputter
10.2.2.3 updater
10.2.2.4 checker
10.2.2.5 approver
10.2.2.6 user
10.2.2.7 withdrawer
10.2.2.8 exporter
10.2.2.9 importer
10.2.2.10 subset owner
10.3 subset identifier
10.3.1 customer subset
10.3.2 initial customer subset
10.3.3 project subset
10.3.4 initial project subset
10.3.5 product subset
10.3.6 application subset
10.3.7 environment subset
10.3.8
business unit subset
10.3.9 security subset
10.4 authorization - disallowed
10.5 user suggestion
10.6 administrative term qualifiers
10.6.1 entailed term
10.6.2 sort key
10.6.3 search term
10.7 language symbol - not a datcat -- LANG attribute
10.8 foreign text
10.9 collocating sequence - not a datcat -- refObjectList give collating sequences for particular languages.
10.10 entry type - disallowed, but phraseological units can be marked with termType.
10.11 element working status - disallowed
10.12 target database - disallowed
10.13 entry source - disallowed
10.14 concept indentifier - not a datcat -- use id on <conceptEntry>
10.15 entry identifier - not a datcat -- use id on <conceptEntry>
10.16 record indentifier - not a datcat -- use id on <conceptEntry>
10.17 file identifier - not a datcat -- see document header
10.18 cross-reference
10.18.1 see - disallowed
10.18.2 see also - disallowed
10.18.3 inverted term - disallowed
10.18.4 permuted term - disallowed
10.18.5 homograph
10.18.6 antonym
10.19 source - disallowed: use A.10.20 - distinction between published document and person is made by refObject type pointed to 10.20
10.20 source identifier
10.21 namespace identifier
10.21.1 URL
10.21.2 FPI
10.22 originating entity
10.22.1 originating person - disallowed: use A.10.20
10.22.2 originating institution
10.22.3 originating institution - disallowed (termbase specific)
10.1 terminology management transactions
Description: One of the steps involved in the creation, approval, and use of a terminology entry.
Permissible Instances: Terminology management functions (A.10.2) 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.
10.2 terminology management functions
Description: Data categories pertaining to the management of terminology within the activities of a working group.
Note: Types of terminology management functions can include:
10.2.1 date
Description: The point of time at which a transaction or event takes place.
Note 1: Types of date can include:
Blind MARTIF Representation: <date type=X>...</date>, where X is one of the date types listed above (10.2.1.*).
Note 2: The content of the date is restricted to ISO data(/time) format.
Blind MARTIF Example: <date type=origination>1996-05-24T16:12:02</date>
10.2.1.1 origination date
Description: The date on which an element (field, record, entry, etc.) is created.
Blind MARTIF Example: <date type=origination>1996-05-24T16:12:02</date>
10.2.1.2 input date
Description: The date on which an element (field, record, entry, etc.) is input into a data collection.
Note: "Origination date" and "input date", as well as their respective transactions, can be identical, in which case the latter may not be necessary.
Blind MARTIF Example: <date type=input>1996-05-24T16:12:02</date>
10.2.1.3 modification date
Description: The date when a field, record, etc. is edited or otherwise modified.
Blind MARTIF Example: <date type=modification>1996-05-24T16:12:02</date>
10.2.1.4 check date
Description: The date when a field, record, etc. is checked.
Blind MARTIF Example: <date type=check>1996-05-24T16:12:02</date>
10.2.1.5 approval date
Description: The date when a record, entry, etc. is approved or declared a consolidated item.
Blind MARTIF Example: <date type=approval>1996-05-24T16:12:02</date>
10.2.1.6 withdrawal date
Description: The date when a record or entry is removed from an active data collection and placed in an archive file.
Blind MARTIF Example: <date type=withdrawal>1996-05-24T16:12:02</date>
10.2.1.7 standardization date
Description: The date when a term is introduced as a normative term based on final approval by an authoritative body.
Blind MARTIF Example: <date type=standardization>1996-05-24T16:12:02</date>
10.2.1.8 exportation date
Description: The date when a terminological entry is exported from a database to another database or to an interchange format.
Blind MARTIF Example: <date type=exportation>1996-05-24T16:12:02</date>
10.2.1.9 importation date
Description: The date when a terminological entry is imported into a database.
Blind MARTIF Example: <date type=importation>1996-05-24T16:12:02</date>
10.2.2 responsibility
Description: An identifier assigned to the individual associated with a terminology management transaction.
Note: Types of responsibility can include:
Blind MARTIF Representation: <ptr type=X target=YRes/>, where X is a responsible party type from the list above (10.2.2.*) and where YRes is the refid of a <refObject type=responsibleParty>
10.2.2.1 originator
Description: An identifier assigned to the individual creating a field, record, etc.
Blind MARTIF Example: <ptr type=originator target='hames'/>
10.2.2.2 inputter
Description: An identifier assigned to the individual inputting a field, or record, etc. if this varies from the originator.
Blind MARTIF Example: <ptr type=inputter target='hames'/>
10.2.2.3 updater
Description: An identifier assigned to the individual editing or otherwise modifying a field or record.
Blind MARTIF Example: <ptr type=updater target='hames'/>
10.2.2.4 checker
Description: An identifier assigned to the individual checking a field or record.
Blind MARTIF Example: <ptr type=checker target='hames'/>
10.2.2.5 approver
Description: An identifier assigned to the individual approving a consolidated or definitive field or record.
Blind MARTIF Example: <ptr type=approver target='hames'/>
10.2.2.6 user
Description: An identifier assigned to the specific user-audience of a terminological entry.
Blind MARTIF Example: <ptr type=user target='hames'/>
10.2.2.7 withdrawer
Description: An identifier assigned to the individual responsible for withdrawing a terminological entry from the main terminology collection.
Blind MARTIF Example: <ptr type=withdrawer target='hames'/>
10.2.2.8 exporter
Description: An identifier assigned to the individual responsible for exporting a terminological entry from a terminology database.
Blind MARTIF Example: <ptr type=exporter target='hames'/>
10.2.2.9 importer
Description: An identifier assigned to the individual responsible for importing a terminological entry into a terminology database.
Blind MARTIF Example: <ptr type=importer target='hames'/>
10.2.2.10 subset owner
Description: An identifier assigned to the specific individual responsible for administering a subset of terminological records.
Blind MARTIF Example: <ptr type=subsetOwner target='hames'/>
10.3 subset identifier
Description: Any sub-group of terms within a database identified as having a property in common with other members of the sub-group, such as being administered by a single user or used for a specified application.
Note 1: Types of subsets can include:
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.
Blind MARTIF Representation: <ref type=X target=YSub>...</ref>, where X is a subset of 10.3.* (listed above) and YSub is the refid of a <refObjec type=subset> that lists the permissable values of the members of the subset type and where the content is the particular subset name.
10.3.1 customer subset
Description: An identifier assigned to a terminological record indicating that it is associated with a specific customer.
Blind MARTIF Example: <ref type=customerSubset target=subset>...</ref>
10.3.2 initial customer subset
Description: An identifier assigned to a terminological record indicating that it is associated with a specific initial customer.
Blind MARTIF Example: <ref type=initialCustomerSubset target=subset>...</ref>
10.3.3 project subset
Description: An identifier assigned to a specific project indicating that it is associated with a term, record or entry.
Blind MARTIF Example: <ref type=projectSubset target=subset>...</ref>
10.3.4 initial project subset
Description: An identifier assigned to a specific initial project with which a term, record or entry is associated.
Blind MARTIF Example: <ref type=initialProjectSubset target=subset>...</ref>
10.3.5 product subset
Description: An identifier assigned to a product to which a term is related.
Blind MARTIF Example: <ref type=productSubset target=subset>...</ref>
10.3.6 application subset
Description: An identifier assigned to a terminology entry associated with a specific application.
Note: Originally intended for the identification of terms used in computer applications, this data category can potentially be used to identify terms used in other types of applications as well.
Blind MARTIF Example: <ref type=applicationSubset target=subset>...</ref>
10.3.7 environment subset
Description: An identifier assigned to a terminology entry indicating its association with a specific computer environment.
Blind MARTIF Example: <ref type=environmentSubset target=subset>...</ref>
10.3.8 business unit subset
Description: An identifier assigned to a term or terminological record indicating its association with a specific department, division, or other unit of an enterprise.
Blind MARTIF Example: <ref type=businessUnitSubset target=subset>...</ref>
10.3.9 security subset
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:
- public
Description: Security qualifier indicating that all users in a system can access an entry.
- confidential
Description: Security qualifier indicating that only authorized users can access an entry.
Blind MARTIF Example: <admin type=securitySubset >public or confidential</admin>
10.4 authorization information
10.4.1 authorization function
Description: An identifier assigned to a system user designating the functions that user shall perform in the system or the range of data to which the user shall have access.
Note: Typical functions include read, write, and delete capabilities.
10.4.2 authorization identifier
Description: An identifier assigned to a system user designating that individuals log-in name.
Note: Typical identifiers are real names or aliases.
10.4.3 authorization password
Description: Name assigned to a system user that authorizes access to a database or data entry.
Note: Passwords are unique and typically user-selected.
10.4.4 job title
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.
10.5 user suggestion
Description: A suggested modification of the term, record or entry.
Note: This data category is used in group terminology management situations where some members of the group are not authorized to, or choose not to, change term entries, but can document suggestions for changes to be implemented by someone else. User suggestion can be associated with some sort of user identifier, e.g., a job title, authorization function, or responsibility identifier.
Blind MARTIF Representation: <admin type=userSuggestion>...</admin>
10.6 administrative term qualifiers
10.6.1 entailed term
Description: A term that is defined in another terminological entry in the same lexicon, glossary, terminology or vocabulary.
Note 1: Entailed terms can be any term used in a definition, either as a genus or a differentia, or any term used in a note, cross-reference or other textual element.
Blind MARTIF Representation: <term><hi type=entailedTerm target=Z>...</hi></term>, where Z is a refid of a termEntry containing the entailed term.
Note 2: See DTD for where allowed.
10.6.2 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".
Blind MARTIF Representation: <admin type=sortKey>...</admin>, where the content is unrestricted.
10.6.3 search term
Description: A term entered in a term entry for purposes of retrieval.
Example: Many secondary index keys generated in terminological databases function as search terms, e.g., in a directional multilingual entry, target language equivalents can be identified as secondary keys and used as search terms.
Blind MARTIF Representation: <admin type=searchTerm>...</admin>, where the content is unrestricted.
10.7 language symbol
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)
10.8 foreign text
Description: Markup used to identify a word, phrase, or extended text as belonging to some language other than that of the surrounding text.
Blind MARTIF Representation: <foreign>...</foreign>
Blind MARTIF 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>
10.9 collating sequence
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.6.2.
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.
10.10 entry type
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.
10.11 element working status
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.
10.12 target database
Description: A database or format to which data are exported.
10.13 entry source
Description: A database or format from which data are imported.
10.14 concept identifier
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.
10.15 entry identifier
Description: A code that serves as the unique identifier of a terminological entry.
10.16 record identifier
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.
10.17 file identifier
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.
10.18 cross-reference
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.
Blind MARTIF Representation for A.10.18: <ref type=crossReference target=Z>...</ref> or <ptr type=crossReference target=Z/>, where Z is the id of a termEntry or smaller element, and the content (if any) identifies a section of the reference.
10.18.1 see
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".
10.18.2 see also
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.
10.18.3 inverted term
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 spongiform
10.18.4 permuted term
Description: A multiword string that has been rearranged so that desired keywords embedded in the term appear first for the purpose of alphabetization.
Note: A permuted term will generally be used together with a "see" cross-reference.
Example: term: bovine spongiform encephalopathy
permuted term: spongiform, bovine ~ encephalopathy
10.18.5 homograph
Description: A word that is spelled like another, but that has a different pronunciation, meaning, and origin.
Example: lead (guide), lead (metal); wind (airflow), wind (turn)
Note: As opposed to polysemic terms, which involve the same words being applied to different concepts, homographs are words that are derived from different etymological origins. Homograph is most likely to occur as a pointer to the entry for the other instance or instances where the word is used in association with a different concept.
A homograph number is a sequential number used to distinguish homographs. Although many print dictionaries use superscripts for homograph numbers, this convention has been infrequently facilitated in traditional databases. It is easily achieved in Graphical User Interfaces (GUI applications).
Blind MARTIF Representation for A.10.18.*: <ref type=X target=Z>...</ref>, where X is homograph or antonym and the content is the actual homograph or antonym and Z is the refid of the termEntry containing the term.
10.18.6 antonym
Description: 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 : white
Blind MARTIF Representation for A.10.18.*: <ref type=X target=Z>...</ref>, where X is homograph or antonym and the content is the actual homograph or antonym and Z is the refid of the termEntry containing the term.
10.19 source
Description: A complete citation of the bibliographic information pertaining to a document or other resource.
Note: For instance, a standard number would constitute a complete bibliographic citation, or the complete documentation might be included in a term entry. In electronic database management environments, inclusion of each entire bibliographical source in each terminological entry can lead to the presence of redundant data within a collection.
Example 1: ISO 10241:1992 International Terminology Standards - Preparation and layout
Example 2: Wüster, Eugen. 1968. The Machine Tool. London: Technical Press.
10.20 source identifier
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.
Blind MARTIF Representation: <ref type=sourceIdentifier target=YSRC>...</ref> or <ptr type=sourceIdentifier target=YSRC/>, where YSRC is the refid of a <refObject type=bibl> and the content (if any) identifies a section of the reference.
10.21 namespace identifier
10.21.1 URL
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.
Blind MARTIF Representation: <ptr type=URL target=YURL/>, where YURL is the refid of a <refObject type=URL> that contains the URL.
10.21.2 FPI
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.
Blind MARTIF Representation: <ptr type=FPI target=YFPI/>, where YFPI is the refid of a <refObject type=FPI> that contains the FPI.
10.22 originating entity
Description: A person, an institution, a company, etc., that serves as the origin of information in lieu of a document.
Note: These data categories can also be used to identify the origin of a new term in a language-planning or standardization environment as described in A.2.4.4.
10.22.1 originating person
Admitted Name 1: expert
Admitted Name 2: specialist
Description: An individual treated as a source of information for the purpose of bibliographic documentation.
10.22.2 originating institution
Description: An institution (i.e., company, government agency, etc.) treated as a source of information for the purpose of bibliographic documentation.
Blind MARTIF Representation: <ptr type=originatingInstitution target=YRes/>, where YRes is the refid of a <refObject type=responsibleParty>.
10.22.3 originating database
Description: A database treated as a document for the purpose of bibliographic documentation.
|
![[CLS Framework]](images/clshead.gif)