Goal: decide on implementation
- How will we implement tags?
- Option 1:As plain text that is appended to slide revisions and decks (e.g. tags: [mathematics, fibonacci, ...] or
- Pros:
- Cons:
- Option 2: as URIs that are already linked to further knowledge (RDF)?
- Pros:
- Cons:
- Other options? (Ali KhaliliRoy MeissnerMariano RicoAntje SchlafLuis )
- Option 1:As plain text that is appended to slide revisions and decks (e.g. tags: [mathematics, fibonacci, ...] or
- How do we save these tags?
- Option 1 - As part of the slide model in the MongoDB or
- Pros:
- Cons:
- Option 2 - as a separate DB (e.g. a Graph DB - read next section)
- Pros:
- Cons:
- Other options? (Ali KhaliliRoy MeissnerMariano RicoAntje SchlafLuis )
- Related:
- RML - http://rml.io/
- Karma - https://usc-isi-i2.github.io/karma/
- SparqlMap - https://github.com/tomatophantastico/sparqlmap/
- morph-xr2rml - https://github.com/frmichel/morph-xr2rml
- Option 1 - As part of the slide model in the MongoDB or
- How do we realize semi-automatic semantic annotation of decks and slides?
- Option 2 - Use LD-R semi-automatic annotating feature (API?) (Ali Khalili
- Pros:
- Cons:
- Option 3 - Implement our own function/service?
- Pros:
- Cons: Possibly takes more time? Reuse existing libraries?
- Other options? (Roy MeissnerMariano RicoAntje SchlafLuis Daniel Fernandes Rotger )
- Option 2 - Use LD-R semi-automatic annotating feature (API?) (Ali Khalili