Add more content to the draft Web Bluetooth CG Charter: #84
Conversation
| @@ -34,15 +35,37 @@ that implement Bluetooth 4.0, 4.1, or 4.2. | |||
| standard using the Generic Attribute Profile (GATT). See the | |||
| [Web Bluetooth API](http://webbluetoothcg.github.io/web-bluetooth/) that serves as the | |||
| initial input. | |||
| This specification is a candidate for the Dual License as specified in | |||
There was a problem hiding this comment.
I don't object to this line, but am curious what the source of its selection is. Spot checking a few e.g. WebApps documents I don't see a reference to this document. I see some related copyright and attribution comments in https://www.w3.org/community/about/agreements/cla/. It would be good to document at least in change history the source of this.
There was a problem hiding this comment.
I copied this line from http://www.w3.org/2014/06/webapps-charter.html#url. The idea is that it would let a group like WHATWG fork the spec if the W3C ever freezes again.
There was a problem hiding this comment.
Looks good to me. I suggest we merge this and loop the revised version of the Charter via Wayne in the mail thread.
There was a problem hiding this comment.
WebApps WG has that in their charter because W3C Working Groups publish under the W3C Document License which doesn't allow forking for use in specs. There's an experiment that allows HTML WG extensions and this one Web Apps WG spec dual license. But, that is only relevant for specs in S3C Working Groups. Community Groups already publish under the CLA which allows forking, so it's pointless for a Community Group spec. https://www.w3.org/community/about/agreements/cla/#id2
|
LGTM |
* List stream communication as out-of-scope. * Suggest that the Spec be dual-licensed, using wording from http://www.w3.org/2014/06/webapps-charter.html#url. * Mention the security model, test suite, and polyfills as extra deliverables. * Rephrase the WebAppSec liason, since they should review more than just our use of "secure contexts". * Mention possibly asking for changes to Bluetooth itself, through the SIG. * Mention that contributions can come in through GitHub.
Add more content to the draft Web Bluetooth CG Charter.
@anssiko