31 | | Being prepared in [https://docs.google.com/document/d/14yrkJwg2lxf5GGkkA-wMjgByHSlQYWiSt--Lvn0biyo/edit?usp=sharing Google Docs] |
32 | | |
33 | | {{{#!comment |
34 | | TODO: Review glossary items below |
35 | | CLARIN-FCS, FCS:: |
36 | | CLARIN federated content search, an interface specification to allow searching within resource content of repositories. |
37 | | |
38 | | PID:: |
39 | | A Persistent identifier is a long-lasting reference to a digital object. |
40 | | |
41 | | attribute:: |
42 | | synonym of XML attribute |
43 | | |
44 | | bundle:: |
45 | | collection in which the resources are tight together, having the same origin and are distributed together |
46 | | a media file and its annotation created and distributed by the same person |
47 | | |
48 | | CCSL, CMDI Component Specification Language:: |
49 | | XML based language for describing components according to the CMDI model |
50 | | |
51 | | CMDI, Component Metadata Infrastructure:: |
52 | | Metadata description framework consisting of the CMDI model and infrastructure |
53 | | |
54 | | collection:: |
55 | | set of resources described by common metadata and distributed as a unit, i.e. referenced by a single persistent identifier |
56 | | |
57 | | component:: |
58 | | list of metadata elements and other components of which every data element corresponds to a metadata category. Together they describe an aspect of a component, e.g. name, language, other metadata properties of a LRT |
59 | | |
60 | | data category, datcat:: |
61 | | result of the specification of a given data field |
62 | | 1. a type of data field, such as /definition/. |
63 | | 2. ISO 212620:2009 provides for the creation of an inventory of data categories. |
64 | | |
65 | | data category registry:: |
66 | | set of data categories to be used as a reference for the definition of linguistic annotation schemes or any other formats in the domain of language resources |
67 | | |
68 | | DCR, Data Category Registry, ISO TC37 Data Category Registry:: |
69 | | Data category registry used for ISO Technical Committee 37. |
70 | | The DCR is available at http://www.isocat.org. |
71 | | |
72 | | DCS, Data Category Selection:: |
73 | | set of data categories selected from the DCR |
74 | | |
75 | | data category selection:: |
76 | | set of attributes used to fully describe a given data element concept |
77 | | |
78 | | data stream:: |
79 | | constituent of a digital object |
80 | | individual files in a digitial object |
81 | | |
82 | | digital object, DO:: |
83 | | resource in a repository stored in one repository containter that can be addressed by an identifier |
84 | | a digital object can be seen as a generalization of a directory in a file system containing one or more files which are the data stream(s). Digital objects can exist in databases, hence the comparison to directory and file structures falls short. |
85 | | |
86 | | element:: |
87 | | synonym of XML element |
88 | | |
89 | | information unit, IU:: |
90 | | elementary piece of information attached to a level of the metamodel |
91 | | |
92 | | mimetype:: |
93 | | type of file as defined by IETF RFC 2045, IETF RFC 2046 and registered by IANA |
94 | | |
95 | | namespace:: |
96 | | synonym to XML namespace |
97 | | |
98 | | persistent identifier, PID:: |
99 | | unique Uniform Resource Identifier (URI) that assures permanent access for a digital object by providing access to it independently of its physical location or current ownership |
100 | | |
101 | | profile:: |
102 | | component that can be translated into a schema for metadata for a specific type of resource |
103 | | |
104 | | proxy:: |
105 | | placeholder for external data; a proxy provides a standard way of addressing otherwise unreachable resources |
106 | | |
107 | | registry:: |
108 | | central directory designed for persistent provision of negotiated information that can rebiably be accessed |
109 | | |
110 | | repository:: |
111 | | computer system for long time storage of resources |
112 | | |
113 | | resource:: |
114 | | entity that can be referenced by a URI |
115 | | |
116 | | resource type:: |
117 | | classification of a resource |
118 | | |
119 | | UML, Unified Modelling Language:: |
120 | | language for specifying, visualizing, constructing and documenting the artifacts of software systems |
121 | | |
122 | | URI, Uniform Resource Identifier:: |
123 | | identifier for locating resources on the internet |
124 | | |
125 | | value:: |
126 | | property of an attribute |
127 | | |
128 | | virtual collection:: |
129 | | collection in which the individual resources are loosely combined in a registry and do not necessarily exist in one digital object. |
130 | | }}} |
| 31 | {{{#!div class="system-message" |
| 32 | Please do not edit here, but use the [https://docs.google.com/document/d/14yrkJwg2lxf5GGkkA-wMjgByHSlQYWiSt--Lvn0biyo/edit?usp=sharing Google Docs version]! |
| 33 | }}} |
| 34 | |
| 35 | * CMD model, Component Metadata model |
| 36 | * The component based metadata model described in the present specification |
| 37 | * CMDI, Component Metadata Infrastructure |
| 38 | * Metadata description framework consisting of the __CMD model__ and infrastructure |
| 39 | * CCSL, CMDI Component Specification Language |
| 40 | * __XML__ based language for describing components according to the __CMD__ model |
| 41 | * CLARIN |
| 42 | * The infrastructure governed by the CLARIN ERIC |
| 43 | * [http://www.clarin.eu] |
| 44 | |
| 45 | |
| 46 | * resource, language resource |
| 47 | * A (digitally) accessible entity that can be described in terms of its content and technical properties, referenced by a __Uniform Resource Identifier__ |
| 48 | * digital object |
| 49 | * __Resource__ in a repository stored in one repository container that can be addressed by an identifier; a digital object can be seen as a generalization of a directory in a file system containing one or more files which are the data stream(s). Digital objects can exist in databases, hence the comparison to directory and file structures falls short. |
| 50 | |
| 51 | * metadata |
| 52 | * A description of a __resource__, usually given as a set of properties in the form of attribute-value pairs. This description may contain information about the resource, aspects or parts of the resource and/or artefacts and actors connected to the resource. |
| 53 | * persistent identifier, PID |
| 54 | * Unique __Uniform Resource Identifier__ that assures permanent access for a digital object by providing access to it independently of its physical location or current ownership |
| 55 | |
| 56 | * concept |
| 57 | * An abstract or generic idea generalized from particular instances (source: [http://www.merriam-webster.com/dictionary/concept Merriam-Webster]) |
| 58 | * semantic registry |
| 59 | * A list/directory/system maintaining (authoritative) definitions of terms, __concepts__ or data categories. These registries should also provide __persistent identifiers__ for their entries. |
| 60 | * concept link |
| 61 | * A reference from a __CMD profile__, __CMD component__, __CMD element__, __CMD attribute__ or a value in a __controlled vocabulary__ to an entry in a __semantic registry__ via its __persistent identifier__. |
| 62 | * CLARIN Concept Registry |
| 63 | * The __semantic registry__ maintaining __concepts__ used/central to the CLARIN infrastructure |
| 64 | * [http://clarin.eu/ccr] |
| 65 | |
| 66 | * XML |
| 67 | * Markup language standard as described by W3C recommendation http://www.w3.org/TR/xml/ |
| 68 | * XML document |
| 69 | * ... |
| 70 | * XML element |
| 71 | * A constituent of an __XML document__ as defined in W3C recommendation [http://www.w3.org/TR/xml/] (distinct from a __CMD element__) |
| 72 | * XML schema datatype |
| 73 | * A predefined set of permissible content within a section of an XML document as described in [http://www.w3.org/TR/xmlschema-2/] |
| 74 | * XML container element |
| 75 | * An __XML element__ that has one or more XML elements as its descendants |
| 76 | * XML attribute |
| 77 | * A property of an __XML element __as defined in W3C recommendation http://www.w3.org/TR/xml/ (distinct from a __CMD attribute__) |
| 78 | * Uniform Resource Identifier, URI |
| 79 | * An identifier for __resources__ as described in [http://tools.ietf.org/html/rfc3986 RFC3986] |
| 80 | * namespace |
| 81 | * An __XML__ namespace as described in [http://www.w3.org/TR/xml-names/] |
| 82 | |
| 83 | * CMD instance, metadata instance, CMDI file, metadata record, CMD record |
| 84 | * A file that conforms to the general CMDI instance structure as described in this specification, and at the __instance payload__ level follows the specific structure defined by the __CMD specification__ it relates to |
| 85 | * Instance header |
| 86 | * The section of a __metadata instance__ marked as ‘header’, providing information on that metadata instance as such, not the __resource__ that is described by the metadata file |
| 87 | * Resource proxy, CMD resource reference |
| 88 | * A representation of a __resource__ within a __metadata instance__ containing a __Uniform Resource Identifier__ as a reference to the resource itself and a specification of its type (one of: Resource, Metadata, !SearchPage, !SearchService, !LandingPage) |
| 89 | * Resource proxy reference |
| 90 | * A reference from any point within the __instance payload__ to any of the __resource proxies__ |
| 91 | * Instance payload(?) |
| 92 | * The section of a __metadata instance__ that follows the structure defined by the profile it references and contains the description of the __resources__ to which that metadata instance relates |
| 93 | |
| 94 | * CMD specification, component specification/definition, profile specification/definition |
| 95 | * The implementation of a __CMD component__ or __CMD profile__ by means of the __CCSL__ |
| 96 | * Specification header, component header, profile header |
| 97 | * The section of a __CMD specification__ marked as ‘header’, providing information on that specification as such that is not part of the defined structure |
| 98 | * CMD component, component |
| 99 | * A reusable, structured template for the description of (an aspect of)a __resource__, defined by means of a __CMD specification__ document with the potential of embedding other components by reference |
| 100 | * CMD profile, profile definition, profile |
| 101 | * A __CMD component__ that is used to describe a class of resources and is not embedded into other components, and therefore provides the complete structure for an __instance payload__ |
| 102 | * CMD element, element definition |
| 103 | * A unit of a CMD component that describes the level of the __metadata instance__ that can carry atomic values constrained by a __value scheme__, and does not contain further levels except for that of the __CMD attribute__ |
| 104 | * CMD attribute |
| 105 | * A unit of a CMD element that describes the level at which properties of a __CMD element__ can be provided by means of __value scheme __constrained atomic values. |
| 106 | |
| 107 | * value scheme |
| 108 | * A set of constraints governing the range of values allowed for a specific __CMD element__ or __CMD attribute__ in a __metadata instance__, expressed in terms of an __XML schema datatype__, __controlled vocabulary__, or __regular expression__ |
| 109 | * controlled vocabulary, closed/open vocabulary |
| 110 | * A set of values that can be used either to constrain the set of permissible values or to provide suggestions for applicable values in a given context |
| 111 | * regular expression |
| 112 | * An expression that constrains the set of permissible values,as described in XML Schema Regular Expressions [http://www.w3.org/TR/xmlschema-2/#regexs] |