[Zope-Moz] Design discussion (was RDF Use cases)

[Brian Lloyd]

> > I propose that we adopt "Role Verbs Noun" as the title of use cases.
> > For instance, "Content Manager Edits Document" or "Manager Adds
> > Portal".  We then discuss the sequence of activities and 
> branches for
> > each use case.
> 
> I see that few of the use cases I suggested look like this. 
> Now I feel I need
> more inputs before I can provide constructive suggestions.
> 
> 1. What should be the set of actors for the use cases?
> How about these: administrator, content manager, database 
> programmer, zope
> developer, zope studio, zope itself, web-browser.

I suggest that Zope Developer and Content Manager are the 
main actors that we will be worrying about given the scope
of the project (below).


> 2. Are we looking at use of RDF in Zope or 'use cases' for 
> the Zope Studio?

The scope of the current project is "to develop an extensible
framework for the production of RDF data from Zope objects", 
not to define an eventual "Zope Studio". 


> If its RDF in Zope (anywhere in Zope) then things like privacy 
> preferences and signatures (interactions between the browser and 
> zope) would make sense here.

I don't totally agree - things like privacy prefs or signatures 
are *application-level* things that will be done with the 
framework that we are trying to design. The use cases for those
particular applications are not really relevant *except* where
they spawn specific requirements (use cases) on the framework 
design.

To take privacy preferences as an example, the only use case 
that really relates to the *framework* might be:

  o Zope developer implements Privacy vocabulary

...the rest is specific to the application domain and imposes 
no required behavior on the framework that supports the production
of RDF.


Brian Lloyd        brian@digicool.com
Software Engineer  540.371.6909              
Digital Creations  http://www.digicool.com