Difference between revisions of "PAWS"
Line 1: | Line 1: | ||
− | = | + | = About PAWS = |
+ | Personalized Adaptive Web Systems Lab was established in 2004 with support from National Science Foundation and School of Information Sciences. The goal of the PAWS Lab is development and evaluation of innovative user- and group-adaptive Web-based technologies, systems, and architectures. The Lab currently explores a range of user modeling, adaptation and personalization technologies. The work of the Lab is supported by NSF and DARPA funding. | ||
+ | |||
The main purpose of this wiki is to map entity-relationship models of applications in [http://www.sis.pitt.edu/~paws/project_adapt2.htm ADAPT² architecture] to RDF. If necessary, appropriate comments would be given about models, schemata and vocabularies themselves. | The main purpose of this wiki is to map entity-relationship models of applications in [http://www.sis.pitt.edu/~paws/project_adapt2.htm ADAPT² architecture] to RDF. If necessary, appropriate comments would be given about models, schemata and vocabularies themselves. |
Revision as of 18:58, 12 February 2009
About PAWS
Personalized Adaptive Web Systems Lab was established in 2004 with support from National Science Foundation and School of Information Sciences. The goal of the PAWS Lab is development and evaluation of innovative user- and group-adaptive Web-based technologies, systems, and architectures. The Lab currently explores a range of user modeling, adaptation and personalization technologies. The work of the Lab is supported by NSF and DARPA funding.
The main purpose of this wiki is to map entity-relationship models of applications in ADAPT² architecture to RDF. If necessary, appropriate comments would be given about models, schemata and vocabularies themselves.
This wiki 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
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:Description→rdf:type→rss:channel
- Domain-Range pair of a Property is prefixed with :: (double colon) and connected by ⇒ (double rignt arrow), e.g. lom:annotation :: lom:LearningObject⇒lom:Annotation
- ER Element is RDF-serialized - ✓ (green check-mark)
- RDF Serialization of ER Element is arguably unnecessary - ✗ (red ballot X)
- Decision on RDF serialization needs clarification - ?¿ (bold blue question mark and inverted question mark)
ER Models
- Knowledge Tree - course portal
- WebEx - application serving dissected examples
- ADAPT² PServices - adaptive functionality profider
- QuizPACK
- CUMULATE - Centralized User Modeling Server
RDF Schemata and Vocabularies
- RDF - has single vocabulary rdf
- RDFS - has single vocabulary rdfs
- OWL
- Dublin Core - has vocabularies dc, dcterms, dcmitypes
- RSS - has single vocabulary rss (here we mean RSS v.1.0)
- FOAF - has single vocabulary foaf
- LOM - has vocabularies lom, lomvoc, lomstruc, lomagglvl, lomstatus, lominttype, lomlrtype, lomintlvl, lomsemden, lominteur, lomcon, lomdiff, lomrole, lombrotech, lomostech, lompurp
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.