Changes between Version 31 and Version 32 of VLO-Taskforce/Relations

Timestamp:

02/10/14 16:37:54 (10 years ago)

Author:

eckartkn@ims.uni-stuttgart.de

Comment:

added IMS section

VLO-Taskforce/Relations

@@ -163 +163 @@
 }}}
 
+=== IMS Stuttgart ===
+
+This is a list of the relations which we would like to represent in the CMDI records, and how we deal with them so far.
+Due to the fact, that we were not sure about recommendations how to use the 'Resources' component, we have not applied it yet, but are of course interested in using it, so that some of the relations might also be exploited in the VLO:
+
+a. 
+  * Relation type: tool -- modular tool component (parameter file, language model, lexicon, ...)
+  * Current approach: Using the CMDI component 'Prereqisites' (clarin.eu:cr1:c_1290431694521) to state that a tool needs an additional component. The tool components are described in their own CMDI record (profile not in public section yet).
+  * Examples:
+       * !TreeTagger (Metadata: http://hdl.handle.net/11858/00-247C-0000-0022-C698-E) --> Italian parameter file (Achim Stein)
+       * !TreeTagger (Metadata: http://hdl.handle.net/11858/00-247C-0000-0022-C698-E) --> Italian parameter file (Marco Baroni)
+       * !TreeTagger (Metadata: http://hdl.handle.net/11858/00-247C-0000-0022-C698-E) --> English parameter file
+       * Mate Tools Parser (Metadata: http://hdl.handle.net/11858/00-247C-0000-0022-C697-0) --> French model
+       * Mate Tools Parser (Metadata: http://hdl.handle.net/11858/00-247C-0000-0022-C697-0) --> English model
+       * !BitPar (Metadata http://hdl.handle.net/11858/00-247C-0000-0022-F7AF-1)--> Lexicon DE
+       * !BitPar (Metadata http://hdl.handle.net/11858/00-247C-0000-0022-F7AF-1)--> Grammar EN
+b. 
+  * Relation type: trained model -- data set on which the model was trained
+  * Current approach: Optional CMDI component '!BasedOn' as part of the profile to describe tool components (CMDI component not in public section yet).
+  * Examples:
+       * Dutch parameter file for !TreeTagger --> trained on Eindhoven corpus
+       * German grammar for !BitPar --> extracted from Tiger treebank
+c. 
+  * Relation type: versioning
+  * Current approach: Element 'Version' in CMDI component '!GeneralInfo' (clarin.eu:cr1:c_1290431694495) and where applicable a common part in the '!ResourceName' to implicitly relate different versions.
+  * No examples yet, but this will change in future. Affects all types of resources: corpora, lexicons, tools, web services, ...
+d.  
+  * Relation type: tool -- web service
+  * We keep getting mails asking for information and publications on the tools 'behind' the web services. This also affects the action item regarding the CMDI profiles for web services.
+
+Further notes:
+ * Making these relations explicit will also mean more maintenance effort to keep the md-records up to date, thus we should discuss where this will make sense and where it creates too much overhead.
+ * Some relationships are between 'clearly distinct' resources: 'Source' was mentioned in the Tischvorlage, others might include:
+    * 'A is based on B' e.g. when a trainable component (parameterfile, language model, ...) has been trained on a specific corpus, or a collection of technical terms has been extracted based on the frequencies of a specific corpus resource (see relation type b.)
+    * 'A can be used with B', e.g. when a tool can use an (additional) knowledge base (lexicon, language model, ...), or a corpus is encoded for a specific query engine (see relation type a.)
+    * 'A was used for the creation of B', e.g. when manual annotations were added with the help of a specific system, ...
+  At the moment some of these relationships can be expressed in the component section of the CMDI-records (e.g. 'Derivation', 'Source') but are not exploited in the VLO.
+
+
 === Summary on Representation of Relationships ===