[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [Fwd: [chairs] need input for doc mgmt requirements]
Hi Eduardo, Karl said he's send out minutes. In the meantime here's an overview, and I've attached my notes. It was the beginning. I didn't realize this would be an ongoing effort. I thought it would be more of a follow-up to our previous feedback, perhaps one or two meetings, but it is really an entire effort to come up with a new system for doc management, and may be an ongoing effort until the system is in place, it seems. They discussed making it a separate TC, but that was ruled out. It's an ad-hoc committe for now and Karl is the Chair. Our next meeting is in two weeks. As Jon's message pointed out, one of the participants asked Karl to try to get more input from the TC chairs, since there were only about 6 chairs at the meeting. So that's what that mail is about. It's mostly focused on TCs that aren't involved in this yet, to make sure requirements are voiced now rather than finding out later they were missed. AIs for the participants were for us to send our requirements to the list, even if we had given them to Karl already. I need to weed out the Kavi issues from the real requirements for a doc management system. Kavi issues go a separate route (Karl mentioned he was setting up a separate meeting for those). I didn't get a list of all the people who attended because the roll call went very quickly. I asked for Karl to put together a list of who is in the meeting, but he said he didn't know himself who everyone was, since the participants were there because they apparently responded to a request for 'interested parties'. He said that if people identified themselves as they sent in the requirements he'd create a list, so hopefully by the next meeting I'll know who's who. So, for now, until some of the requirements hit the alias, it's still just getting under way. The meeting mostly covered procedural stuff. The person who suggested the BDM RFI (Carl Mattocks) did mention it, but Karl said it seemed a bit overkill for now, although he may take a look at it later. The other suggestion (webDAV) wasn't discussed at all. -Anne Eduardo Gutentag wrote: > Anne, > > how did the meeting go? Do you have a summary? > > -------- Original Message -------- > Subject: [chairs] need input for doc mgmt requirements > Date: Fri, 16 May 2003 17:38:24 -0400 > From: Karl F. Best <karl.best@oasis-open.org> > Reply-To: karl.best@oasis-open.org > Organization: OASIS > To: chairs@lists.oasis-open.org > > 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 > > -- Eduardo Gutentag | e-mail: eduardo.gutentag@Sun.COM Web Technologies and Standards | Phone: +1 510 550 4616 x31442 Sun Microsystems Inc. | 1800 Harrison St. Oakland, CA 94612 W3C AC Rep / OASIS TAB Chair
Kavi 15 May meeting discussion Karl: Many TCs, increasingly active. In past just provided ftp access. Then moved to Kavi system which includes doc repository. Have naming scheme. Looking for coherent system for managing docs. Is adhoc for now but need to formalize (create TC?) Scope: Manage docs and facilitate collaboration Structure: Ad hoc committee OK? Yes. Although do need mailing list. AI: Karl create mail list. Conduct business on email unless other meetings required. Prioritize requirements. AI: Everyone throw their requirements out to the list. Karl is starting point release for Kavi. Need separate requirements list for doc management. Karl as TC Chairs explicitly for their requirements. Karl will chair, Matt will be editor. Schedule: 2-3 months for completion, so 2-4 weeks to gather requirements. Discussion: Major requirements topics * Naming/versioning/long-term * Persistent names/URL/URN * Access/security * Collaborative development/review * Multi-part specs Broaden scope of what can be included as viewable documents. Better way to organize documents according to TC needs. Spec tools/templates/namingconventions codified more clearly. Every published official document to have a URN. Next meeting: Monday 2 June, 1:00 PT
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]