[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [chairs] RE: [members] OASIS member review of proposedrevision of TC Process
The more I think about this, the more onerous it becomes. I understand the need to have accountability that is underneath this requirement, but compatibility with previous efforts tends to make it unworkable as an absolute restriction. There are also external efforts associated with TC standards efforts, such as FreebXML hosted on SourceForge, as are other efforts, where testbeds are required to test the workability and interoperability of standards, quite apart from associated collateral materials that we development as individuals or as companies, things like white papers, glossaries, etc., that are not strictly OASIS contributions but which form part of the bulwark of materials that support a standard or set of standards and are indispensable to promotion and adoption of a standard. This all requires much more thought. Ciao, Rex At 9:21 AM -0400 10/14/04, Norman Walsh wrote: >/ Matthew MacKenzie <mattm@adobe.com> was heard to say: >| "All resources of the TC and its associated >| subcommittees, including web pages, documents, email >| lists and any other discussions, must be located only >| on facilities provided by OASIS; TCs and SCs may not >| conduct business or technical discussions, store >| documents, or host web pages on non-OASIS servers. All >| web pages, documents, and email archives of all TCs >| and SCs shall be publicly visible." >| >| So...will OASIS also be providing us with email accounts? I suggest >| softening this passage considerably because at the end of the day if >| OASIS restricts the tools we use, many of us will end up finding a >| new home for our standards work. > >Indeed. Quoting the message I sent to the review list[1] before I >noticed that discussion was taking place here: > >> All resources of the TC and its associated subcommittees, including >> web pages, documents, email lists and any other discussions, must be >> located only on facilities provided by OASIS; TCs and SCs may not >> conduct business or technical discussions, store documents, or host >> web pages on non-OASIS servers. >> >>By a strict interpretation of this clause, I am forbidden from >>mirroring the DocBook specifications and schemas on docbook.org. Is >>that the intent? Or is the intent merely that no TC content may appear >>solely on non-OASIS servers? >> >>Suppose a third party, unaffiliated with OASIS or the TC constructs >>such a mirror? Will OASIS pursue having those materials removed from >>the mirror? > >I feel compelled also to note that this requirement places a >considerable burden on chairs and secretaries coming as it does in >advance of an improved (i.e. useful and workable) document repository >administered by OASIS. > > Be seeing you, > norm > >[1] >http://lists.oasis-open.org/archives/tcproc-member-review/200410/msg00001.html > >-- >Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc. >NOTICE: This email message is for the sole use of the intended >recipient(s) and may contain confidential and privileged information. >Any unauthorized review, use, disclosure or distribution is prohibited. >If you are not the intended recipient, please contact the sender by >reply email and destroy all copies of the original message. > >Attachment converted: Enterprise:Untitled ( / ) (002F64D6) -- Rex Brooks GeoAddress: 1361-A Addison, Berkeley, CA, 94702 USA, Earth W3Address: http://www.starbourne.com Email: rexb@starbourne.com Tel: 510-849-2309 Fax: By Request
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]