OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

chairs message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [chairs] Seeking your feedback on proposed workflow changes

Not to be overly pedantic, but there is also an escape clause that you did not mention that Jamie pointed out to me. A member of a TC actually has 7 days, past the date of the ballot, to exist the TC and not be beholden to the IPR.   So OASIS Staff should really find a way to track members that were in a TC and then left, up until 7 days past the CS ballot.

PGP Fingerprint: 63B4 FC53 680A 6B7D 1447  F2C0 74F8 ACAE 7415 0050
"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."

On May 26, 2020, at 9:14 AM, Chet Ensign <chet.ensign@oasis-open.org> wrote:

Allan, sorry for the confusion. I'll do a better job of explaining. 

All work that happens here is covered by the IPR Policy. Copyright, trademarks, etc. is always applicable to anything and everything done in a committee. 

The particular issue I was pointing out to Stefan is the difference between an OASIS Standards Draft Deliverable and an OASIS Standards Final Deliverable. 

A Committee Specification Draft is a Standards Draft Deliverable. It is covered by the LIMITED PATENT COVENANT FOR DELIVERABLE DEVELOPMENT (section 6 - https://www.oasis-open.org/policies-guidelines/ipr#limitedpatent) - a limited covenant not to assert any essential claims against another TC member for the development of the work. 

When the TC approves the CSD as a Committee Specification, it is then an OASIS Standards Final Deliverable. It is at that point that the obligations and commitments associated with the chosen IPR mode lock in and the obligations made by TC members apply for any conforming implementation. That was the distinction I was pointing out to Stefan. The distinction in name between Committee Spec Draft and Committee Spec is meaningful in that regard. 

Does that answer the question? 



On Tue, May 26, 2020 at 10:28 AM Allan Thomson <athomson@lookingglasscyber.com> wrote:

It doesnât ?


How can we state that each TC operates under the IPR policy (at any stage) and then the statement that it only applies when you get to a CS?


This makes no sense whatsoever.


Either all the work in a TC is covered by the IPR policy or it invalidates a lot of collaboration.


Allan Thomson

CTO (+1-408-331-6646)

LookingGlass Cyber Solutions



Chet Ensign
Chief Technical Community Steward
OASIS: Advancing open source & open standards for the information society

Mobile: +1 201-341-1393 

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]