Changes between Version 9 and Version 10 of CMDI 1.2/Vocabularies/Summary


Ignore:
Timestamp:
03/05/14 13:18:13 (10 years ago)
Author:
Twan Goosen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CMDI 1.2/Vocabularies/Summary

    v9 v10  
    99The 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
     11The desired 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.
     12
    1113=== CLAVAS ===
    1214
    1315OpenSKOS 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 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].
    14 
    15 The 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.
    1616
    1717Currently, the following vocabularies are available in CLAVAS: