User talk:Harikrishna/Phases/1 - Revision history

Harikrishna: User talk:Harikrishna/Phases/1/ moved to User talk:Harikrishna/Phases/1

2008-08-28T09:52:50Z

User talk:Harikrishna/Phases/1/ moved to User talk:Harikrishna/Phases/1

Harikrishna: User talk:Harikrishna/Phase 1 : Focus on global context and user productivity moved to User talk:Harikrishna/Phases/1/

2008-08-28T09:33:51Z

User talk:Harikrishna/Phase 1 : Focus on global context and user productivity moved to User talk:Harikrishna/Phases/1/

Harikrishna at 12:57, 27 August 2008

2008-08-27T12:57:16Z

Dhaumann: Phase 1 : Focus on global context and user productivity moved to User talk:Harikrishna/Phase 1 : Focus on global context and user productivity: subpage

2008-08-27T12:24:21Z

Phase 1 : Focus on global context and user productivity moved to User talk:Harikrishna/Phase 1 : Focus on global context and user productivity: subpage

Harikrishna at 11:41, 27 August 2008

2008-08-27T11:41:58Z

Harikrishna at 11:39, 27 August 2008

2008-08-27T11:39:34Z

Harikrishna: New page: -- Activity Context 1). I think "Activity" should be the central context of interest. All other contexts exist just to help the user be more productive and focus on his "Activity" 2). ...

2008-08-27T11:38:53Z

New page: -- Activity Context 1). I think "Activity" should be the central context of interest. All other contexts exist just to help the user be more productive and focus on his "Activity" 2). ...

New page

-- Activity Context
1). I think "Activity" should be the central context of interest. All other contexts exist just to help the user be more productive and focus on his "Activity"

2). User manually creates activities, and can possibly associate semantics to it by special "template tags" (which can be templates for settings, file attributes, apps used in activity, etc), instead of current passive tags used just for linking data.

3). when the user switches activities, the whole environment changes to focus the attention of the user on the related things and auto-tags the resources used (like files created, etc) with the activity.

-- Other Sub Contexts
1). We can just listen to system-wide events (location, resources ) via listeners, send them to User Observation Hub which just broadcasts it

2). System adjusts the focus or auto-tagging according to the subcontexts, if needed

@@ Line 1: / Line 1: @@
 === Activity Context ===
-) I think "Activity" should be the central context of interest. All other contexts exist just to help the user be more productive and focus on his "Activity"
+I think "Activity" should be the central context of interest. All other contexts exist just to help the user be more productive and focus on his "Activity"
 ) User manually creates activities, and can possibly associate semantics to it by special "template tags" (which can be templates for settings, file attributes, apps used in activity, etc), instead of current passive tags used just for linking data.
 ) when the user switches activities, the whole environment changes to focus the attention of the user on the related things and auto-tags the resources used (like files created, etc) with the activity.
 === Other Sub Contexts ===

@@ Line 1: / Line 1: @@
--- Activity Context
+=== Activity Context ===
-).  I think "Activity" should be the central context of interest. All other contexts exist just to help the user be more productive and focus on his "Activity"
+) I think "Activity" should be the central context of interest. All other contexts exist just to help the user be more productive and focus on his "Activity"
-).  User manually creates activities, and can possibly associate semantics to it by special "template tags" (which can be templates for settings, file attributes, apps used in activity, etc), instead of current passive tags used just for linking data.
+) User manually creates activities, and can possibly associate semantics to it by special "template tags" (which can be templates for settings, file attributes, apps used in activity, etc), instead of current passive tags used just for linking data.
-). when the user switches activities, the whole environment changes to focus the attention of the user on the related things and auto-tags the resources used (like files created, etc) with the activity.
+) when the user switches activities, the whole environment changes to focus the attention of the user on the related things and auto-tags the resources used (like files created, etc) with the activity.
--- Other Sub Contexts
+=== Other Sub Contexts ===
-). We can just listen to system-wide events (location, resources ) via listeners, send them to User Observation Hub which just broadcasts it
+) We can just listen to system-wide events (location, resources ) via listeners, send them to User Observation Hub which just broadcasts it
-). System adjusts the focus or auto-tagging according to the subcontexts, if needed
+) System adjusts the focus or auto-tagging according to the subcontexts, if needed
-Realisation :
+=== Realisation ===
 ) We need to finalise the exact model of the concerned contexts,

← Older revision		Revision as of 11:39, 27 August 2008
Line 10:		Line 10:

	2). System adjusts the focus or auto-tagging according to the subcontexts, if needed		2). System adjusts the focus or auto-tagging according to the subcontexts, if needed
		+
		+
		+	Realisation :
		+	1) We need to finalise the exact model of the concerned contexts,
		+
		+	2) need to come up with how the system adjusts itself to focus on activity depending on subcontexts and
		+
		+	3) possibly come with guidelines on how the applications would auto-tag associated resources (keeping in mind the corner cases)