Re: CfC: Shelve Web Intents, Web Intents Addendum, Pick Media Intent, Pick Contacts Intent, respond by 17 May (next Friday) (resend)
This CfC has completed with support for shelving the Web Intents Addendum, Pick Media Intent, and Pick Contacts Intent specifications. Based on the CfC mail discussion (and DAP teleconference) we have also agreed to publish Web Intents as a W3C WG Note to complete work (for now). As with all shelving (and Notes) the WG may decide to resume this work at any time with the current or a revised approach. Thanks to Jungkee for adding a note to the Pick Media Intent and Pick Contacts Intent specifications to mark them as shelved. I have done the same for the Web Intents Addendum. I have also updated the DAP home page to note that Web Intents Addendum, Pick Media Intent, and Pick Contacts Intent are shelved. We will go ahead to arrange the publication of Web Intents as a W3C Note and then I will update the DAP page accordingly. Thanks regards, Frederick Frederick Hirsch, Nokia Chair, W3C DAP Working Group On May 8, 2013, at 4:00 PM, Hirsch Frederick (Nokia-CIC/Boston) wrote: (resend to include Web Intents TF list and WebApps list for shelving Web Intents spec, as well as DAP for all of specs) --- This is a Call for Consensus (CfC) to shelve the Web Intents, Web Intents Addendum, Pick Media Intent, and Pick Contacts Intent specifications (4 specs). Shelving in this case means that we are not sure the specifications will advance along the lines the drafts indicate. As a result we want to be clear to everyone that we may not advance the specifications or that we may change the approach. This does not mean that we have decided not to advance them, just that there is a question as to the direction and/or progression at this point. In order to advance this work we need support for the underlying technology, which we have been assuming will be a combination of Web Intents and Web Activities. This will require some sharing of proposals on the public list to enable progress. It would be best if we can progress this on the public list by September, so that we can have a meaningful result on the topic at a TPAC F2F. If we have consensus to shelve the documents, this will have the following immediate consequences: 1. The editors will edit each document to add a warning statement before the abstract. I suggest we use the following text (feel free to make suggestions): The Device APIs Working Group is currently not progressing the approach outlined in this draft. Please treat this document with caution and do not reference it or use it as the basis for implementation. The domain covered by this document is still within the scope of the Working Group as defined in its Charter. The Working Group may resume this work or adopt an alternative approach depending on the interest of WG members and implementers. 2. On the DAP home page we will move the specifications from the active roadmap [1] to the list of shelved specifications [2]. I suggest we keep both the links to the latest published draft and editors draft available when we do this. (I can volunteer to make this update if we agree to this CfC). Please send all comments regarding this CfC to the public-device-a...@w3.org mail list by 17 May (next Friday). Silence will be considered as agreement with the proposal. If you support this CfC, a positive response is preferred and encouraged, even if a +1. Obviously any constructive work on the list regarding the underlying technology would also be welcome. Thanks regards, Frederick Frederick Hirsch, Nokia Chair, W3C DAP Working Group [1] http://www.w3.org/2009/dap/#roadmap [2] http://www.w3.org/2009/dap/#shelved
Re: CfC: Shelve Web Intents, Web Intents Addendum, Pick Media Intent, Pick Contacts Intent, respond by 17 May (next Friday) (resend)
On 5/8/13 4:00 PM, ext frederick.hir...@nokia.com wrote: This is a Call for Consensus (CfC) to shelve the Web Intents, Web Intents Addendum, Pick Media Intent, and Pick Contacts Intent specifications (4 specs). Shelving in this case means that we are not sure the specifications will advance along the lines the drafts indicate. As a result we want to be clear to everyone that we may not advance the specifications or that we may change the approach. This does not mean that we have decided not to advance them, just that there is a question as to the direction and/or progression at this point. My general comment is the Consortium's way to state work on a document has ended is to publish a WG Note [WGNote]. So although I agree it is important to clarify the status of Web Intents, it's not clear to me that inventing new process (shelving) is a good approach and it certainly fails the HeartBeat publication requirement [Heartbeat]. It appears to me Web Intents has not changed in seven months [Changelog]. Is there any credible plan including commitment(s) to continue the work? If so, where is that info? Based on the data I have seen so far, it seems like the appropriate next step for Web Intents is to publish it as a WG Note. (I am indifferent about the other specs mentioned above.) (At some future point in time, if there is consensus to do so and the necessary resources are identified, the spec could continue along the TR track). -AB [WGNote] http://www.w3.org/2005/10/Process-20051014/tr.html#q75 [Heartbeat] http://www.w3.org/2005/10/Process-20051014/groups.html#three-month-rule [Changelog] https://dvcs.w3.org/hg/web-intents/log
Re: CfC: Shelve Web Intents, Web Intents Addendum, Pick Media Intent, Pick Contacts Intent, respond by 17 May (next Friday) (resend)
On Thu, 09 May 2013 13:35:06 +0200, Arthur Barstow art.bars...@nokia.com wrote: On 5/8/13 4:00 PM, ext frederick.hir...@nokia.com wrote: This is a Call for Consensus (CfC) to shelve the Web Intents, Web Intents Addendum, Pick Media Intent, and Pick Contacts Intent specifications (4 specs). Shelving in this case means that we are not sure the specifications will advance along the lines the drafts indicate. As a result we want to be clear to everyone that we may not advance the specifications or that we may change the approach. This does not mean that we have decided not to advance them, just that there is a question as to the direction and/or progression at this point. My general comment is the Consortium's way to state work on a document has ended is to publish a WG Note [WGNote]. So although I agree it is important to clarify the status of Web Intents, it's not clear to me that inventing new process (shelving) is a good approach and it certainly fails the HeartBeat publication requirement [Heartbeat]. It appears to me Web Intents has not changed in seven months [Changelog]. Is there any credible plan including commitment(s) to continue the work? If so, where is that info? Based on the data I have seen so far, it seems like the appropriate next step for Web Intents is to publish it as a WG Note. (I am indifferent about the other specs mentioned above.) I agree with Art here. cheers Chaals (At some future point in time, if there is consensus to do so and the necessary resources are identified, the spec could continue along the TR track). -AB [WGNote] http://www.w3.org/2005/10/Process-20051014/tr.html#q75 [Heartbeat] http://www.w3.org/2005/10/Process-20051014/groups.html#three-month-rule [Changelog] https://dvcs.w3.org/hg/web-intents/log -- Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex cha...@yandex-team.ru Find more at http://yandex.com
CfC: Shelve Web Intents, Web Intents Addendum, Pick Media Intent, Pick Contacts Intent, respond by 17 May (next Friday) (resend)
(resend to include Web Intents TF list and WebApps list for shelving Web Intents spec, as well as DAP for all of specs) --- This is a Call for Consensus (CfC) to shelve the Web Intents, Web Intents Addendum, Pick Media Intent, and Pick Contacts Intent specifications (4 specs). Shelving in this case means that we are not sure the specifications will advance along the lines the drafts indicate. As a result we want to be clear to everyone that we may not advance the specifications or that we may change the approach. This does not mean that we have decided not to advance them, just that there is a question as to the direction and/or progression at this point. In order to advance this work we need support for the underlying technology, which we have been assuming will be a combination of Web Intents and Web Activities. This will require some sharing of proposals on the public list to enable progress. It would be best if we can progress this on the public list by September, so that we can have a meaningful result on the topic at a TPAC F2F. If we have consensus to shelve the documents, this will have the following immediate consequences: 1. The editors will edit each document to add a warning statement before the abstract. I suggest we use the following text (feel free to make suggestions): The Device APIs Working Group is currently not progressing the approach outlined in this draft. Please treat this document with caution and do not reference it or use it as the basis for implementation. The domain covered by this document is still within the scope of the Working Group as defined in its Charter. The Working Group may resume this work or adopt an alternative approach depending on the interest of WG members and implementers. 2. On the DAP home page we will move the specifications from the active roadmap [1] to the list of shelved specifications [2]. I suggest we keep both the links to the latest published draft and editors draft available when we do this. (I can volunteer to make this update if we agree to this CfC). Please send all comments regarding this CfC to the public-device-a...@w3.org mail list by 17 May (next Friday). Silence will be considered as agreement with the proposal. If you support this CfC, a positive response is preferred and encouraged, even if a +1. Obviously any constructive work on the list regarding the underlying technology would also be welcome. Thanks regards, Frederick Frederick Hirsch, Nokia Chair, W3C DAP Working Group [1] http://www.w3.org/2009/dap/#roadmap [2] http://www.w3.org/2009/dap/#shelved
