1、 ! ! “# $% 3( )89$9:%$9+$) 6- ( *)89$9:%$, 4 )89$9:%$9+$= however, doublettes are determined based on identical concepts, not on identical terms. Doublettes should not be confused with homographs. 3.1.10 concept system set of concepts structured according to the relationships among them ISO 1087-1:2
2、000, 3.2.11 3.1.11 concept diagram graphic representation of a concept system (3.1.10) ISO 1087-1:2000, 3.2.12 N1) National footnote: In the source text of ISO 26162, there is a note referring to a term in the source language. This note has not been translated into German. N1)DIN ISO 26162:2016-12 8
3、 3.1.12 legacy data terminological data that are available in an existing file or database, and that are considered for importation into a TMS (3.1.2) NOTE Legacy data may be in the form of previously used databases, word-processing files, comma-delimited text files, SGML, HTML, or XML files, and th
4、e like. Conversion of such data to a format that will be compatible with a new TMS can pose serious challenges. 3.1.13 term word, or several words, that denote a concept EXAMPLES “Olympics” and “special Olympics” are two terms in the field of sports. NOTE 1 When the word or words can denote more tha
5、n one concept, each word/concept pair is a separate term. For example, “port” (shelter for boats) and “port” (computer connection point) are two different terms. NOTE 2 In terminology theory, terms denote concepts in specific subject fields, and words from the general lexicon are not considered to b
6、e terms. In a TDC, however, words from the general lexicon are sometimes recorded in terminological entries, where they are still referred to as “terms”. 3.2 Data categories 3.2.1 data category result of the specification of a data field ISO 1087-2:2000, 6.14 3.2.2 data element unit of data that, in
7、 a certain context, is considered indivisible ISO 1087-2:2000, 6.11 3.2.3 data granularity degree of precision of data NOTE For example, the set of individual data categories (3.2.1) /part of speech/, /grammatical gender/, and /grammatical number/ provides for greater data granularity than does the
8、single data category /grammar/. 3.2.4 data elementarity principle whereby a single data field shall contain only one item of information NOTE For example, including both a full form and an abbreviation in the same field would be a violation of the principle of data elementarity. 3.2.5 term autonomy
9、principle whereby all terms in a terminological entry (3.1.4) can be described by using the same set of data categories (3.2.1) 3.2.6 Data Category Registry DCR set of standardized data categories (3.2.1) to be used as a reference for the definition of linguistic annotation schemes or any other form
10、ats in the domain of language resources ISO 12620:2009, 3.2.1 DIN ISO 26162:2016-12 9 NOTE The ISO/TC 37 DCR contains data category specifications (3.2.7), which include historical, descriptive, and administrative information and other metadata. 3.2.7 data category specification set of attributes us
11、ed to fully describe a given data category (3.2.1) ISO 12620:2009, 3.2.2 NOTE The abbreviation DCS refers to Data Category Selection (3.2.8) . 3.2.8 Data Category Selection DCS set of data categories (3.2.1) selected from the Data Category Registry (3.2.6) ISO 12620:2009, 3.2.3 3.2.9 complex data ca
12、tegory data category (3.2.1) that has a conceptual domain (3.2.11) ISO 12620:2009, 3.1.7 3.2.10 open data category complex data category (3.2.9) whose conceptual domain (3.2.11) is not restricted to an enumerated set of values ISO 12620:2009, 3.1.8 3.2.11 conceptual domain set of valid value meaning
13、s (3.2.14) NOTE 1 Based on ISO/IEC 11179-1:2004, 3.3.6. NOTE 2 The value meanings in a conceptual domain may be enumerated, further specified by additional constraints or expressed via a description. For instance, the data category (3.2.1) /term/ is described by its definition and thus constrained f
14、rom properly containing, for example, contextual information or grammatical information, but it would be impossible to enumerate all values associated with this data category. 3.2.12 closed data category complex data category (3.2.9) whose conceptual domain (3.2.11) is restricted to a set of identif
15、ied simple data categories (3.2.13) ISO 12620:2009, 3.1.13 3.2.13 simple data category data category (3.2.1) with no conceptual domain (3.2.11) ISO 12620:2009, 3.1.12 3.2.14 value meaning meaning or semantic content of a value ISO/IEC 11179-1:2004, 3.3.39 N2) National footnote: In the source text of
16、 ISO 26162, there is a note referring to a term in the source language. This note has not been translated into German. N2)DIN ISO 26162:2016-12 10 NOTE ISO/TC 37 treats enumerated values as simple data categories, that is, as data categories in their own right. The meaning of a value is always viewe
17、d in the context of the overall value domain and the closed data category with which it is associated, and is not just a property of the domain value itself. 3.2.15 value domain set of permissible values (3.2.16) ISO/IEC 11179-1:2004, 3.3.38 3.2.16 permissible value expression of a value meaning (3.
18、2.14) allowed in a specific value domain (3.2.15) ISO/IEC 11179-1:2004, 3.3.28 3.2.17 thematic domain class of applications identified by the similarity of the data structures they need to manipulate ISO 12620:2009, 3.4.3 EXAMPLES Terminology, lexicography, morphosyntactic annotation. 3.2.18 themati
19、c domain profile profile representation within a data category specification (3.2.7) of the thematic domain (3.2.17) with which a data category (3.2.1) is associated ISO 12620:2009, 3.4.4 NOTE A data category may have several thematic domain profiles, indicating that it is used by several thematic d
20、omains. 3.3 Data modelling 3.3.1 data model graphical and/or lexical representation of data, specifying their properties, structure and inter-relationships ISO/IEC 11179-1:2004, 3.2.7 3.3.2 data modelling process of structuring and organizing data, typically for implementation in a database manageme
21、nt system 3.3.3 data modelling variance variation in the assignment of data categories (3.2.1) to data models as a result of differences in philosophy with respect to the ordering of information in the terminological entry (3.1.4) 3.3.4 metamodel data model (3.3.1) that specifies one or more other d
22、ata models ISO/IEC 11179-1:2004, 3.2.20 DIN ISO 26162:2016-12 11 3.3.5 metadata data that define and describe other data ISO/IEC 11179-1:2004, 3.2.16 3.3.6 global information GI technical and administrative information applying to a complete data collection ISO 16642:2003, 3.7 EXAMPLE Title of the d
23、ata collection, revision history. 3.3.7 complementary information CI information supplementary to that described in terminological entries (3.1.4) and shared across the terminological data collection (3.1.1) ISO 16642:2003, 3.1 EXAMPLE Domain hierarchies, institution descriptions and bibliographical
24、 references are typical examples of complementary information. 3.3.8 shared resource information object that can be accessed from any of the terminological or lexicographical entries in a terminological or lexicographical resource EXAMPLE Shared resources typically include bibliographical entries, r
25、esponsibility entries, namespace identifiers, frequently referenced textual material, geographical location lists, and external files, such as graphics or audio files. 3.3.9 language section LS part of a terminological entry (3.1.4) containing information related to one language ISO 16642:2003, 3.9
26、3.3.10 term section TS part of a language section (3.3.9) containing information about a term (3.1.13) ISO 16642:2003, 3.15 3.3.11 class object class UML description of a set of objects that share the same members 3.3.12 multiplicity number of instances of one class (3.3.11) linked to one instance o
27、f another class in a relationship set NOTE For instance, an origination date may be the same for many terminological entries, but one terminological entry can only have one origination date. DIN ISO 26162:2016-12 12 3.4 Applications 3.4.1 language planning deliberate efforts to influence human behav
28、iour with respect to the acquisition, structure, or functional allocation of language EXAMPLE Language planning can include the standardization of spelling and grammatical rules, the specification of official national languages, efforts to create viable neologisms designed to increase the capacity o
29、f a language as a vehicle for scientific and commercial communication, and measures designed to protect the language from foreign influences. 3.4.2 descriptive terminology approach for managing terminology that documents the way that terms (3.1.13) are used in contexts without indicating preferred u
30、sage 3.4.3 prescriptive terminology approach for managing terminology that indicates preferred usage 3.4.4 normative terminology approach for managing terminology that is used in standards work or governmental regulation 3.4.5 translation editor software that supports the process of creating and rev
31、ising translations 3.4.6 controlled authoring authoring that uses limited vocabulary and textual complexity to produce clear documents 3.4.7 localization l10n process of taking a product and making it linguistically and culturally appropriate to the target locale (country/region and language) where
32、it will be used and sold Localization Industry Standards Association 4 Terminology management system (TMS) 4.1 General description A TMS is a software tool specifically designed to collect, maintain, and access terminological data. It is used by translators, terminologists, technical writers, and va
33、rious other users. TMSs shall be based on the principles for terminology work set down in ISO 704, which means that the terminological resources that are created by using a TMS contain terminological entries designed to document concepts and all the terms (synonyms and equivalents in other languages
34、) that denote those concepts. TMSs are typically used to elaborate, maintain and disseminate TDCs in a variety of organizational environments, including national bodies, government agencies, interest groups, companies, and individuals. Depending on the organizational framework, the TMS will need to
35、support a variety of necessary features, different tasks and potential users. When planning a software application for terminology management, it is important to consider the different possible types or categories of TMS. DIN ISO 26162:2016-12 13 4.2 Purchased or self-programmed TMS There is a varie
36、ty of terminology management tools on the software market; most of the software is commercial, but an increasing array of freeware or open-source software is available for terminology management. If the organizational, functional and methodological needs of the respective application environment are
37、 met by the system, it can be used off the shelf. However, in many cases, a customer-specific adaptation and adjustment is necessary. If the commercial software cannot be tailored to specific, identified needs, a TMS will have to be developed in-house. Costs, maintenance, support and interoperabilit
38、y are important parameters to be considered when deciding between buying or leasing a TMS, and developing one in-house. 4.3 Predefined or freely definable TMS Commercial TMSs can have predefined or freely definable data modelling structures. A TMS with a fixed set of data categories, a defined set o
39、f languages and/or an unchangeable data model shall only be used if the setting corresponds exactly with the needs of the organizational environment in which the TMS will be applied. A TMS with a freely definable structure allows users to define their own data categories and their own entry structur
40、es so that the software can be adapted to suit users specific terminological needs and can be modified as future requirements change. 4.4 Desktop, client-server or Web-based TMS The simplest TMSs are installed on a local computer for a single individual. Sometimes the underlying database files are s
41、tored on a LAN computer and can be shared by multiple desktop clients. In large organizations with many users (and different roles), only a TMS with client-server architecture can serve the needs of the organization. These TMSs require a client installation on each local desktop and a server softwar
42、e installation handling the simultaneous access of different clients (with different tasks). If multiple users all over the world are to have access to the terminological data, the only viable solution is a Web-based TMS; users do not have to install software specific to the TMS on their local compu
43、ters because a standard Web browser will allow all operations with the TMS. When opting for a Web-based TMS, designers also have to decide whether to host their own server or to utilize a third-party TMS, for instance choosing between services offered by major TMS software suppliers or free, Web-res
44、ident collaborative environments. Before opting to outsource the hosting function, they should carefully weigh factors such as cost, host expertise, and reliable data accessibility, as well as data security and confidentiality. 4.5 Stand-alone, integrated or combined TMS A stand-alone TMS is an auto
45、nomous software package designed for managing terminology independently of any other application. Integrating the terminology from a stand-alone TMS into other applications, such as controlled authoring tools or Computer Assisted Translation (CAT) tools, usually requires terminology to be exported from the TMS and imported into the other application. Sometimes the integration can be real
