[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ekmi] Minutes :: EKMI Monthly TC Meeting - August 18, 2009
Sorry for any missunderstanding. I think that Mary answered your question clearly. The process seems reasonable to me. Cheers, Tomas Benjamin Tomhave wrote: > Tomas - you grossly misconstrue my comments, which had nothing to do > with open-source (StrongKey is open source). > > Mary can correct me if I'm wrong here, but my point was this: for KeyMG > to have a use statement that counts toward the number of use statements > need to move to the next phase of development, it would have to either > be an officially supported/sanctioned work of RedHat and/or PrimeKey > (your respective member orgs), OR it would have to be adopted by them > into a product (open source, closed source, whatever) and then they > would have to issue use statements on that respective product. > > This point goes directly toward due process and protocol. It's not > adequate to just go create an open-source library conforming to the > draft standard - a member org has to issue a use statement indicating > use of the library. > > -ben > > Anil Saldhana wrote: >> It is only supportive for any standard to get as many statement of usage >> from individuals, organizations (non-profit >> & commercial) as possible. It shows that the particular standard in >> question is not something that has been carved >> out for fun. >> >> Given this, Oasis (and rightly so) tries to ensure that the particular >> effort becomes a public standard only after getting >> an endorsement from 3 entities (who are contributor level or higher in >> Oasis membership) claiming *usage* of the standard. >> This requirement not only dispels those standards that are created with >> a lot of vested interest but also brings credibility to >> the standards that become Oasis Public Standard. >> >> My opinion. >> >> Tomas Gustavsson wrote: >>> Great, that does not seem to make any difference between open or closed >>> source software. >>> >>> Regards, >>> Tomas >>> >>> >>> Mary McRae wrote: >>> >>>> Just to clarify, statements of use must be from OASIS Organizational >>>> Members, not 'commercial vendors'. Anyone who is an OASIS Organizational >>>> Member (meaning not an Individual or Associate Member) can issue a >>>> statement of use. They do not need to belong to the TC. >>>> >>>> A Statement of Use is defined in the TC Process as follows: >>>> "Statement of Use", with respect to a specification, is a written >>>> statement by an OASIS Organizational Member stating that it is >>>> successfully using or implementing that specification in accordance with >>>> the conformance clauses specified in Section 2.18 >>>> <http://www.oasis-open.org/committees/process.php#specQuality>, and >>>> stating whether its use included the interoperation of multiple >>>> independent implementations. >>>> >>>> Regards, >>>> >>>> Mary >>>> >>>> >>>> >>>> Mary P McRae >>>> Director, Standards Development >>>> Technical Committee Administrator >>>> OASIS: Advancing open standards for the information society >>>> email: mary.mcrae@oasis-open.org <mailto:mary.mcrae@oasis-open.org> >>>> web: www.oasis-open.org <http://www.oasis-open.org> >>>> twitter: fiberartisan #oasisopen >>>> phone: 1.603.232.9090 >>>> >>>> Standards are like parachutes: they work best when they're open. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Aug 19, 2009, at 2:49 AM, Tomas Gustavsson wrote: >>>> >>>> >>>>> If that is the case I think OASIS have made a huge misstake. I hope >>>>> someone from Oasis can answer this question? >>>>> >>>>> Discriminating open source software certainly does not seem worthy of >>>>> an open standardization organization. >>>>> >>>>> Regards, >>>>> Tomas >>>>> >>>>> >>>>> Benjamin Tomhave wrote: >>>>> >>>>>> A question on conforming implementations... don't they need to be from >>>>>> commercial vendors to count toward the number required to move on with >>>>>> the process? >>>>>> Anil Saldhana wrote: >>>>>> >>>>>>> Anil Saldhana wrote: >>>>>>> >>>>>>>> EKMI TC Monthly Meeting - August 18, 2009 (Tuesday) >>>>>>>> 10:00am CDT/11:00amEDT/8amPDT/3:00pm UTC/5:00pm Oslo >>>>>>>> >>>>>>>> Agenda >>>>>>>> 1. Roll Call >>>>>>>> >>>>>>> Voting Members: >>>>>>> Tomas (PrimeKey), Tim(CA) and Anil (Red Hat) (3 out of 5) - Quorum >>>>>>> Reached >>>>>>> >>>>>>>> 2. XSD Improvements >>>>>>>> (http://lists.oasis-open.org/archives/ekmi/200906/msg00014.html) >>>>>>>> >>>>>>> We will make the changes to the schema. >>>>>>> >>>>>>> >>>>>>>> 3. WSDL >>>>>>>> (http://lists.oasis-open.org/archives/ekmi/200906/msg00015.html) >>>>>>>> >>>>>>> We will add it to the spec. >>>>>>> >>>>>>>> 4. Discussion on Implementations >>>>>>>> >>>>>>> Anil created this open source project >>>>>>> http://keymg.codehaus.org at the CodeHaus Foundation >>>>>>> to create a conforming implementation. >>>>>>> * The library will be LGPL licensed. Both Anil and Tomas >>>>>>> are current owners of this project. >>>>>>> - If you want to be added to this project, enroll at codehaus : >>>>>>> http://xircles.codehaus.org/signup >>>>>>> - Then please tell us about it. We can add you to the project in a >>>>>>> role. >>>>>>> >>>>>>> >>>>>>>> 5. Subcommittee Report >>>>>>>> >>>>>>> - Audit Guidelines SC : Put on hold as Ken Adler is unavailable >>>>>>> (as per >>>>>>> Ken). >>>>>>> - Mobile SC: Put on hold until we get the v1.0 out >>>>>>> - TCK SC: We will generate it as part of the aforementioned OSS >>>>>>> project. >>>>>>> >>>>>>>> 6. Other Business >>>>>>>> >>>>>>> - We will drop the idea of standardizing a Client API at this time. >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe from this mail list, you must leave the OASIS TC that >>>>>>> generates this mail. Follow this link to all your TCs in OASIS at: >>>>>>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >>>>>>> >>>>>>> >>>>>>> >>>>>>> >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> >> >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]