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


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-cap message

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

Subject: Re: [emergency-cap] Groups - CAP Extensibility Options uploaded

Hi Elysa, hi Steve, 

Thanks very much for looping Jamie and I into this conversation. Here is some OASIS feedback for you. 

Re " I encourage all members in the EM-TC to comment on the list and on your document posted in Kavi.  It may be a little more awkward but will ensure that your comments are protected under your signed IPR agreement with OASIS concerning our TC." 

This is correct Elysa and thanks for pointing that out. You all need to keep your comments "on the farm" so to speak in order to stay within the IPR protections of the TC charter and your participation at OASIS. 

Re "As to the comments that come in from the Google site..." I'll be even more explicit. You may not use those comments at all. The OASIS TC Process is very explicit, in section 2.8, TC Visibility (see https://www.oasis-open.org/policies-guidelines/tc-process#visibility), that "Comments to the TC made by Members of the TC must be made via the TC general email list, and comments made by non-TC members, including from the public, must be made via the TC's comment facility. Comments shall not be accepted via any other means." 

Assuming all the comments on the Google doc are from TC members only, collecting the comments together in some form and then submitting to the TC via the mailing list or by uploading to the Kavi archive would be fine. That would give you everything you need. But leaving them in a document living off the OASIS platform is both a breach of OASIS rules and general philosophy of openness, transparency and permanence of the record of the TC's work and leaves you in a possibly vulnerable position to boot. 

Again, thanks & let me know if you have any questions about this. 


On Wed, Jul 17, 2013 at 10:17 AM, Elysa Jones <elysajones@yahoo.com> wrote:

Hi Steve,


Thank you for the good work you have done on this document and the effort to layout the options going forward to include more structured data in CAP.  I encourage all members in the EM-TC to comment on the list and on your document posted in Kavi.  It may be a little more awkward but will ensure that your comments are protected under your signed IPR agreement with OASIS concerning our TC. 


As to the comments that come in from the Google site, I’m concerned that contributions may be made that could ultimately wind up in a specification for which someone might try to extract royalties at a later time.  Perhaps Google has protection from that in the posting of comments/corrections/changes on your site?  Maybe it is ok if Google collects these comments and submits the redline under their OASIS membership IPR agreement?  I’m copying Chet (TC Admin) and Jamie (Legal Counsel) so they can weigh in as appropriate.


Thanks again for your great support and work on CAP!





From: emergency-cap@lists.oasis-open.org [mailto:emergency-cap@lists.oasis-open.org] On Behalf Of Steve Hakusa
Sent: Tuesday, July 16, 2013 9:50 PM
To: emergency-cap@lists.oasis-open.org
Subject: [emergency-cap] Groups - CAP Extensibility Options uploaded


Submitter's message
Hello CAP-SC members,

I took an action item from the July 8, 2013 CAP-SC meeting to try to summarize our discussion on CAP extensibility options and explore security implications. The goal of creating this doc is to facilitate discussion outside of our bi-weekly meeting, more quickly reach a consensus, and allow the committee to use its valuable meeting time on other CAP-SC business.

The full document has been uploaded to the CAP-SC document list, but if you have comments (and a Google account), it may be faster to provide those comments directly in the live version, which can be found here:
https://docs.google.com/document/d/10s_wB4xT3pw_cHY6jNiiTjn5N2pa_dbzCWgcAafnfS4/edit Please use that version if possible.

Steve Hakusa

-- Mr. Steve Hakusa

Document Name: CAP Extensibility Options

This document is intended to summarize use cases and requirements for
expressing system-specific data inside the Common Alerting Protocol. It
was written following a presentation on Hierarchical Structured Data in CAP
delivered to the Common Alerting Protocol Implementation Workshop in Geneva
on April, 2013.
Download Latest Revision
Public Download Link

Submitter: Mr. Steve Hakusa
Group: EM CAP SC
Folder: Contributions
Date submitted: 2013-07-16 19:50:10



Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open

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