...
- CERIF2VIVO
- Review sprint
- Scheduling: https://docs.google.com/spreadsheets/d/1_t0Oqe-GRWeNBN-IYatD4iKR6fE1dLwfyTGokVskZ7Y/edit - Christian Hauschke
- Procedure documentation: Mapping precision vocabulary, comment column, status column, reviewer column, communication, veto column
- Christian will prepare a table for the review process
- Dragan will review the structure table with someone with VIVO experience. The types can be done without deeper CERIF experience
- Review sprint
- Instantiated graph example for the key property 'claim_publications_by' (proposal) - Michel Héon / Dragan Ivanovic
- Issues:
- Using SKOS: Originally, VIVO was designed around the manipulation of rdfs:label. This approach was sufficient in a single language context. In the i18n context it is advantageous to have access to a label prioritization mechanism as well as to be able to use a label (or its URL) as a 'subject' to a triplet. The use of SKOS offers these advantages.
- Suggestion by Brian: Postpone this question, first it has to be decided on how a future I18N architecture could look like.
- Michel: Using SKOS would be a first step to using deep learning or pattern matching tools.
Individual IRI: Two approaches are possible for the generation of an IRI, either an approach based on the generation of a random value, or a value respecting a pattern. In both cases the IRI must be unique.
Institutional labelling: In addition to supporting labeling features differentiating between regions, packages (VIVO/VITRO/languages) and themes, the labeling ontology allows for institutional labeling overload. See
:claim_publications_by.vivo-languages-uqamfor UQAMConcerned files tracking: In the process of adding a new linguistic context it is often necessary to contextualize the translation according to the originating files and displays of the text.
The propertiesUrl and ftlUrl data properties contain the values necessary to identify the use of the key
- Using SKOS: Originally, VIVO was designed around the manipulation of rdfs:label. This approach was sufficient in a single language context. In the i18n context it is advantageous to have access to a label prioritization mechanism as well as to be able to use a label (or its URL) as a 'subject' to a triplet. The use of SKOS offers these advantages.
- It's currently unclear where the gains of implementing this ontology. Other approaches might be of more impact for the application.
- Issues: