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

RE: API design style issues

From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Wed, 26 Aug 2009 21:49:33 +0200
To: Robin Berjon <robin@robineko.com>, DAP <public-device-apis@w3.org>
Message-ID: <FAA1D89C5BAF1142A74AF116630A9F2C2890C65BC6@OBEEX01.obe.access-company.com>
Hi Robin, All,

There is a new version of the below document at:
but the section 2 is the same.

As you may know, in BONDI we have identified a few other possible API design patterns.
They will surely propagate to DAP soon.


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 25, 2009 3:15 PM
Subject: API design style issues


I raised a few issues about API design style (ISSUE-1, ISSUE-2,
ISSUE-3, and ISSUE-4)*.

I would like to get these out of the way as early as possible so that
we can avoid many bikeshed discussions down the line, and also so that
we can sustain a modicum of consistency across the APIs that we produce.

I leave it to the group to reach consensus on various approaches, but
one input that we should take into account is the document that Marcin
wrote for BONDI, most notably section 2 on WebIDL patterns:


* Quick note of explanation, when text like ISSUE-X or ACTION-X
appears in an email, it gets tracked in the corresponding issue or
action on the group's tracker which is at: http://www.w3.org/2009/dap/track/
. Try to mention those (in body or subject) when discussing an issue
or action.

Robin Berjon
   robineko - setting new standards


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


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 Wednesday, 26 August 2009 19:50:32 UTC

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