| 8 | | The issue is about utilising external vocabularies as value domains for CMDI elements and CMDI attributes (i.e. Attribute elements) |
| 9 | | |
| 10 | | 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 discussion within the CMDI Taskforce. |
| 11 | | |
| 12 | | [http://openskos.org OpenSKOS OpenSKOS] is a vocabulary service offering facilitating publication, management and use of SKOS-ified vocabulary data. The data can be accessed by a RESTful API. At this point only basic SKOS is supported. Also, some DC elements are included, but not indexed. |
| | 8 | 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. |
| | 9 | |
| | 10 | 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 | |
| | 12 | == CLAVAS == |
| | 13 | [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. |
| 21 | | |
| 22 | | A [http://editor.openskos.org/api public API] that allows one to search for concepts within a ConceptScheme (vocabulary) is available. |
| 23 | | |
| 24 | | The [http://openskos.org/api#autocomlete autocomplete API] can be used to get all items in an identified vocabulary or a subset in JSON or RDF by providing the URI of a vocabulary as a parameter. |
| | 22 | The [http://openskos.org/api RESTful API] complies with the [http://lucene.apache.org/core/2_9_4/queryparsersyntax.html Apache Lucene Query Parser Syntax]. |
| | 23 | This allows one to search for concepts within a ConceptScheme (vocabulary). |
| | 24 | |
| | 25 | In addition the vocabulary data may be harvested from an OAI-PMH endpoint, at which the data are organised in sets corresponding to individual vocabularies. |
| | 26 | |
| | 27 | ===== Find concepts ===== |
| | 28 | |
| | 29 | Example queries: |
| | 30 | * Languages which prefLabel starts with "Norw": [https://openskos.meertens.knaw.nl/api/find-concepts?q=inScheme:http*iso-639-3 AND prefLabel:Norw*&format=rdf] |
| | 31 | * Languages which code starts with "no": [https://openskos.meertens.knaw.nl/api/find-concepts?q=inScheme:%22http://openskos.meertens.knaw.nl/iso-639-3%22 AND notation:no*] |
| | 32 | * Concepts which prefLabel is "Norwegian University Press" (in any vocabulary): [https://openskos.meertens.knaw.nl/api/find- concepts?q=prefLabel:%22Norwegian%20University%20Press%22] |
| | 33 | |
| | 34 | ===== Autocomplete ===== |
| | 35 | |
| | 36 | The [http://openskos.org/api#autocomlete autocomplete API] is a simplified version of Find concepts, by which single property values may be retrieved as a list. However, delimiting search to individual vocabularies doesn't appear to be possible with autocomplete. |
| | 37 | |
| | 38 | Example query: [https://openskos.meertens.knaw.nl/api/autocomplete/Norw?returnLabel=prefLabel&searchLabel=prefLabel] |
| | 39 | |
| | 40 | There is also an autocomplete variant of Find concepts, for example: |
| | 41 | * Languages which prefLabel starts with "Norw": [https://openskos.meertens.knaw.nl/api/find-concepts?q=inScheme:%22http://openskos.meertens.knaw.nl/iso-639-3%22 AND prefLabelAutocomplete:Norw] |
| | 42 | |
| | 43 | ===== Harvesting ===== |
| | 44 | |
| | 45 | Example query: |
| | 46 | * The entire vocabulary of languages in rdf format: [https://openskos.meertens.knaw.nl/oai-pmh?verb=ListRecords&set=meertens:iso-639-3&metadataPrefix=oai_rdf] |
