W3C home > Mailing lists > Public > public-device-apis@w3.org > August 2009

RE: Editors, Requirements, Style, etc.

From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Tue, 4 Aug 2009 17:42:11 +0200
To: Robin Berjon <robin@robineko.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <FAA1D89C5BAF1142A74AF116630A9F2C2890AF8728@OBEEX01.obe.access-company.com>
Hi Robin, Frederick, All,

Additionally to volunteering to work on APIs I would also be interested in contributing to the specification of the security policy, as the Policy and APIs should together constitute one coherent model.
All of these, of course, if time allows.

Thanks.

Kind regards,
Marcin

Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452  |  Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanclik@access-company.com

-----Original Message-----
From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of Robin Berjon
Sent: Tuesday, August 04, 2009 4:28 PM
To: public-device-apis@w3.org
Subject: Editors, Requirements, Style, etc.

Hi,

while this WG will only get into full swing closer to the end of
August when people are back from vacation, we should try to get a
number of things out of the way earlier so we don't get bogged down in
administrativia later.

First of all, I should make it clear that this WG will operate more or
less with two hemispheres: API and Policy. I won't take the brain
metaphor too far lest we fall into Starship Troppers references too
fast, but the two are linked and communicate but can also operate
independently (so that if you're only interested in one side, you
don't have to sift through too much crud from the other).

Frederick is handling the Policy side, while I'll do APIs. That being
said if you need to talk to the chairs about something, please copy
both of us as we intend to be able to cover for each other's side.

The rest of this email is largely about the API side of things, though
should it inspire you to talk about Policies by all means go ahead.

There are quite a few APIs that we need to specify, and it would be
nice (to say the least) if they had some form of coherence. As a
result, the plan for the API specifications is that rather than having
one or two editors per API, we have a pool of editors for all of them.
So far the following have heroically volunteered:

   Daniel Coloma, Telefónica de España
   Marcin Hanclik, Access
   myself

If you have objections to these people editing, please voice them now
or forever keep them in your drafts folder.

We very much welcome other volunteers - we'll need a fair amount of
editing power to get all those documents out in time. The pool will be
kept up to date at: http://www.w3.org/2009/dap/editor-pool.html.

Where the specifications are concerned, we've already had an
interesting thread covering some of the difference between the Nokia
and BONDI APIs. I wonder if it might not be simpler to list the
requirements that led to the creation of these APIs, alongside other
requirements that people may have? It would help define an target to
be met (and features to be pushed off to future versions) for these
specifications.

Finally I would like all of you to think about API style (e.g. the way
in which arguments are passed) ahead of starting, and invite anyone
with a strong opinion on the matter to post about it now.

Thanks!

--
Robin Berjon
   robineko - setting new standards
   http://robineko.com/





________________________________________

Access Systems Germany GmbH
Essener Strasse 5  |  D-46047 Oberhausen
HRB 13548 Amtsgericht Duisburg
Geschaeftsfuehrer: Michel Piquemal, Tomonori Watanabe, Yusuke Kanda

www.access-company.com

CONFIDENTIALITY NOTICE
This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the
individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited.
If you have received this document in error, please notify us promptly by responding to this e-mail. Thank you.
Received on Tuesday, 4 August 2009 15:42:59 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:38 UTC