[TagCommons-WG] Actors in TagCommons use cases

[Nitin Borwankar]

All,

Some of the discussions so far have, IMHO, been coming from the 
viewpoints of different actors in the TagCommons universe.
It may be useful to explicate them as distinct entities.   They have 
different concerns and some of them have been expressed stronger than 
others.

To wit,

a) Tagging site builder:  incorporates tagging schema and API into 
domain model and provides web service as well as human UI for tagging.

b) (Non-web) Tagging application builder: incorporates tagging schema 
and API into domain model and provides developer API as well as human Ui 
for tagging.

c) Tagging site user: uses tagging UI of site to create taggings local 
to site.

d) (Non-web) Tagging app user: uses tagging UI of non-web app to create 
taggings local to app.

e) Tagging mashup creator: integrates multiple web services into a (we 
hope :-) ) coherent application that produces/consumes tags.

f) Tagging mashup user: uses mashup to produce/consume tags.

g) Tagging middleware creator: builds libraries/apps that connect 
non-web tagging applications to web based tagging application ( such as 
between a desktop bookmark manager and the del site )

h) Tagging middleware user: uses tagging middleware to integrate non-web 
and web applications either as a developer of the non-web app or merely 
as a "system integrator"

A number of subjects, including some of those I have expressed, speak 
narrowly to the concerns only one or two of these actors at a time.
I believe we may need to be clearer about which hat we are wearing when 
we talk about why things should be done one way and not another.
And we may need to balance a number of competing concerns.

-- 
Nitin Borwankar

http://greener.com
Find, Learn, Act .... Greener, the search engine for the planet

http://tagschema.com
Implementation of tag database applications

nitin at borwankar.com
510-872-7066