...
- VIVO-1528: It's true that VIVO bases most editing based on the type of the property. But for strings it's not clear which should be HTML edited, which not. At least 3 different solutions:
- Configuration property for deciding which editor should be applied
- Use data type for decision which editor should be used
- Application decides based on context, like most application do. That puts domain language knowledge in the templates
Violeta & Mike: We should reduce the use of the HTML/WYSIWYG editor anyway.
To do: Where in a common/popular ontology is the data range of the DOI declared as URL (data type restriction = URL). Fallback solution: URI. Christian Hauschke
Then there should be a PR for the bibontology. [http://bibliographic-ontology.org/ AND https://github.com/structureddynamics/Bibliographic-Ontology-BIBO]
Look into schema.org and how they define identifiers: https://schema.org/identifier ]
Christian: Proposing an identifier ontology
Mike: Maybe at Pidapalooza 2019 - Brian's session at the VIVO conference 2018 regarding the askupdated.sparql (https://github.com/search?q=org%3Avivo-project+askupdated.sparql&type=Code). We could start with ontology releases (with semantic versioning. which has its downsides).
- Clear process for ontology additions/changes:
- Make a local ontology
- If there's something that could be intersting to the VIVO community in general: Open up an issue in https://github.com/openrif/vivo-isf-ontology/
...