PERSEUS RDF Binding

This page is under construction and requires cleaning

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

PERSEUS does 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 -

See also

• PERSEUS
• ADAPT2 RDF Binding