Page Comparison

Proposal (work in progress - please participate):

Concrete tasks for the near future (and deliverable 2.3):

• Design a proper and user friendly tagging view - Abi James and Klaas Andries de Graaf
• Implement frontend part that enables users to tag slides/decks and to help them finding existing tags - maybe Klaas Andries de Graaf ?
• Research and implement a program that analyzes slides/decks to find topics that will appear as tags - Antje Schlaf is already working on it
• Save tags as ??? somewhere (MongoDB or separate GraphDB?) - maybe Roy Meissner
• Link tags to further knowledge (from the internet) - Mariano Rico was interested, Antje Schlaf will also participate
• Transfer tags from SlideWiki V1 DB to SlideWiki V2 DB - Darya Tarasowa should be best for this job
• ???

Open Questions:

• How will we implement tags? As plain text that is appended to slide revisions and decks (e.g. tags: [mathematics, fibonacci, ...] or as URIs that are already linked to further knowledge (RDF)?
  • for the second option: How do we make sure that the concept is distinct, so we can link it to further knowledge? E.g. someone tags a slide with "bench" .... did he meant furniture or law (maybe not the best example in English)
  • how do we handle distinct concepts in case we 
  • for the second option: How do we save these tags? As part of the slide model in the MongoDB or as a separate DB (e.g. a Graph DB - read next section)
  • for the second option: Do we want to show to users that they are working with RDF (e.g. by showing them URIs)?
  • ???
• ???

Concrete Tasks for the future:

We wrote in D2.1 that we want to "semantify" the whole SlideWiki by transferring all of the data to a (or more than one) RDF graph. Is this still valid?

If yes, we could save tags already as part of a GraphDB, that covers a simplified set of the MongoDB (Slide ID and Deck ID to tags). → Starting point for future work (future deliverables)

How do we want to include RDFa into the SlideWiki frontend?

Real use cases for the semantic representation:

• Interlink several SlideWiki instances (in case we implement versioning as part of the data store)
• ???

Academic use cases for the semantic representation:

• Having a Slide/Deck ontology at http://lov.okfn.org/dataset/lov that can be used by other researches/developers
• Having another open SPARQL endpoint with lot's of data
• Semantic description of service APIs (Topic service description)

...