Difference between revisions of "ADAPT2 RDF Binding"

From PAWS Lab
Jump to: navigation, search
(ER Models)
(ER Models)
Line 17: Line 17:
  
 
= ER Models =
 
= ER Models =
* [[Knowledge Tree RDF Binding|Knowledge Tree]] - course portal (<span style='color:green;'>--</span>|<span style='color:orange;'>--</span>|<span style='color:red;'>--</span>|<span style='color:black;'>--</span>)
+
* [[Knowledge Tree RDF Binding|Knowledge Tree]] - course portal (<span style='color:green;'>15</span>|<span style='color:orange;'>0</span>|<span style='color:red;'>1</span>|<span style='color:black;'>33</span>)
 
* [[WebEx RDF Binding|WebEx]] - application serving dissected examples (<span style='color:green;'>--</span>|<span style='color:orange;'>--</span>|<span style='color:red;'>--</span>|<span style='color:black;'>--</span>)
 
* [[WebEx RDF Binding|WebEx]] - application serving dissected examples (<span style='color:green;'>--</span>|<span style='color:orange;'>--</span>|<span style='color:red;'>--</span>|<span style='color:black;'>--</span>)
 
* [[PERSEUS RDF Binding|PERSEUS]] - adaptive functionality profider (<span style='color:green;'>--</span>|<span style='color:orange;'>--</span>|<span style='color:red;'>--</span>|<span style='color:black;'>--</span>)
 
* [[PERSEUS RDF Binding|PERSEUS]] - adaptive functionality profider (<span style='color:green;'>--</span>|<span style='color:orange;'>--</span>|<span style='color:red;'>--</span>|<span style='color:black;'>--</span>)

Revision as of 19:52, 19 May 2009

Ambox style.png

This page is under construction and requires cleaning

The main purpose of this effort is to map entity-relationship models of applications in ADAPT2 architecture to RDF. If necessary, appropriate comments would be given about models, schemata and vocabularies themselves.

Further work has the following structural units:

  • ER Models - describe individual adaptive applications. Each entity and relationship is supplied with a list of suggested RDF bindings
  • RDF schemata - describe classes and properties with suggested use in describing entities and relationships of applications. Each schema can have several vocabularies identified by prefixes

Tentative Conventions

  • Objects and Entities are shown in boldface
  • Properties and relationships - regular face
  • Schema is written in upper case, e.g. DC, vocabulary in lower case, e.g. dc, dcterms
  • A chain of Object/Property statements is abbreviated with the help of → (right arrow), e.g. rdf:Descriptionrdf:typerss:channel
  • Domain-Range pair of a Property is prefixed with :: (double colon) and connected by ⇒ (double rignt arrow), e.g. lom:annotation :: lom:LearningObjectlom:Annotation
  • RDF-serialization of an ER Element is implemented - Done
  • RDF-serialization of an ER Element is (arguably) unnecessary - Not
  • Decision on RDF serialization needs clarification - Clarify

ER Models

  • Knowledge Tree - course portal (15|0|1|33)
  • WebEx - application serving dissected examples (--|--|--|--)
  • PERSEUS - adaptive functionality profider (--|--|--|--)
  • QuizPACK - a package of parametrized quizzes in C (--|--|--|--)
  • CUMULATE - Centralized User Modeling Server (--|--|--|--)

RDF Schemata and Vocabularies

Polisemy AKA Equivalence

Among various RDF schemata and vocabularies there exist overlap in what they actually mean. For example, dc:title, rdf:label, and rss:title all mean the same. We will maintain (our) classes of equivalence as a reference to RDF homonyms.