W3C home > Mailing lists > Public > www-tag@w3.org > January 2012

Re: TAG Work Plan pages updated to reflect F2F decisions

From: Noah Mendelsohn <nrm@arcanedomain.com>
Date: Fri, 13 Jan 2012 16:16:41 -0500
Message-ID: <4F109F39.1060407@arcanedomain.com>
To: Robin Berjon <robin@berjon.com>
CC: "www-tag@w3.org" <www-tag@w3.org>
On 1/13/2012 2:40 PM, Robin Berjon wrote:
> I'm happy to pick up Dan's work on API Minimisation wherever he leaves
> off (Dan: feel free to finish it before the end of the month though
> ;-). I wonder if it should be related to the API design document[0]
> that's recently been started (but that's a rather major undertaking).

Picking up work before you're asked is definitely a way to ingratiate
yourself with the chair, thank you. That said, we generally do these things
by consensus, so whether we want to continue to invest in this is a
question I will put before the TAG as a whole.

You can probably figure out from the other product pages linked at [1] what
sort of plans we try to put in place before investing in serious project
work, I.e. setting out overall project goals, success criteria (which
typically should include actual impact on the community, as opposed to just
"we shipped a document"), proposed dates for deliverables, etc. Suggestion:
would you care to draft a proposed revision to the API Minimization product
page at [2], giving your ideas on what we should do and when? That would,
IMO, be an excellent basis for discussion with the group.

For now, please either attach any proposed drafts to an e-mail, or else
check them in under some convenient name in TAG space if you have the
appropriate CVS access (you should, but we may have to take care of that
with the team.) If and when the TAG approves this as a plan, I'll copy it
into the space below [1].

 > While on APIs, there's also a gaping void in describing the security
 > architecture for privileged APIs that I think could use some TAG work.

Please give some thought to whether this is part of the minimization 
project. I suspect not. If that's the case, then we'll need to consider 
whether to broaden the scope of the "product" on APIs to include security 
as well, or whether to propose it as a separate piece of TAG work. Either 
way, maybe you could start with an e-mail giving a bit more background on 
this concern?

Thank you again.

Noah

[1] http://www.w3.org/2001/tag/products/
[2] http://www.w3.org/2001/tag/products/apiminimization.html

On 1/13/2012 2:40 PM, Robin Berjon wrote:
> Hi all,
>
> On Jan 13, 2012, at 03:46 , Noah Mendelsohn wrote:
>> I have updated that TAG's work plan [1,2], along with the "product"
>> pages linked from that, to reflect my understanding of the progress
>> and decisions made at the F2F. Please review, as it's likely that I've
>> made at least some minor errors in doing this.
>
> I'm happy to pick up Dan's work on API Minimisation wherever he leaves
> off (Dan: feel free to finish it before the end of the month though ;-).
> I wonder if it should be related to the API design document[0] that's
> recently been started (but that's a rather major undertaking). While on
> APIs, there's also a gaping void in describing the security architecture
> for privileged APIs that I think could use some TAG work.
>
>
> [0] http://scriptlib-cg.github.com/api-design-cookbook/
>
Received on Friday, 13 January 2012 21:19:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:44 GMT