On Thu, 03 May 2012 00:03:05 +0200, Arthur Barstow art.bars...@nokia.com
wrote:
On 5/2/12 1:27 PM, ext Olli Pettay wrote:
I don't understand this.
The explainer doesn't look like something which should become a
recommendation.
And it may never become a Recommendation (f.ex. the group may
FYI: I buffed up the explainer to conform to PubRules:
http://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/index.html
:DG
As discussed during WebApps' May 1 f2f meeting [2], the Web Components
Explainer document is ready for a First Public Working Draft (FPWD)
publication and this a Call for Consensus (CfC) to do so:
http://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/index.html
This CfC satisfies the
I don't understand this.
The explainer doesn't look like something which should become a
recommendation.
It just, well, explains how the various proposed APIs work.
So, why do we need explainer as FPWD?
-Olli
On 05/02/2012 11:22 PM, Arthur Barstow wrote:
As discussed during WebApps' May 1
On 5/2/12 1:27 PM, ext Olli Pettay wrote:
I don't understand this.
The explainer doesn't look like something which should become a
recommendation.
And it may never become a Recommendation (f.ex. the group may later
decide to publish it as a WG Note).
It just, well, explains how the
