UBL & Kavi - [Fwd: concall for doc mgmt ad hoc committee]

[Anne Hendry <anne.hendry@sun.com>]

  Hi,

I've been 'elected' ;) to represent UBL in this effort.  I'd like to make
sure our concerns/requirements are adequately described.  Karl has listed
below a summary of what he perceives to be the main requirements for an
OASIS system that would adequately support our needs.

There is a meeting this Friday is to review the requirements, so I'd like
to make sure I have the UBL TC's concerns included by then.  If you have
anything you'd like to add to the requirements that Karl has listed below
please let me know.  I'll go through the previous list we put together
as well, but there may have been some things that have come up in the
meantime.

If you'd rather I send this request to any full sc membership,
rather than task you with collecting it to your particular SC,
please let me know.  I just want to make sure that there are no
lingering undocumented issues after Friday.

Thanks,
Anne

-------- Original Message --------
Subject: concall for doc mgmt ad hoc committee
Date: Mon, 12 May 2003 09:33:53 -0400
From: "Karl F. Best" <karl.best@oasis-open.org>
Reply-To: karl.best@oasis-open.org
Organization: OASIS
To: karl.best@oasis-open.org
CC: klawrenc@us.ibm.com, rexb@starbourne.com, drummond.reed@onename.com, 
matt@yellowdragonsoft.com, jik@jkeane.com, marc.andrue.goodner@sap.com, 
Michael.Debellis@consulting.fujitsu.com, jharrop@speedlegal.com, 
john.kemp@earthlink.net, CarlMattocks@CHECKMi.com, 
Sumeet.Malhotra@unisys.com, stan.swaren@cgi.com, ndw@nwalsh.com, 
anne.hendry@sun.com, marc.lemaitre@onename.com, Jeffrey Lomas 
<jeff.lomas@oasis-open.org>
References: <3EB635AA.1050800@oasis-open.org> 
<3EB8AED7.1010307@oasis-open.org> <3EBAA05A.90302@oasis-open.org>



All:

Let's have a concall for our doc mgmt ad hoc committee.

Friday 16 May, 1:00 PT / 4:00 ET.
Conference Dial-in:	+1 512-225-3050
Conference Guest Code:	84759

As this is an ad hoc committee I'm not going to worry about membership 
or attendance or etc. We can conduct our email correspondence using a 
list of CC'd addresses, rather than setting up a mail list. We can 
discuss the schedule for future calls at the end of Friday's meeting.

Our discussion should follow these three phases:
1. gather requirements for a doc mgmt system at OASIS
2. design a system around the requirements
3. look for solutions for OASIS to build or buy

Known requirements are as follows:

* allow the TCs to manage all of their docs in a consistent manner
* allow multi-part specifications (made up of mulitple documents); 
ability to manage collectively and individually
* require permissions for different types of people (members, chairs,
public, etc.) to perform different functions
* use the just-completed doc naming scheme (discussed by the TC chairs) 
for the various stages of a doc's life
* use the assigned OASIS URN namespace, and provide some mechanism for
administering this (both assigning and resolving names)
* ensure persistent URLs, both for existing docs and into the future, so 
that docs can be referenced both during development and after publication
* include a CVS collaborative development environment
* take advantage of at least some of the collaborative tools (Kavi) doc
repository functionality (notification of TC members, etc.)
* provide for long-term archiving of completed and approved OASIS Standards
* provide adequate security for the server and files located there

In addition, whatever we come up with needs to be built using limited
or donated resources, and needs to run on existing OASIS server resources.



-Karl

=================================================================
Karl F. Best
Vice President, OASIS
office  +1 978.667.5115 x206     mobile +1 978.761.1648
karl.best@oasis-open.org      http://www.oasis-open.org