PERSEUS RDF Binding - Revision history

Myudelson at 17:22, 19 May 2009

2009-05-19T17:22:27Z

Myudelson at 17:21, 19 May 2009

2009-05-19T17:21:49Z

Myudelson at 17:19, 19 May 2009

2009-05-19T17:19:18Z

Myudelson: /* See also */

2009-02-16T20:35:08Z

‎See also

Myudelson at 18:50, 16 February 2009

2009-02-16T18:50:00Z

Myudelson at 17:56, 16 February 2009

2009-02-16T17:56:21Z

Myudelson at 17:50, 16 February 2009

2009-02-16T17:50:12Z

Myudelson at 17:49, 16 February 2009

2009-02-16T17:49:30Z

Myudelson at 14:32, 16 February 2009

2009-02-16T14:32:15Z

Myudelson: New page: ADAPT² PServices (ADAPT² Personalization Services) - is an attempt to provide adaptive functionality to applications that lack it in a transparent manner. The main purpose o...

2009-02-16T14:30:49Z

New page: ADAPT² PServices (ADAPT² Personalization Services) - is an attempt to provide adaptive functionality to applications that lack it in a transparent manner. The main purpose o...

New page

[[ADAPT² PServices]] (ADAPT² 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.

== ER Model, Annotations and RDF Bindings==

[[ADAPT² PServices]] do not expose its model in RDF format. The only visible part is the annotations [[#pservice|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: @@
 {{ambox|type=clean | text=''This page is under construction and requires cleaning''}}
-This page describes [http://en.wikipedia.org/wiki/Resource_Description_Framework RDF] binding of [[Knowledge Tree]] data model as part of [[ADAPT2 RDF Binding]] initiative.
+This page describes [http://en.wikipedia.org/wiki/Resource_Description_Framework RDF] binding of [[PERSEUS]] data model as part of [[ADAPT2 RDF Binding]] initiative.
 == Overview ==

@@ Line 5: / Line 5: @@
 == ER Model, Annotations and RDF Bindings==
-[[ADAPT&sup2; PServices]] do not expose its model in RDF format. The only visible part is the annotations [[#pservice|PServices]] generate.
+[[PERSEUS]] does not expose its model in RDF format. The only visible part is the annotations [[#pservice|PServices]] generate.
 === ER Model ===

← Older revision		Revision as of 20:35, 16 February 2009
Line 30:		Line 30:

	== See also ==		== See also ==
		+	* [[PERSEUS]]
	* [[ADAPT2 RDF Binding]]		* [[ADAPT2 RDF Binding]]

@@ Line 1: / Line 1: @@
-{{ambox| text=''This page is under construction and requires cleaning''}}
+{{ambox|type=clean | text=''This page is under construction and requires cleaning''}}
 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.

← Older revision		Revision as of 17:56, 16 February 2009
Line 28:		Line 28:
	** [average] group progress -		** [average] group progress -
	** [average] group knowledge -		** [average] group knowledge -
		+
		+	== See also ==
		+	* [[ADAPT2 RDF Binding]]

← Older revision		Revision as of 17:49, 16 February 2009
Line 1:		Line 1:
		+	{{ambox\| text=This page is under construction and requires cleaning}}
	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.		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.		[[#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.

← Older revision		Revision as of 14:32, 16 February 2009
Line 1:		Line 1:
−	~~[[ADAPT² PServices]] (ADAPT² 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.		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.		[[#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.