Re: Request to move app: URI to FPWD

On 18/04/13 16:42, Mandyam, Giridhar wrote:
>> The point of a charter is to define the scope of deliverables so
>> that participants can estimate the breadth of the patent
>> commitment.
>
> This feature was not defined within scope of the charter based on our
> understanding.  This is why I was asking for it to be called out in
> the charter.

The idea of a distinct URI scheme for installed apps is called out in 
the examples cited in the charter, see e.g. the strawman proposal from 
Google as linked from the description of the security model.

The scope of the charter is set out broadly in section 2, with more 
detail in section 3 with brief descriptions of each deliverable, 
together with examples that were explicitly included in the charter to 
allow the Advisory Committee to better understand the scope, and many 
companies have subsequently joined the System Applications Working Group 
after reviewing the charter.

-- Dave

> -----Original Message-----
> From: Robin Berjon [mailto:robin@w3.org]
> Sent: Thursday, April 18, 2013 8:17 AM
> To: Mandyam, Giridhar
> Cc: Marcos Caceres; Mounir Lamouri; wonsuk11.lee@samsung.com; public-sysapps@w3.org
> Subject: Re: Request to move app: URI to FPWD
>
> On 18/04/2013 17:08 , Mandyam, Giridhar wrote:
>> I don't see a problem in amending the charter to make this deliverable
>> explicit (this can also be done for app manifest).
>> Please propose the appropriate charter modifications and we can
>> withdraw our objection.
>
> As noted the app: URI scheme was part of a document that was in its
> entirety already deemed in scope for this group (and very justifiably
> so). The point of a charter is to define the scope of deliverables so
> that participants can estimate the breadth of the patent commitment.
> Its point is emphatically not to PHB-micromanage the publication of
> documents — that's the group's full prerogative. Splitting chartered
> deliverables into multiple documents, or conversely merging multiple
> chartered deliverables into a single document, is therefore a common
> operation.
>
> There is therefore no need whatsoever for the charter to be modified.
> This objection has no grounding in W3C Process. I kindly suggest that
> you withdraw it with no further ado.
>
> --
> Robin Berjon - http://berjon.com/ - @robinberjon
>


-- 
Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett

Received on Friday, 19 April 2013 09:25:28 UTC