Difference between revisions of "PERSEUS RDF Binding"

Revision as of 14:32, 16 February 2009

Each PService can be set up to use several data sources - configurations. Annotations each PService provides can either be used as is, in the form of RDF, or can be interpreted. Interpretation is provided by visualizers and syndicators. Both visualizers and syndicators do the same work, but at a different level of granularity. Visualizers only interpret a piece of annotation PService associates with resource or a feed. Syndicators in addition encapsulate access to the resource feed(s) in the form of user interface.

ER Model, Annotations and RDF Bindings

ADAPT² PServices do not expose its model in RDF format. The only visible part is the annotations PServices generate.

ER Model

pservice - Personalization Service itself
- pservice name - name of PService
- pservice description - description of PService
- pservice classname - class that implements PService Functionality
- pservice hasConfiguration - related data configurations
[data] configuration - data configuration that PService can use
visualizer - PService annotation interpreter
syndicator - PService annotation interpreter

Annotations

personal level annotations - describe user
- personal attempt count -
- personal progress -
- personal knowledge -
group level annotations - describe group user is part of (e.g. class)
- [average] group attempt count -
- [average] group progress -
- [average] group knowledge -

@@ Line 1: / Line 1: @@
-[[ADAPT&sup2; PServices]] (ADAPT&sup2; Personalization Services) - is an attempt to provide adaptive functionality to applications that lack it in a transparent manner.
-The main purpose of [[#pservice|PServices]] is to provide personalized annotations (e.g. navigation support) to various [collections of] resources. Naturally, the principal objects that [[#pservice|PServices]] operate on are [[RSS]] feeds. Upon invocation [[#pservice|PService]] enriches otherwise "plain" resource feed with personalized information, such as: progress, knowledge, or social cues. [[#pservice|PService]] relies upon external data sources such as User Model, class schedules, etc. to deliver adaptive value. All data in and out of [[#pservice|PService]] is in RDF format.
 Each [[#pservice|PService]] can be set up to use several data sources - [[#configuration|configurations]]. Annotations each [[#pservice|PService]] provides can either be used as is, in the form of RDF, or can be interpreted. Interpretation is provided by [[#visualizer|visualizers]] and [[#syndicator|syndicators]]. Both [[#visualizer|visualizers]] and [[#syndicator|syndicators]] do the same work, but at a different level of granularity.
 [[#visualizer|Visualizers]] only interpret a piece of annotation [[#pservice|PService]] associates with resource or a feed. [[#syndicator|Syndicators]] in addition encapsulate access to the resource feed(s) in the form of user interface.