Re: [chairs] How to handle applicants and disclosures re TC participation

["David Webber \(XML\)" <david@drrw.info>]

Toby,

I'm not sure this is entirely the right picture.

There's two thread's here - one side is the OASIS formal side,
that has to have certain ground rules to develop the formal
specifications.

The other side is the world.  There is nothing to stop
you creating related sites that are public that provide open
access to resources around an initiative.

So - you can have a link to your www.oBIX.org  from your
TC description page.  And you can have a freelists.org  hosted
general discussion list - or a SourceForge Dev list and so on,
and note that too.

I agree that the current Kavi-centric front door to OASIS site
is confusing and difficult to grok.  But that's a website design
issue - not a procedural issue.

I've been asking for Wiki style facilities within Kavi for a
while - but again - you can easily create a wiki and point
to that too.

Each TC will differ on how it needs to interact with the
broader world.  I do think having some uniformity and
predictability to how this is presented from the OASIS
frontdoor is good.   We clearly need to do more on
making public access better and easier.

It's not all easy though - look at the effort that went
into getting TC snapshots for the New Orleans
presentations.

Thanks, DW

----- Original Message ----- 
From: "Considine, Toby (Facilities Technology Office)"
<Toby.Considine@unc.edu>
To: "James Bryce Clark" <jamie.clark@oasis-open.org>; "Ian Robinson"
<ian_robinson@uk.ibm.com>
Cc: <chairs@lists.oasis-open.org>; <scott.mcgrath@oasis-open.org>;
<carol.geyer@oasis-open.org>
Sent: Tuesday, June 21, 2005 11:57 AM
Subject: RE: [chairs] How to handle applicants and disclosures re TC
participation


This increases the need (as oBIX has requested repeatedly) to have some sort
of public forum. The net affect of oBIX moving to OASIS has been in many
ways, a complete separation of the oBIX standards committee from any of the
larger industry it is a part of. Let's see now, under OASIS guidelines:

- No advertising of standard
- no conversation with outsiders
- no suggestion box (which is also a good recruting tool)
- no public BBS

All we need to do is remove the right-side menu on the OASIS site and our
isolation will be complete.

I understand the need to distinguish between foormal IP and other offerings
to deliver restriction-free standards. But somehow we are going overboard
and damaging our ability to bring industry consensus together that the OASIS
standard for [oBIX] is worth while. We may as well give up and conced the
standards entirely to the ad-hoc market standards and give up on
development.

"A goal is a planned conflict with the status quo." -Hyrum W. Smith
----------------------------------------------------------------------------
------------------------------------
Toby Considine
UNC