[ubl-csc] [Fwd: [chairs] Member interface launch 17 March; needsattention; future plans]

["Eve L. Maler" <eve.maler@sun.com>]

I don't know if all the UBL SC chairs are on the OASIS chairs list.  In 
case you're not, here's an urgent notice regarding Kavi...

	Eve

-------- Original Message --------
Subject: [chairs] Member interface launch 17 March;  needs attention; 
future plans
Date: Fri, 14 Mar 2003 14:50:20 -0800
From: James Bryce Clark <jamie.clark@oasis-open.org>
To: chairs@lists.oasis-open.org

      Per Karl's message, we are completing the initialization of the OASIS
member interface and its back-end database, and plan to launch officially
on Monday.
      As discussed on this list -- at some length -- when we flip the
switch, the definitive membership database also will control access to
OASIS mailing lists.  A fair number of TC chairs have not yet signed in to
review their TC membership lists.  The critical path for implementation
requires each chair to confirm the voting/observer status of each TC
participant.  The system also allows a properly-designated TC secretary
(might be a subordinate officer, vice-chair, etc.)  to do this *for* you.
      In the short run, failure to do so will result in legitimate members
being locked out from posting temporarily.  This would be disappointing and
perhaps disruptive to ongoing substantive work.  We ask each of you to make
it a first priority to enter your voting member designations.  I will
contact you to follow up on the status of your TC's membership roster next
week.
      Please note that we will launch the DB and access system with its
basic set of capabilities, as described in our announcements and training
sessions.   As also discussed -- a lot -- there may be functions that have
less granularity than some might like.
      Adoption of the interface software, like our work on shared document
naming rules, necessarily does constrain some of our activities into
taxonomies and normative locations.  There will be initial mapping issues,
and we are sensitive to persistent URI needs.  Still, we view this as a
positive and necessary step towards greater  transparency to our members
and to the target users of OASIS deliverables.  Effective, scalable access
to our rapidly-growing body of work always has been a core OASIS goal.  As
we get bigger and more diverse, it becomes more complex and even more
strategically important to do it well.
      We are receiving helpful comments and suggestions on this [chairs]
list, and off-sides.  We anticipate a second stage of tweaks and possible
extensions within a few months of the initial launch date.  As previously
announced, in order to preserve backward compatibility, we will co-locate
most pre-launch work product at its prior location as well as a new
DB-managed location during this interim period.  During that time our
community will explore and discuss persistent aliasing or cross-referencing
approaches.  This is the kind of challenge we should enjoy having.  It
results from our collective body of work being sufficiently large, dense
and archival to need careful planning.
      Obviously, we need and welcome your continued feedback.  Our task is
to maintain and refine good practices and procedures that work both for 50+
existing TCs, and for the many others who come to us and evaluate our
capabilities as a productive, open, fair, functional and effective platform
for their standards work.

Best regards
Jamie Clark
OASIS Open
+1 978 667 5115 x 203



----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>


-- 
Eve Maler                                        +1 781 442 3190
Sun Microsystems                            cell +1 781 354 9441
Web Technologies and Standards               eve.maler @ sun.com


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>