> Thanks for the performance improvements. There still seem to
> be some delays with email distribution, but better than it was.
>
> Persistent, referenceable URLs for documents is highest on my list.
And mine - also that they be easily updateable from some kind of script
- in particular so that the issues list can be kept up-to-date. I have
tools that add links into the email archive for each issue, so can often
get several revisions a day (for the hyper-active bpel tc). At present
we cope with this using a separately-hosted "working copy" (ftp upload
from perl script) and upload (using the normal web interface) to the TC
pages once a week or so.
Also concur on the other points made - the absence of a tc->public back
link I find irritating too.
Having different URLs for a publically-available document accessed
publically and accessed as a member complicates things sometimes.
Peter
>
> Agree completely with others comments about the attendance
> tracking system.
>
> =bill
>
> -----Original Message-----
> From: Karl F. Best [mailto:]
> Sent: Tuesday, January 06, 2004 11:32 AM
> To: Chairs OASIS
> Cc: ;
> 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
>
>
> =================================================================
> Karl F. Best
> Vice President, OASIS
> office +1 978.667.5115 x206 mobile +1 978.761.1648
> http://www.oasis-open.org
>
>
>
