W3C home > Mailing lists > Public > public-wot-ig@w3.org > May 2016

Re: IG charter - alpha 4

From: J. Alan Bird <abird@w3.org>
Date: Wed, 18 May 2016 13:43:40 -0400
To: Dave Raggett <dsr@w3.org>, Public Web of Things IG <public-wot-ig@w3.org>
Message-ID: <bf4c1daa-57d1-1fd1-ff20-215e1db25f91@w3.org>

    I'll gladly be the reviewer, no problem.  One thing I'm hoping that 
is in there, and I'll find out on my review, is some of the new things 
that have been discussed on the threads that my team can use to recruit 
new Members to the work.  I think we need to accelerate the work that's 
being done and that can only happen with new bodies.   Stay tuned for 
the full review.



On 5/18/2016 13:39, Dave Raggett wrote:
> I am seeking a W3C Management Committee (W3M) member to review the 
> draft charter, something that is a precondition for asking approval to 
> start the Advisory Committee Review. I expect to announce the charter 
> extension as part of the advanced notice for the work on the IG and WG 
> charters. I plan to send this out on Monday morning.  We need to 
> finalise the IG charter by the close of Friday, and I will ask W3M for 
> approval for the AC Review at their next meeting on Wednesday, Jul 25.
> Following today’s call, I have generated the alpha 4 version of the 
> draft IG charter, see:
> http://www.w3.org/2016/05/wot-ig-2016-alpha4.html
> We’re still in need of dates for first IG notes for each of the 
> deliverables.
> The changes are as follows:
> I’ve switched to the patent disclosure wording from the previous 
> charter as the new charter template was designed primarily for WGs.
> Update the relationships figure to fix camel-casing of PlugFest, and 
> corrected WG description to “write test suites” rather than “interop” 
> since W3C WGs don’t normally work on interop testing. Instead, they 
> are required to produce test suites and to collect implementation 
> reports as a condition for moving from Candidate to Proposed 
> Recommendation for their specifications. Note clicking/tapping on the 
> figure gives you the full sized version which could be useful for 
> people viewing the charter on mobile devices.
> The first paragraph for the scope section has been split and new text 
> added to the resulting second paragraph to explain the work on 
> semantic interoperability and end to end security across platforms 
> using different standards. It is made clear that this work 
> will combine implementation experience with in-depth analysis.
> The bullet points in the scope section have modified to clarify the 
> distinction between supporting the Working Group in respect to 
> satisfying the exit criteria for Candidate Recommendations, and the 
> role of PlugFests for interoperability testing across implementations 
> for ideas at different levels of maturity.
> I have added examples for further ideas for topics to the paragraph 
> following the bullet points.
> In respect to the deliverables, I would note that without the 
> deliverables for semantics and security, the W3C is unlikely to 
> attract the participation of the companies that we need to make the 
> Web of Things widely successful.  We need a compelling charter to 
> bring in people from all scales of businesses, with the breadth of 
> experience across different areas.  We need to become strategically 
> compelling for businesses as they seek embrace the opportunity and 
> disruption that the IoT will bring.  I recommend reading the Harvard 
> Business Review article by Michael Porter and James HeppelMan "How 
> Smart, Connected Products Are Transforming Competition”. See:
> https://hbr.org/2014/11/how-smart-connected-products-are-transforming-competition
> p.s. I am copying Alan Bird, W3C Business Development lead to allow 
> him to confirm the importance of rising the to opportunity for the Web 
> of Things.
> —
>    Dave Raggett <dsr@w3.org <mailto:dsr@w3.org>>

J. Alan Bird
W3C Global Business Development Leader
office +1 617 253 7823  mobile +1 978 335 0537
abird@w3.org   twitter @jalanbird
Received on Wednesday, 18 May 2016 17:43:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:27:03 UTC