OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

chairs message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [chairs] your input on OASIS functionality enhancements

Title: RE: [chairs] your input on OASIS functionality enhancements

Trivial request:

each TC has an internal "members only" home page, and an external "public" home page.  While I mostly need the internal for my work, when sending infomation to non-members I need the other.  I have not found any link that takes me from the internal to the external home page.  I have added such a link to the "notes" but it seems like this should be a generic part of the system.

-Keith Swenson

-----Original Message-----
From: Karl F. Best [mailto:karl.best@oasis-open.org]
Sent: Tuesday, January 06, 2004 8:32 AM
To: Chairs OASIS
Cc: jamie.clark@oasis-open.org; jeff.lomas@oasis-open.org
Subject: [chairs] your input on OASIS functionality enhancements

TC chairs and secretaries:

As I've done in the past, I would like to ask for your input on the
infrastructure and functionality provided by OASIS to the TCs.

Last spring we rolled out the new collaborative tools from Kavi,
including membership roster management, balloting, email lists, document
repository, action items, etc. While the rollout didn't go as smoothly
as we had hoped I think that we've got most of the bugs worked out.
We've recently updated the attendance notification scripts (and as a
reminder, these rely on your keeping your rosters and meeting attendance
current), and our IT staff has over the holidays upgraded the Kavi
software so you should see some significant performance improvements.

We have also recently launched the OASIS Standards Registry for the
purpose of sharing information about the status of our technical work.
We're asking our member organizations to submit information about their
implementations of OASIS TC specifications. We'll also be working on
synchronizing some aspects of the registry data with the information
stored in the Kavi database so that we don't have to enter identical
information in two places.

I've had on my list for some time now the development of a document
management system, including functionality for persistent URLs, version
control, checkin/out, etc. I gathered some input from you last spring
and summer, and we're going to resume putting together the design for
this system so that we can then start development. It's evident that
this functionality is needed by our TCs, and we want to be able to
deliver this soon.

I would like to hear from you what other functionality is crucially
needed by the TCs for their operation. While our development resources
are limited and so we must concentrate on those things most important to
the largest number of our members, we want to hear from you what sorts
of things we ought to be working on. (We would also be interested in
hearing about any development resources that any of our member companies
could contribute to our infrastructure efforts.)

Please reply to this list or to me directly over the next couple of
weeks so that we on the OASIS staff can make our development plans for
the rest of the year.


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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]