formal & explicit urn/url assignment

["Matthew MacKenzie" <matt@yellowdragonsoft.com>]

Title: Message

Sorry if this requirement includes a proposed solution, that is a habit of mine :-)

 

REQUIREMENT

 

I would like to see a simple tool that integrates to kavi and provides a way of formally assigning a URN to a document, and using a uniform URL structure provides access to the document at its actual, Kavi-managed location.

 

SOLUTION

 

So, given that the ebxml-msg SOAP extension schema is actually located at http://www.oasis-open.org/kavi/somephpscript.php?did=3e77jjdjjd, the new script would provides a URL like:

 

http://names.oasis-open.org/ebxml-msg/schema/2_0 and transparently forward to the actual location.  TC chairs and secretaries would be able to setup forwarding for any publicly published document.

 

This could be easily implemented using a PHP script and one database table.  I beleive this would solve some other problems as well.

 

-Matt

 

-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Monday, May 19, 2003 9:47 AM
To: doc-mgmt@lists.oasis-open.org
Subject: [doc-mgmt] Re: [chairs] need input for doc mgmt requirements

A requirement that I notice is missing is for a stable URL to point to the latest revision of a document. This will often be useful on public pages and press releases.

Rich Thompson

"Karl F. Best" <karl.best@oasis-open.org> 05/16/2003 05:38 PM Please respond to karl.best

To:        chairs@lists.oasis-open.org         cc:                 Subject:        [chairs] need input for doc mgmt requirements

Chairs:

Today we had a meeting for the ad hoc doc management committee, whose
purpose is to gather requirements and define a solution for management
of TC documents at OASIS. I had sent out a call for this several weeks
ago, first to the chairs then to the members. (Attached below is a copy
of that initial call, to remind you what this project is about.) Today's
call was composed of people who expressed interest in participating in
the project.

The participants in today's call were asked to, over the next two weeks,
send in the suggestions for requirements for doc management at OASIS. It
was suggested that I ask you, the leaders of the TCs, to also submit
your suggestions. Even if you aren't interested or don't have the time
to help refine the suggestions for requirements you could still
contribute items.

If you have any ideas please send them to doc-mgmt@lists.oasis-open.org
(this is a moderated list, so you don't have to be subscribed).

-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





-------- Original Message --------
Subject: need input on doc mgmt at OASIS
Date: Thu, 24 Apr 2003 14:07:05 -0400
From: Karl Best <karl.best@oasis-open.org>
Reply-To: karl.best@oasis-open.org
Organization: OASIS
To: "'chairs@lists.oasis-open.org'" <chairs@lists.oasis-open.org>
CC: robin cover <robin.cover@oasis-open.org>, Jeffrey Lomas
<jeff.lomas@oasis-open.org>

Chairs:

Now that we've got the new collaborative tools (Kavi) up and running --
though with a few minor fixes still required, we're thinking about the
next bit of major functionality that we need to provide to our TCs.
We're aware that the Kavi tools don't provide the complete functionality
that we need for management of documents produced by the TCs, so would
like to address this problem next.

For a long time we've been using ftp so the TCs could manage their own
docs, which has pros and cons. The Kavi tools provide some level of
functionality, but not everything that we need. We've also got a
registered URN name space but no way to manage or administer this.

We need an integrated solution that will allow us to do the following:

* allow the TCs to manage all of their docs in a consistent manner
* require permissions for different types of people (members, chairs,
public, etc.) to perform different functions
* use the just-completed doc naming scheme (from the chairs mail list)
* use the OASIS URN namespace, and provide some mechanism for
administering this
* ensure persistent URLs, both for existing docs and into the future
* include a CVS collaborative development environment
* take advantage of at least some of the 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.

This is certainly not a complete list of requirements, but just some of
the things I can think of off the top of my head. Some issues are
related to functionality, others to usability; we need to address both.

All of this is more than we here on OASIS staff are going to be able to
solve, and as you, the TC chairs, are the users of most of this we need
your input and expertise.

I would like to assemble a small, ad hoc committee of OASIS members that
could help us come up with first a list of requirements that we would
then circulate for comment, then a proposed solution that we would also
circulate for comment before starting to build a solution.

If you are interested in helping with this project please let me know.
If there are people in your TC that you think might be interested or
have expertise in this area please forward this to them and ask them to
respond to me. I'd like to get this going soon, as there is a fairly
urgent need to have this problem solved.

thanks
-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



---------------------------------------------------------------------
To unsubscribe, e-mail: chairs-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: chairs-help@lists.oasis-open.org