Changes between Version 1 and Version 2 of CMDI 1.2/Vocabularies/Summary


Ignore:
Timestamp:
03/05/14 11:27:59 (10 years ago)
Author:
Twan Goosen
Comment:

issue description

Legend:

Unmodified
Added
Removed
Modified

  • CMDI 1.2/Vocabularies/Summary

    v1 v2  
    77== Issue description ==
    88
    9 The issue is about utilising external vocabularies as value domains for CMDI elements and CMDI attributes (i.e. Attribute elements. More specifically, how to do this using the [http://openskos.org OpenSKOS]-based [https://openskos.meertens.knaw.nl/web-report/documentation/clavas-overview.html CLAVAS] vocabulary service.
     9The objective is to utilise external vocabularies as value domains for CMDI elements and CMDI attributes. While the solution on the model level should be generic and service-agnostic, it will be designed specifically to work with the [http://openskos.org OpenSKOS]-based [https://openskos.meertens.knaw.nl/web-report/documentation/clavas-overview.html CLAVAS] vocabulary service.
    1010
    11 This has been described and explored on the page [[CmdiClavasIntegration]]. The issue description below is based on the one found on that page, and subsequent discussions within the CMDI Taskforce.
     11=== CLAVAS ===
    1212
    13 == CLAVAS ==
    14 [http://openskos.org OpenSKOS] is a vocabulary service by which users may publish, manage and use SKOS-ified vocabulary data. The data can be accessed by a publicly available RESTful API. At this point only basic SKOS is supported. Also, some Dublin Core elements are included, but not indexed.
     13OpenSKOS is a vocabulary service by which users may publish, manage and use vocabulary data in the SKOS format. The data can be accessed by a set of publicly available RESTful API's. Also, some Dublin Core elements are included, but not indexed. CLAVAS is a CLARIN-NL's application of OpenSKOS, hosted by the Meertens Institute (contact is [[henniebrugman|Hennie Brugman]]). The vocabularies will be available through a set of web services hosted at Meertens, supporting exploration, search and autocomplete. More information is available in the [attachment:wiki:CmdiClavasIntegration:CLAVAS-Workplan-1.1.docx CLAVAS work plan document].
    1514
    16 CLAVAS is a CLARIN-NL's application of OpenSKOS. It is hosted by the Meertens Institute, contact is [[henniebrugman|Hennie Brugman]]. The vocabularies will be available through a set of web services hosted at Meertens. CLAVAS is based on [http://openskos.org OpenSKOS], where vocabularies map to 'concept schemes' in OpenSKOS. More information is available in the [attachment:wiki:CmdiClavasIntegration:CLAVAS-Workplan-1.1.docx CLAVAS work plan document].
    17 
    18 This page covers integration of CLAVAS with [[CmdiIndex|CMDI]]. The proposed workflow is that metadata modelers can associate a vocabulary (identified by its URI) with an element in their components and profiles. The metadata creator will then be able to pick values from the specified vocabulary or (in the case of open vocabularies) still choose to use a custom value that does not appear in the vocabulary. Editors like [http://tla.mpi.nl/tools/arbil Arbil] need to be extended to access the CLAVAS public API for retrieving potential values from vocabularies.
    19 
    20 PUBLIC API, FIND CONCEPTS, AUTOCOMPLETE
     15The proposed workflow is that metadata modellers can associate a vocabulary (identified by its URI) with an element in their components and profiles. The metadata creator will then be able to pick values from the specified vocabulary or (in the case of open vocabularies) still choose to use a custom value that does not appear in the vocabulary. Editors like [http://tla.mpi.nl/tools/arbil Arbil] need to be extended to access the CLAVAS public API for retrieving potential values from vocabularies.
    2116
    2217==== Available data ====
     18
     19Currently, the following vocabularies are available in CLAVAS:
    2320
    2421* '''Languages:'''
    … …  
    3229 *   OAI set: meertens:isocat
    3330
    34 == Solution description (proposed) ==
    35 This section the solution as proposed at Utrecht Taskforce Meeting 21.2.2014
     31== Description of proposed solution ==
     32This section describes the solution as proposed at the Taskforce Meeting in Utrecht on 2014-2-12.
    3633
    37 There are mainly 2 ways of using the OpenSKOS vocabularies in CMDI:
     34There are two ways of using the OpenSKOS vocabularies in CMDI:
    3835
    3936* Importing vocabularies as closed value domains for CMD_elements or Attribute. Since the vocabulary items are enumerated explicitly as a choice list in the elements in question, validation is possible.