more requirements

["Karl F. Best" <karl.best@oasis-open.org>]

Here's a few more things that I thought of over the weekend.

Please remember to get your ideas for requirements sent in by the end of 
this week -- or better yet by mid week so that we can discuss them in 
our meeting on Friday.

-Karl


security
--------
- owner/submitter recorded as part of submission

- owner/submittter has rights to modify (make new version), but not
replace or delete (this is a permanent repository)

- TC chair, sec, editor has ?what? rights in directory


URL
------
- file has persistent identifier/URL regardless where the file (or
package) is actually stored.

- mechanism for resolving URNs embedded in schemas, etc.

- URL is compact; not full of database query string/characters


versioning/metadata
------------------
- uses OASIS file naming scheme (developed on TC chairs list; inlcudes 
draft, CS, OS, etc.); does the TC editor assign names, or can the doc 
mgmt system do this? Perhaps a checkbox at submission to specify name 
and stage, etc. then doc mgmt system checks for uniqueness, versioning, 
etc. The TC Admin owns all OS-level docs and assigns those names

- metadata includes filename, submitter/owner, TC, date
created/modified, IPR, etc.


legacy
------
- resolve current document addresses/URLs

- import existing docs from ftp and from Kavi; persistent names


files
------
- Multi-part files: a single spec can be composed of a number of files;
submitter can upload entire package, and can also upload/modify just one
of the files; user can download entire package.

- Doc can be any file type; package may contain any combination of file
types


interface/process
----------
- TC mail list notified when file/package submitted or modified;
notification includes metadata and link to download.

- Entry added to TC web page with new/modified file (page on TC's web
area is the entry point for all TC's docs.)

- web form (from any browser) is interface for submission/modification;
use Kavi account/pswd for authentication?

- doc mgmt area created for new TC when TC created in Kavi; chair/editor
permissions inherited from Kavi