CEN/ISSS WS/eCAT Terminology for ecatalogues and Product Description and Classification Report Final Version This report has been written for WS/eCAT by Mrs. Bodil Nistrup Madsen (bnm.danterm@cbs.dk) and Mr. Håvard Hjulstad (havard@hjulstad.com). Submission of comments and updates Comments and updates should be inserted in the text of the entire report or relevant parts of the report and sent to: bnm.danterm@cbs.dk. Please use the commenting feature or tracking of changes in MS Word.
2 CEN/ISSS WS/eCAT Terminology Report Final version Contents Submission of comments and updates 1 Contents 2 Foreword 3 Introduction 4 1 Scope 5 2 Normative References 6 3 General information about the terminology study 7 4 Concept systems 8 4.1 Concept systems: Knowledge representation 8 4.2 Concept system: Modeling tools 11 4.3 Concept system: Terminology and related products 12 4.4 Concept system: Product catalogues 13 4.5 Concept system: Registries 14 4.6 Levels in product classification systems 15 Level 1 15 Level 2 15 Level 3 15 Level 4 15 Level 5 15 Level 6 15 Recommendations 15 5 Terms and definitions 16 5.1 Terms relating to ontologies and data models 16 5.2 Terms relating to classification systems 21 5.3 Terms relating to modeling tools 23 5.4 Terms relating to terminology and related products 25 5.5 Terms relating to product description and metadata 26 6 Alphabetical list of terms 28 7 Bibliography 30
CEN/ISSS WS/eCAT Terminology Report Final version 3 Foreword This report has been written by Mrs. Bodil Nistrup Madsen, DANTERMcentret, the Danish Terminology Centre, bnm.danterm@cbs.dk and Mr. Håvard Hjulstad, Standards Norway, havard@hjulstad.com or hhj@standard.no for the CEN/ISSS ecat Workshop.
4 CEN/ISSS WS/eCAT Terminology Report Final version Introduction During the work in the CEN/ISSS ecat Workshop and elsewhere it has become clear that there is a need to clean up terminology usage in the fields of ecatalogues and Product Description and Classification. The authors of this document were asked to recommend one set of terms for the use within the project, and hopefully beyond the ecat activities. Work started in December 2003. The terminology work may continue within the WS after the submission of this report by the Project Team. This document is intended as an appendix to the report CEN/ISSS WS/eCAT Multilingual catalogue strategies for ecommerce and ebusiness.
CEN/ISSS WS/eCAT Terminology Report Final version 5 1 Scope The purpose of this document is to attempt to establish consensus within the CEN/ISSS ecat Workshop regarding important concepts of electronic catalogues and product description and classification. Recommendations relating to terms and definitions do not necessarily imply that we find other terms and definitions erroneous or inferior. The document seeks to establish one set of terms and definitions, while other sets might also have served the same purpose. In cases where different fields of study have different terminological tradition, we have chosen to conform more closely to traditional usage within language resources rather than e.g. the usage within data modeling.
CEN/ISSS WS/eCAT Terminology Report Final version 2003-12-30 6 2 Normative References The following International and European Standards have been used in the preparation of this document. Other references of interest are listed in the Bibliography. BS 1000m: Part 1 : 1995 Universal Decimal Classification. International Medium Edition, English text, FID publication no. 571. ISO 704 : 2000 Terminology work Principles and methods. ISO 1087-1 : 2000 Terminology work Vocabulary Part 1: Theory and application. ISO 1087-2 : 2000 Terminology work Vocabulary Part 2: Computer applications. ISO 10303-1 : 1994 Industrial automation systems and integration - Product data representation and exchange - Part 1: Overview and fundamental principles. ISO 12200 : 1999 Computer applications in terminology Machine-readable terminology interchange format (MARTIF) Negotiated interchange. ISO 12620 : 1999 Computer applications in terminology Data categories. ISO 13584 Industrial automation systems and integration Parts library (published in several parts from 1998). ISO 16642 : 2003 Computer applications in terminology Terminological markup framework. ISO/IEC 11179-3 : 2003 (ISO JTC 1/SC 32) Information technology Data management and interchange Metadata registries (MdR) Part 3: Registry metamodel. ISO/IEC 15459-1 : 1999 Information technology Unique identification of transport units Part 1: General. ISO/IEC 15459-2 : 1999 Information technology Unique identification of transport units Part 2: Registration procedures. ISO/IEC FCD 11179-3 : 200x(E) (ISO JTC 1/SC 32): Information technology Data management and interchange Metadata registries (MdR) Part 3: Registry metamodel. ISO/WD 12620-1 : 2003 Data Category Registry for ISO TC37.
CEN/ISSS WS/eCAT Terminology Report Final version 7 3 General information about the terminology study The terminology study that is underlying the presentation in this document is based on traditional terminological principles as described e.g. in documents from ISO/TC 37 (Terminology and other language resources). This report contains a number of general concepts that are central to the fields of ecatalogues and Product Description and Classification. Due to the time limit of the project, many more specific concepts of the domain are not included.
CEN/ISSS WS/eCAT Terminology Report Final version 2003-12-30 8 4 Concept systems Terminology studies utilize concept relations and concept systems as tools. We have chosen to present the concept systems in graphical form to facilitate understanding of the relations between the concepts. The concept systems below are simplified since they do not comprise all relevant concepts within the ecatalogue domain. A few concepts in the concept systems are not defined in section 5 Terms and definitions, and the concept systems do not comprise all concepts defined in section 5. If a concept occurs in several concept systems, it is only defined once. 4.1 Concept systems: Knowledge representation knowledge representation model classification system See figure 4-2 See figure 4-3 ontology data model taxonomy subject classification system Figure 4-1: Top of concept system Knowledge representation Figure 4-2 and 4-3 show two parts of the full concept system Knowledge representation. Explanation of relation types type of part of belongs to describes
CEN/ISSS WS/eCAT Terminology Report Final version 9 model ontology data model top-level ontology domain-specific ontology metamodel conceptual data model information model physical data model database schema terminological concept system product ontology data dictionary XML schema DTD concept concept relation product category entity business vocabulary characteristic product element attribute property feature specification product property attribute value Figure 4-2: Part 1 of concept system Knowledge representation : Ontologies and data models
CEN/ISSS WS/eCAT Terminology Report Final version 2003-12-30 10 classification system taxonomy subject classification system taxonomy category product taxonomy metadata taxonomy product classification system product category metadata category product class metadata product sub category metadata sub category product subclass entity product product description metadata description property product property attribute value attribute value Figure 4-3: Part 2 of concept system Knowledge representation : Classification systems
CEN/ISSS WS/eCAT Terminology Report Final version 11 4.2 Concept system: Modeling tools modeling tool concept modeling tool data modeling tool ontology graph concept diagram UML class diagram ER diagram EER diagram hierarchical element tree concept concept relation concept concept relation class association entity type relationship type entity type relationship type element attribute Figure 4-4: Concept system Modeling tools
CEN/ISSS WS/eCAT Terminology Report Final version 2003-12-30 12 4.3 Concept system: Terminology and related products terminology nomenclature terminological dictionary vocabulary glossary thesaurus relation keyword descriptor non-descriptor Figure 4-5: Concept system Terminology and related products
CEN/ISSS WS/eCAT Terminology Report Final version 13 4.4 Concept system: Product catalogues product catalogue product category ecatalogue See figure 4-3 product description Figure 4-6: Concept system Product catalogues
CEN/ISSS WS/eCAT Terminology Report Final version 2003-12-30 14 4.5 Concept system: Registries registry metadata registry item registry metadata register item repository metadata category See figure 4-3 metadata description Figure 4-7: Concept system Registries
CEN/ISSS WS/eCAT Terminology Report Final version 15 4.6 Levels in product classification systems Words such as section, division, group, etc. have no clear order of magnitude in natural language. One example from public and private administration is that some sections are subdivided into several divisions, while in other cases divisions may consist of several sections. It is no wonder then that different systems of product classification have used widely different denotations for the different levels of their respective hierarchies. It should also be noted that the concept of levels itself may differ from one system to another. The following terms have been identified for the different levels. This list is not exhaustive. Level 1 division main category section sector segment Level 2 category chapter division family group heading macro-family main group major group subsector Level 3 class family group heading industry group sub-category sub-heading Level 4 brick class commodity commodity class commodity group group industry subheading Level 5 attribute category class property sub-class Level 6 attribute category property sub-category Recommendations (1) When using any of the terms designating levels in a hierarchy there should always be a clear indication of which system the terms belong to. (2) It is advisable to use generic terms, such as top level, second level, etc., at least to designate some of the levels.
CEN/ISSS WS/eCAT Terminology Report Final version 2003-12-30 16 5 Terms and definitions The terms in this document are listed in a systematic order. The entries have the following structure: Entry number, recommended term, definition, reference, note on concept and note on terms. Entry number, recommended term and definition are the mandatory elements of each entry. Other elements appear only when appropriate. References are given when the definition is taken over from or based on a definition of a standard. Notes on concepts describe any differences between the concept and closely related concepts as defined or used in other documents. This note can also give additional information about a defined concept. Notes on terms enumerate and explain the usage of other terms that are used for the same concept (or very closely related concepts) in other documents. The terms are printed in boldface and included in the alphabetical index. 5.1 Terms relating to ontologies and data models 1.1 model simplified representation of something 1.2 ontology model of knowledge of the world comprising concepts and relations between concepts NOTE ON CONCEPT The concept ontology is defined in various ways depending on the point of view, e.g. philosophical or pragmatic, top-level or specific, domain-specific or general, formal or not formal etc., cf. e.g. Guarino (1998). John F. Sowa (http://users.bestweb.net/~sowa/ontology/) defines ontology as the study of categories of things that exist or may exist in some domain, cf. clause 8.2 of the report CEN/ISSS WS/eCAT Multilingual catalogue strategies for ecommerce and ebusiness. Guarino (1998) defines ontology as a logical theory accounting for the intended meaning of a formal vocabulary, i.e. its ontological commitment to a particular conceptualization of the world. Our recommendation is to use the term in the general meaning as defined here. An ontology may comprise all kinds of relations between concepts, e.g. generic, partitive and temporal relations, cf. also concept relation, 1.13. This is in contrast to a classification system, which comprises only generic relations. A data model should always be based on an ontology, but sometimes a data model, represented by means of an ER diagram, is referred to as an ontology. Our recommendation is to use the term ontology only as defined here. Please observe that the term conceptual model is referring to a kind of data model, cf. 1.17 conceptual data model. NOTE ON TERMS The terms concept model and concept system are also used, but our recommendation is to use ontology. See also terminological concept system cf. 1.5.
CEN/ISSS WS/eCAT Terminology Report Final version 17 1.3 top-level ontology ontology that describes general concepts like space, time, matter, object, event, action, etc., which are independent of a particular problem or domain NOTE ON TERMS The term top ontology is also used, but our recommendation is to use top-level ontology. 1.4 domain-specific ontology ontology which describes concepts of a specific domain NOTE ON TERMS The term domain ontology is also used, but our recommendation is to use domain-specific ontology. 1.5 terminological concept system domain-specific ontology used in terminology work NOTE ON CONCEPT ISO 1087-1: 2000 (3.2.11) defines concept system as set of concepts structured according to the relations among them. However, the definition given here takes into consideration the position of the concept in the concept system in figure 4-2. NOTE ON TERMS The term concept system is also used, cf. 1.2. 1.6 concept unit of knowledge created by a unique combination of characteristics REFERENCE ISO 1087-1: 2000, 3.2.1 NOTE ON CONCEPT This term is used for different concepts with a continuously varying degree of specialization. Our recommendation is to use the term in the specific meaning as defined here, which is the common usage in the field of terminology. NOTE ON TERMS Concepts in ontologies are also often referred to as types, but the term concept is always used in combination with concept systems used for terminology work ( terminological concept systems ). Our recommendation is to use only the term concept. 1.7 entity anything perceivable or conceivable REFERENCE ISO 1087-1: 2000, 3.1.1 NOTE ON CONCEPT Objects may be material (e.g. an engine, a sheet of paper, a diamond) or immaterial (e.g. conversion ratio, a project plan). 1.8 characteristic feature of a concept describing a property of the entities that make up the extension of the concept NOTE ON CONCEPT Characteristics are used for describing concepts. ISO 1087-1: 2000 (3.2.4) defines characteristic as abstraction of a property of an object or of a set of objects. However, the definition given here takes into consideration the position of the concept in the concept system in figure 4-2.
CEN/ISSS WS/eCAT Terminology Report Final version 2003-12-30 18 The terms characteristic, property and attribute are often used more or less synonymously. Our recommendation is to use: characteristic when referring to the concept level, property when referring to the entity level and attribute when referring to the specification level. 1.9 property quality of an entity NOTE ON CONCEPT Cf. note on characteristic, 1.8. 1.10 feature specification formal representation of a characteristic of a concept by means of an attribute-value pair NOTE ON CONCEPT Example: line printer [OUTPUT: line-per-line], page printer [OUTPUT: page-per-page]. 1.11 attribute part of a feature specification which specifies the feature name NOTE ON CONCEPT The name of an attribute represents the role played by its associated value in the context of the entity in which it occurs. Cf. note on characteristic, 1.8. Please observe that the term attribute also designates another concept, cf. 1.25. Example: line printer [OUTPUT: line-per-line], page printer [OUTPUT: page-per-page]. 1.12 value part of a feature specification which specifies the content of an attribute NOTE ON CONCEPT Example: line printer [OUTPUT: line-per-line], page printer [OUTPUT: page-per-page]. 1.13 concept relation semantic relation between concepts NOTE ON CONCEPT In terminology work one distinguishes between hierarchical relations and associative relations. Hierarchical relations are generic relations (genus-species relations) and partitive relations (part-whole relations). Associative relations are all other kinds of relations, cf. ISO 1087-1: 2000, 3.2.3. 1.14 product ontology domain-specific ontology in which the concepts refer to product categories NOTE ON CONCEPT A product ontology may comprise all kinds of relations and may be a network, as opposed to a product taxonomy, which comprises only generic relations, and which does not allow poly-hierarchy, cf. product taxonomy, 2.4, and product category, 2.5. Most ecatalogues will probably comprise product taxonomies, not product ontologies. ECatalogues may use a combination of a subject classification system for an overall grouping of product categories and one or more specific taxonomies for a more detailed systematization of product categories, cf. subject classification system, 2.15. 1.15 data model formal model for the specification of the properties, structure and inter-relationships of data
CEN/ISSS WS/eCAT Terminology Report Final version 19 REFERENCE Amended from ISO/IEC 11179-3: 2003(E), 3.2.11 NOTE ON TERMS The term data model was originally used to designate a model for describing databases, e.g. the relational model. However, it is also used for the description of the data structure of a database, and it is this meaning of data model which is defined here. 1.16 metamodel a data model that specifies one or more other data models REFERENCE ISO/IEC 11179-3:2003(E), 3.2.24 NOTE ON CONCEPT ISO 16642: 2003 defines metamodel as abstract conceptual data model that supports analysis and design at a very general level. NOTE ON TERMS The variant meta-model is also used. Our recommendation is to use the term metamodel. 1.17 conceptual data model data model that represents an abstract view of the real world REFERENCE ISO/IEC 11179-3: 2003(E), 3.2.8 NOTE ON CONCEPT Is often represented by means of a UML class diagram. NOTE ON TERMS Please observe that the term concept model designates another concept, namely the concept ontology, 2.2, and it should therefore not be mixed up with the concept conceptual data model. The term conceptual model is also used. Our recommendation is to use the term conceptual data model. 1.18 information model data model that represents the organization of information in a manner that reflects the structure of an information system REFERENCE Amended from ISO/IEC FCD 11179-3: 200x(E), 3.2.13 NOTE ON CONCEPT ISO/IEC FCD 11179-3: 200x(E), 3.2.13 defines information model in the following way: a high level description of the organization of information in a manner that reflects its structure. It takes the form of logical groupings of entities and levels of subentities, without showing any relationships between entities other than the hierarchies of sub-entities. An information model is often represented by means of a hierarchical element tree, cf. 3.14, but may also be represented by means of a UML class diagram which is based on the hierarchical relationship, that is the only possible kind of relationship in an XML document. 1.19 physical data model data model represented in a database schema 1.20 database schema schema that describes the physical storage of data
CEN/ISSS WS/eCAT Terminology Report Final version 2003-12-30 20 1.21 data dictionary relational database schema that contains information about relations and attributes NOTE ON TERMS Sometimes the term data dictionary is used as a synonym for business vocabulary, cf. 1.24. Our recommendation is to use data dictionary only in combination with relational database models. 1.22 XML schema database schema that is expressed by means of an XML-based markup language for describing the structure and constraining the contents of XML documents 1.23 business vocabulary set of element names and attribute names that are selected or produced in order to create a custom XML-based markup language NOTE ON CONCEPT A vocabulary forms the basis of an XML schema or a DTD that specifies the relationships between elements and attributes, the restrictions on element contents and attribute values, allowed data types, and so on. The term vocabulary is sometimes used to refer to an entire XML-based markup language defined in an XML schema or a DTD. Our recommendation is to use the term business vocabulary in the meaning as defined here. NOTE ON TERMS The short form vocabulary (without the specification business ) is often used. Our recommendation is, however, to use the term business vocabulary in order to distinguish this concept from the concept vocabulary in the field of terminology. Sometimes the term data dictionary is used as a synonym for business vocabulary. Our recommendation is to use data dictionary only in combination with relational database models, cf. 1.21. 1.24 element in XML and SGML, a main building block of an XML document 1.25 attribute in XML and SGML, a name-value pair associated with an element 1.26 DTD database schema in XML or SGML that comprises a set of declarations that describe the components and structure of a class of documents
CEN/ISSS WS/eCAT Terminology Report Final version 21 5.2 Terms relating to classification systems 2.1 classification system representation of the hierarchical division of phenomena or concepts on the basis of their properties or characteristics NOTE ON CONCEPT A classification system is hierarchical and based exclusively on generic relations. NOTE ON TERMS The term classification is often used in this meaning. Our recommendation is to use the term classification system. 2.2 taxonomy classification system for the classification of categories of a domain NOTE ON CONCEPT A taxonomy is a kind of classification system, that comprises exclusively generic relations between the categories, in contrast to an ontology, which is a kind of model that may comprise all kinds of relations between concepts, cf.1.2. 2.3 taxonomy category concept classified in a taxonomy NOTE ON TERMS The nodes representing concepts in taxonomies are normally referred to as categories. The designation of a category is often referred to as category name. This is probably due to the fact that originally taxonomies typically were used for the categorization of e.g. plants, the designations of which were referred to as names. 2.4 product taxonomy taxonomy defining the relations between product categories NOTE ON CONCEPT Our recommendation is to use the term as defined here and to distinguish it from the concept product ontology, cf. 1.14. An ontology may comprise all kinds of relations between concepts (generic, partitive, temporal relations etc.), whereas a taxonomy comprises exclusively generic relations between concepts. 2.5 product category category in a product taxonomy, denoting a class of products NOTE ON CONCEPT See note on product, 2.6. 2.6 product thing or substance produced by a natural or artificial process REFERENCE ISO 10303-1, 3.2.26 NOTE ON CONCEPT A product may be material or immaterial. NOTE ON TERMS The term product is used for several concepts, e.g. for individual product or product category. Our recommendation is to use the term in the meaning of individual product as defined here. 2.7 product sub category sub category of a product category
CEN/ISSS WS/eCAT Terminology Report Final version 2003-12-30 22 2.8 product description specification of the characteristics of a product category NOTE ON CONCEPT The specification may be given by means of an attribute-value pair or by means of a definition. ISO 10303-1 (3.2.27) defines product data as representation of information about a product in a formal manner suitable for communication, interpretation, or processing by human beings or by computers. The same standard (3.2.28) defines product information as facts, concepts, or instructions about a product. NOTE ON TERMS Our recommendation is to use only the term product description. 2.9 product property property of a product 2.10 metadata taxonomy taxonomy defining the relations between metadata categories 2.11 metadata category category denoting a class of metadata NOTE ON TERMS ISO 16642 : 2003, uses both data category and meta data, and defines data category, 3.2, as result of the specification of a given data field [ISO 1087-2:2000], (i.e. a type of data field, such as definition). Our recommendation is to use only the term metadata category. 2.12 metadata data that defines and describes other data REFERENCE ISO/IEC 11179-3: 2003(E), 3.2.18 2.13 metadata sub category sub category of a metadata category 2.14 metadata description specification of the characteristics of a metadata category NOTE ON CONCEPT The specification may be given by means of an attribute-value pair or by means of a definition. 2.15 subject classification system classification system for the division of phenomena into subject fields NOTE ON CONCEPT Each class in a subject classification system consists of a group of phenomena making up a domain. An example is the Universal Decimal Classification (BS 1000M: Part 1, 1985) where the class with the systematic notation 631.312.3 comprises the following tools: Ploughing machines. Ploughs with movable tools. Rotary ploughs. Gyrotillers. Spading machines etc. ISO 1087-1: 2000, 3.1.2 defines subject field, domain as field of special knowledge.
CEN/ISSS WS/eCAT Terminology Report Final version 23 NOTE ON TERMS The term subject classification is often used for subject classification system. Our recommendation is to use the term subject classification system. 2.16 product classification system subject classification system for the grouping of products into subject fields NOTE ON CONCEPT Clause 8.2 of the report CEN/ISSS WS/eCAT Multilingual catalogue strategies for ecommerce and ebusiness says: The task of product classification is to assign each product to a product group (called classification group or short class ) corresponding to common attributes or application areas. Our recommendation is to use the term as defined here, cf. also product class 2.17. A product classification gives an overall assignment of a product to a group of products (product class), whereas a product taxonomy uniquely specifies a product category (the concept of a product) in relation to other product categories. ECatalogues may use a combination of a subject classification system for an overall grouping of products and one or more specific taxonomies for a more detailed systematization of product categories, cf. 2.5. NOTE ON TERMS The term product classification is often used for product classification system. Our recommendation is to use the term product classification system. 2.17 product class group of products in a product classification system NOTE ON CONCEPT Each class comprises a group of products, i.e. each node in the product classification system represents a group of products. An example of a product class is: - detectors, actuators, electrical motors, This is in contrast to a node of a product taxonomy, which represents one product category (i.e. one concept). Examples of product categories of a product taxonomy are: - detector - actuator - electrical motor 2.18 product subclass subclass of a product class 5.3 Terms relating to modeling tools 3.1 modeling tool tool for the graphical representation of a model 3.2 concept modeling tool modeling tool for the representation of a concept model
CEN/ISSS WS/eCAT Terminology Report Final version 2003-12-30 24 3.3 ontology graph concept modeling tool for the graphical representation of an ontology 3.4 concept diagram concept modeling tool for the graphical representation of a concept system REFERENCE Modified from ISO 1087-1: 2000, 3.2.12 3.5 data modeling tool modeling tool for the representation of a data model 3.6 UML class diagram in UML, a data modeling tool that shows a set of classes and their associations NOTE ON CONCEPT UML class diagrams are often used in a simplified form (without attributes and operations) to represent ontologies, i.e. as a concept modeling tool. Our recommendation is to use the term in the meaning as defined here. NOTE ON TERMS UML is an abbreviation of Unified Modeling Language (OMG Unified Modeling Language Specification, 2003), cf. 3.7. 3.7 Unified Modeling Language language for specifying, visualizing, constructing and documenting the artifacts of software systems NOTE ON TERMS Unified Modeling Language is abbreviated UML, (OMG Unified Modeling Language Specification, 2003). 3.8 class in a UML class diagram, a description of a set of objects that share the same attributes, operations, methods, relationships, and semantics REFERENCE Amended from ISO/IEC 11179-3:2003(E). 3.9 association in a UML class diagram, a semantic relationship between two classes REFERENCE Amended from ISO/IEC 11179-3:2003(E), 3.1.4 NOTE ON CONCEPT Special types of associations are part-whole associations (aggregations and compositions) and generic associations (generalization / specialization). 3.10 ER diagram data modeling tool for representation of data models for relational databases that shows entity types and relationship types NOTE ON TERMS ER is an abbreviation of Entity-Relationship. 3.11 entity type in an ER diagram, a description of a set of entities that share the same attributes
CEN/ISSS WS/eCAT Terminology Report Final version 25 3.12 relationship type in an ER diagram, a semantic relationship between two entity types 3.13 EER diagram ER diagram with extended features, such as for example superclasses and subclasses NOTE ON TERMS EER is an abbreviation of Enhanced Entity-Relationship. 3.14 hierarchical element tree data modeling tool for the graphical representation of the structure of an XML schema NOTE ON TERMS Geroimenko (2004) uses the term hierarchical tree structure. 5.4 Terms relating to terminology and related products 4.1 terminology science studying the structure, formation, development, usage and management of terminologies in various subject fields REFERENCE ISO 1087-1: 2000, 3.5.2 NOTE ON TERMS Please observe that the term terminology also refers to the concept in 4.2. 4.2 terminology set of designations belonging to one special language REFERENCE ISO 1087-1: 2000, 3.5.1 NOTE ON TERMS Please observe that the term terminology also refers to the concept in 4.1. 4.3 nomenclature terminology structured systematically according to pre-established naming rules REFERENCE ISO 1087-1: 2000, 3.5.3 NOTE ON CONCEPT Nomenclatures have been elaborated in various fields, such as biology, medicine, physics and chemistry. 4.4 terminological dictionary collection of terminological entries presenting information related to concepts or designations from one or more specific subject fields REFERENCE ISO 1087-1: 2000, 3.7.1 NOTE ON TERMS synonym: technical dictionary.
CEN/ISSS WS/eCAT Terminology Report Final version 2003-12-30 26 4.5 vocabulary terminological dictionary which contains designations and definitions from one or more specific subject fields REFERENCE ISO 1087-1: 2000, 3.7.2 NOTE ON CONCEPT The vocabulary may be monolingual, bilingual or multilingual. Please observe that the term vocabulary is also used for business vocabulary, cf. 1.24, which is a different concept. 4.6 thesaurus vocabulary of a controlled indexing language, formally organized so that the a priori relationships between concepts (for example 'broader' and 'narrower') are made explicit REFERENCE ISO 2788:1986 NOTE ON CONCEPT The term thesaurus is also used to designate a dictionary where the words are ordered according to the relations between them such as e.g. Roget s Thesaurus. 4.7 glossary terminological dictionary which contains a list of designations from a subject field, together with equivalents in one or more languages REFERENCE ISO 1087-1: 2000, 3.7.3 NOTE ON CONCEPT In English common language usage glossary can refer to a unilingual list of designations and definitions in a particular subject field. 5.5 Terms relating to product description and metadata 5.1 product catalogue catalogue that describes product categories 5.2 ecatalogue product catalogue that is used in ecommerce and ebusiness 5.3 metadata registry information system for registering metadata REFERENCE ISO/IEC 11179-3:2003(E), 3.2.22 NOTE ON CONCEPT register. The associated information store or database is known as a metadata NOTE ON TERMS ISO 16642 : 2003, uses both data category registry and meta data registry. Our recommendation is to use only the term metadata registry. 5.4 metadata register information store or database maintained by a metadata registry REFERENCE ISO/IEC ISO/IEC 11179-3:2003(E), 3.2.21
CEN/ISSS WS/eCAT Terminology Report Final version 27 5.5 item registry information system for storing XML items (e.g., XML schemas, data elements, etc.) and non XML items (e.g. other e-business objects) NOTE ON CONCEPT The definition is modified from http://www.ebxml.org/ebusinessxmlregistry.pdf that uses artifacts instead of items. NOTE ON TERM This term is not explicitly mentioned in the documentation about registries, however our recommendation is to use this term to distinguish between item registry and item repository. 5.6 item repository location or set of distributed locations where repository Items, pointed at by the registry, reside and from which they can be retrieved NOTE ON CONCEPT Definition from UN/CEFACT and OASIS, ebxml Glossary, Technical Architecture Team, 2001. NOTE ON TERMS Normally the term repository is used. Our recommendation is to use the term item repository.
CEN/ISSS WS/eCAT Terminology Report Final version 2003-12-30 28 6 Alphabetical list of terms This alphabetical list of terms refers to the term numbers in the previous chapter. Included in the alphabetical list are also terms mentioned in the notes. All terms in this list are consequently not recommended terms. association (3.9);24 attribute (1.11);18 attribute (1.25);20 attribute (level 5);15 attribute (level 6);15 brick (level 4);15 business vocabulary (1.23);20 category (level 2);15 category (level 5);15 category (level 6);15 category name;21 chapter (level 2);15 characteristic (1.8);17 class (3.8);24 class (level 3);15 class (level 4);15 class (level 5);15 classification;21 classification system (2.1);21 commodity (level 4);15 commodity class (level 4);15 commodity group (level 4);15 concept (1.6);17 concept diagram (3.4);24 concept model;16 concept modeling tool (3.2);23 concept relation (1.13);18 concept system;16;17 conceptual data model (1.17);19 conceptual model;19 data category;22 data category registry;26 data dictionary (1.21);20 data model (1.15);18 data modeling tool (3.5);24 database schema (1.20);19 division (level 1);15 division (level 2);15 domain ontology;17 domain- specific ontology (1.4);17 DTD (1.26);20 ecatalogue (5.2);26 EER diagram (3.13);25 element (1.24);20 entity (1.7);17 entity type (3.11);24 ER diagram (3.10);24 family (level 2);15 family (level 3);15 feature specification (1.10);18 glossary (4.7);26 group (level 2);15 group (level 3);15 group (level 4);15 heading (level 2);15 heading (level 3);15 hierarchical element tree (3.14);25 hierarchical tree structure;25 individual product;21 industry (level 4);15 industry group (level 3);15 information model (1.18);19 item registry (5.5);27 item repository (5.6);27 macro-family (level 2);15 main category (level 1);15 main group (level 2);15 major group (level 2);15 metadata (2.12);22 metadata category (2.11);22 metadata description (2.14);22 metadata register (5.4);26 metadata registry (5.3);26 metadata sub category (2.13);22 metadata taxonomy (2.10);22 metamodel (1.16);19 model (1.1);16 modeling tool (3.1);23 nomenclature (4.3);25 ontology (1.2);16
CEN/ISSS WS/eCAT Terminology Report Final version 29 ontology graph (3.3);24 physical data model (1.19);19 product (2.6);21 product catalogue (5.1);26 product category (2.5);21 product class (2.17);23 product classification;23 product classification system (2.16);23 product description (2.8);22 product ontology (1.14);18 product property (2.9);22 product sub category (2.7);21 product subclass (2.18);23 product taxonomy (2.4);21 property (1.9);18 property (level 5);15 property (level 6);15 relationship type (3.12);25 repository;27 section (level 1);15 sector (level 1);15 segment (level 1);15 sub-category (level 3);15 sub-category (level 6);15 sub-class (level 5);15 sub-heading (level 3);15 sub-heading (level 4);15 subject classification;23 subject classification system (2.15);22 subsector (level 2);15 taxonomy (2.2);21 taxonomy category (2.3);21 technical dictionary;25 terminological concept system (1.5);17 terminological dictionary (4.4);25 terminology (4.1);25 terminology (4.2);25 thesaurus (4.6);26 top ontology;17 top-level ontology (1.3);17 types;17 UML;24 UML class diagram (3.6);24 Unified Modeling Language (3.7);24 value (1.12);18 vocabulary (4.5);26 XML schema (1.22);20
CEN/ISSS WS/eCAT Terminology Report Final version 2003-12-30 30 7 Bibliography - Geroimenko, Vladimir (2004): Dictionary of XML Technologies and the Semantic Web, Springer Professional Computing, Springer-Verlag London - Guarino, N. (1998): Amended version of a paper appeared in N. Guarino (ed.), Formal Ontology in Information Systems. Proceedings of FOIS 98, Trento, Italy, 6-8 June 1998. Amsterdam, IOS Press, pp. 3-15. http://www.loacnr.it/papers/fois98.pdf - OMG (2003): Unified Modeling Language Specification - UN/CEFACT and OASIS (2001): ebxml Glossary, Technical Architecture Team