[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [chairs] RE: [members] OASIS member review of proposed revision of TC Process
Some of my subcommittee members are discussing developing an open source reference implimentation of oBIX on SourceForge. Is this forbidden under this policy? tc -----Original Message----- From: Robin Cover [mailto:robin@oasis-open.org] Sent: Wednesday, October 13, 2004 2:30 PM To: Mason, Howard (UK) Cc: chairs@lists.oasis-open.org Subject: RE: [chairs] RE: [members] OASIS member review of proposed revision of TC Process With respect to mesages from Howard Mason and David RR Webber http://lists.oasis-open.org/archives/chairs/200410/msg00021.html http://lists.oasis-open.org/archives/chairs/200410/msg00024.html [Howard] The constraint on hosting all information on OASIS servers would appear to preclude the use of our publicly-available sourceforge open-source publication process, used to deliver completed documents to the OASIS server by running XSLT scripts against XML source content. This will only be acceptable when an equivalent sourceforge environment can be hosted on OASIS. [David] ... I totally agree on the hosting topic. Perhaps a better wording here is "where OASIS provides equivalent functionality and requests that the TC use it". Notice things like developer discuss lists are one thing that is out there right now - is OASIS going to be hosting all those too? I think Howard and David are referring to the draft TC Process document says (in this revision): ====================================================== 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. ====================================================== Perhaps the OASIS administration would like to clarify whether this represents a substantive change in policy or (rather) a clarification of existing policy, viz., which is the interpretation: "all *PUBLIC, OFFICIAL* resources of the TC ... must be located only on facilities provided by OASIS..." and "TCs and SCs may not... conduct any *OFFICIAL* business or *OFFICIAL* technical discussions, store *OFFICIAL* documents, or host *OFFICIAL* web pages on non-OASIS servers... IMO the word "only" is infelicitous, and should be nuked because literally, without other qualification, it makes an absurd assertion. Literally understood, it's unenforceable, as well as impractical and absurd to understand the "must/only" in a global, universal sense, since we all maintain OASIS TC-related resources on our home computers. I suspect the new language is meant to clarify that all official (canonical) resources are to be OASIS-hosted. Less likely that the dozens of remote sites are going to receive take-down legal notices from OASIS administration for wikis, Yahoo!Groups, SourceForge sites, and many other venues unofficially supporting OASIS spec implementations and storing copies of OASIS-related documents. </unofficial> -rcc On Wed, 13 Oct 2004, Mason, Howard (UK) wrote: > > The new ability for a TC member to be active only in an SC fits very well with the PLCS TC mode of operation. We were already choosing to invite organisations to consider which of their members needed to be registered as a voting member, in order to avoid the need for SC experts to participate in all meetings/telecons. > > The constraint on hosting all information on OASIS servers would appear to preclude the use of our publicly-available sourceforge open-source publication process, used to deliver completed documents to the OASIS server by running XSLT scripts against XML source content. This will only be acceptable when an equivalent sourceforge environment can be hosted on OASIS. > > Similarly, the requirement that all specifications be available also in PDF is not practical for complex hyperlinked documents, such as PLCS data exchange sets. ISO already permits publication in HTML form only, and we do not see why OASIS should be more restrictive for documents that will only be accessed in HTML form. > > > Howard Mason > PLCS TC > > -----Original Message----- > From: Eduardo Gutentag [mailto:Eduardo.Gutentag@Sun.COM] > Sent: 13 October 2004 01:54 > To: Newcomer, Eric > Cc: Philpott, Robert; karl.best@oasis-open.org; > chairs@lists.oasis-open.org; security-services@lists.oasis-open.org > Subject: Re: [chairs] RE: [members] OASIS member review of proposed > revision of TC Process > > > *** WARNING *** > > This mail has originated outside your organization, either from an > external partner or the Global Internet. > Keep this in mind if you answer this message. > > Any OASIS member will be able to join a TC. > > A TC member will have read-write privileges in the list. > > A TC member can request to become a voting member, in which case, and > in which case only, the TC member will have to meet attendance > criteria in order to continue being a voting member. (IOW, if the > attendace criteria are not met the member reverts to general > non-voting status, without leaving the TC). > > All TC members will be subject to the IPR Policy as it applies to the > TC's mode. > > Any OASIS member can become a TC Observer. Such Observer will have > only read privileges, and no obligations under the IPR Policy as it > applies to the TC's mode. > > Because becoming a TC member now has clear IPR implications and > obligations, it would be a bad idea to convert people automatically > from observers to members. This must be done in a proactive manner, > and with the approval, in the case of organizational members, of the organization's representative. > (In that sense [and in that sense only] this is similar to accepted > policy in other organizations, e.g. W3C) > > We really need an FAQ. I thought there was one already out for review, > but obviously I was wrong... > > > > On 10/12/2004 04:56 PM, Newcomer, Eric wrote: > > Eduardo, > > > > Do you mean that the new process doesn't change the ability of anyone to join a TC and participate as a non-voting member? So the proposed change is simply a renaming of the type of member, not the elimination of a membership category? > > > > Thanks, > > > > Eric > > > > -----Original Message----- > > From: Eduardo Gutentag [mailto:Eduardo.Gutentag@Sun.COM] > > Sent: Tuesday, October 12, 2004 7:26 PM > > To: Philpott, Robert > > Cc: karl.best@oasis-open.org; chairs@lists.oasis-open.org; > > security-services@lists.oasis-open.org > > Subject: Re: [chairs] RE: [members] OASIS member review of proposed > > revision of TC Process > > > > > > But Rob, if you read the new process carefully, you will discover > > that you can be a TC member without being a voting member (that is, > > you can be a non-voting TC member without having to meet attendance > > criteria), thus being able to contribute to your heart's content as > > current Observers do. > > > > > > On 10/12/2004 03:25 PM, Philpott, Robert wrote: > > > >>I would like to express serious concerns with the proposed change to > >>the TC process that means that TC observers would no longer be able > >>to post to the TC's mailing list. > >> > >>>From the current process: "An Observer may participate in TC > >>>discussions > >>and post email messages to the TC list, but may not vote and does > >>not need to maintain attendance." > >> > >>>From the proposed process: "Observer" (or "TC Observer") is an > >>>Eligible > >>Person who is subscribed to the TC email list, and may attend TC > >>meetings, but is not allowed to participate in TC email list > >>discussions, participate or speak in TC meetings, or make > >>Contributions to the TC. The process for becoming an Observer is > >>defined in the section "TC Membership and Participation". > >> > >>I STRONGLY disagree with making this change. The SSTC has over 260 > >>members, of which 40-50 are active voting members. However, our TC > >>regularly receives valuable input on email discussion topics from > >>members that don't have currently active voting status. These > >>postings are from folks such as those in other TC's that monitor our > >>list because those TC's have some dependency on ours. Requiring > >>folks to find some other mechanism to provide their input simply > >>throws up barriers in front of them and will in all likelihood > >>result in us not receiving that input at all. > >> > >>The input from these members is very important to us. I believe > >>this to be a bad change of policy that goes against the open, free > >>exchange of ideas that we rely on. > >> > >>Rob Philpott > >>Senior Consulting Engineer > >>RSA Security Inc. > >>Tel: 781-515-7115 > >>Mobile: 617-510-0893 > >>Fax: 781-515-7020 > >>mailto:rphilpott@rsasecurity.com > >> > >> > >> > >>>-----Original Message----- > >>>From: Karl F. Best [mailto:karl.best@oasis-open.org] > >>>Sent: Monday, October 11, 2004 10:10 AM > >>>To: members > >>>Subject: [members] OASIS member review of proposed revision of TC > >> > >>Process > >> > >> > >>>OASIS members: > >>> > >>>You're aware that the OASIS Board of Directors has been working on > >>>a revision of the OASIS IPR Policy, and you have had an opportunity > >>>to give feedback on that proposed revision. > >>> > >>>The Board has also been working on a revision of the OASIS TC > >>>Process, the document that governs the creation and operation of > >>>TCs at OASIS, and the advancement and approval of the work they do. > >>>This revision includes changes suggested by TC chairs, the > >>>Technical Advisory Board (TAB), and other members. It also includes > >>>changes required to support the new IPR Policy; because these two > >>>documents rely on each other > >> > >>they > >> > >> > >>>must be revised, approved, and become effective at the same time. > >>> > >>>The Board has approved an OASIS member review of the revised > >>>Process; this review will start today and go until 10 November. A > >>>draft of the revised TC Process document approved for member review > >>>by the Board is found at > >>>http://www.oasis-open.org/apps/org/workgroup/members- > >>>only/download.php/9623/TC%20Process%2020041007.pdf. > >>> > >>> > >>>A document summarizing the changes from the current Process is at > >>>http://www.oasis-open.org/apps/org/workgroup/members- > >>>only/download.php/9621/Process%20revision%20summary.pdf > >>> > >>>Please send your comments in regards to these proposed changes to > >>>tcproc-member-review@lists.oasis-open.org by 10 November, so that > >>>the Board can consider your comments, make changes to this draft, > >>>and have the Process document ready to be effective at the same > >>>time as the new IPR Policy. > >>> > >>>-Karl > >>> > >>>================================================================= > >>>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 > >>> > >>> > >>> > >>> > >>>_______________________________________________________________ > >>>This email list is used solely by OASIS for official consortium > >>>communications. Opt-out requests may be sent to > >>>member_services@oasis-open.org, however, all members are strongly > >>>encouraged to maintain a subscription to this list. > > > > > > -- > Eduardo Gutentag | e-mail: eduardo.gutentag@Sun.COM > Web Technologies and Standards | Phone: +1 510 550 4616 (internal x31442) > Sun Microsystems Inc. | W3C AC Rep / W3C AB / OASIS BoD > > > ******************************************************************** > This email and any attachments are confidential to the intended > recipient and may also be privileged. If you are not the intended > recipient please delete it from your system and notify the sender. > You should not copy it or use it for any purpose nor disclose or > distribute its contents to any other person. > ******************************************************************** > --
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]