Re: CfC: publish First Public Working Draft of the Presentation API (deadline 12 Feb)

Hello everyone,

I support Mark (Foltz)s comments. The FPWD should flag the open issues that
must be solved to meet the scope of the charter, to encourage feedback on
the whole of the problem space we are addressing.

…Mark

On Wed, Feb 4, 2015 at 3:39 PM, mark a. foltz <mfoltz@google.com> wrote:

> Hello Anssi,
>
> I wanted to raise a concern that the issues listed in the FPWD milestone
> [1] do not reflect significant remaining work items as far as having the
> spec meet the scope of the charter.  If the goal of the FPWD milestone is
> to gain wider visibility and comment in unfinished areas, shouldn't these
> be included?
>
> Charter [2]:
> "...a means to communicate with and control the web content from the
> initiating page and other authorized pages"
> Implies we should address issues 36 [3] and 19 [4] in the draft spec as a
> work in progress.
>
> Charter:
> "The user agent is responsible for determining which secondary displays
> are compatible with the content that is requested to be shown through the
> API."
> Implies we should address issue 9 [5] in the draft spec as a work in
> progress.
>
> Finally, we have a milestone item for defining postMessage behavior in
> issue 46 [6], but we can't really do that until we finalize the messaging
> API per issue 16 [7].  Since Mozilla already has an implementation should
> that be folded into the spec?
>
> Would the next step be to reprioritize these issues appropriately, and
> update the spec to ensure that it correctly reflects the scope of remaining
> work?  Otherwise we will be missing feedback on some key aspects.
>
> I can help craft a pull request with some of these changes.
>
> [1] https://github.com/w3c/presentation-api/milestones/FPWD
> [2] http://www.w3.org/2014/secondscreen/charter.html
> [3] https://github.com/w3c/presentation-api/issues/36
> [4] https://github.com/w3c/presentation-api/issues/19
> [5] https://github.com/w3c/presentation-api/issues/9
> [6] https://github.com/w3c/presentation-api/issues/46
> [7] https://github.com/w3c/presentation-api/issues/16
>
> m.
>
>
>
>
> On Mon, Feb 2, 2015 at 12:45 AM, Kostiainen, Anssi <
> anssi.kostiainen@intel.com> wrote:
>
>> Hi All,
>>
>> This is a Call for Consensus (CfC) to publish a First Public Working
>> Draft (FPWD) [1] of the Presentation API with the shortname
>> "presentation-api". The latest Editor's Draft is at [2].
>>
>> The specification will keep the same shortname throughout its evolution
>> along the Recommendation track. The shortname is used to build the URL of
>> the published document, e.g.:
>>
>> http://www.w3.org/TR/[shortname]
>> http://www.w3.org/TR/WD-[shortname]-[YYYYMMDD]
>>
>> Please review the latest Editor's Draft [2] and inform the group of any
>> concerns on this mailing list. We can do editorial changes during the CfC
>> before we publish the FPWD. For example, we should ensure the P1 issues
>> assigned to the FPWD milestone [3] are clearly noted as "work-in-progress"
>> in the spec. My expectation is the editor will handle this task. In
>> addition, we should update the Status of This Document. Francois
>> volunteered to take this action.
>>
>> The CfC ends 12 February 2015. If more time is needed for the review,
>> please inform me.
>>
>> Responses to this CfC are preferred, even if just +1. Silence is
>> considered an agreement.
>>
>> Please note that a First Public Working Draft is what the name suggests
>> -- a first draft. That is, a FPWD does not need to be perfect and
>> subsequent change is to be expected. By publishing a FPWD the specification
>> will get further review and visibility.
>>
>> Please also note that publication as a First Public Working Draft
>> triggers a Call for Exclusions, per section 4 of the W3C Patent Policy [4].
>>
>> Thanks,
>>
>> -Anssi (WG chair)
>>
>> [1] http://www.w3.org/2014/Process-20140801/#first-wd
>> [2] http://w3c.github.io/presentation-api/
>> [3] https://github.com/w3c/presentation-api/milestones/FPWD
>> [4] http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Exclusion
>>
>
>