RE: Discussion on WebApps APIs (ACTION-461)

Hi Dan,

This seems to be the latest publicly available version designed initially for BONDI:
http://bondi.omtp.org/1.1/apis/BONDI_Interface_Patterns_v1.1.html
Only a few sections are actually applicable to DAP.

Thanks,
Marcin

From: www-tag-request@w3.org [mailto:www-tag-request@w3.org] On Behalf Of Appelquist, Daniel, VF-Group
Sent: Tuesday, October 19, 2010 12:59 AM
To: Robin Berjon
Cc: tag
Subject: Re: Discussion on WebApps APIs (ACTION-461)

Understood - Is there any other document which supersedes it?

Dan


On 18/10/2010 03:23, "Robin Berjon" <robin@berjon.com> wrote:
Hi Dan,

On Oct 18, 2010, at 03:16 , Appelquist, Daniel, VF-Group wrote:
> I've prepared some brief notes for a discussion on WebApps APIs:
>
> http://www.w3.org/2001/tag/2010/10/WebappsAPIDesignNotes.html
>
> After reviewing a number of other documents mostly from the WebApps and Device APIs working groups (recommended reading list at the bottom of that document) my current view is that there is scope for authoring a possible finding on this topic. I believe this finding should attempt to derive best practice thinking from the good work already done particularly in WebApps, and DAP.

Please note that http://dev.w3.org/2009/dap/design-patterns/ which you reference was largely the work of one person and hasn't been touched in a year. I wouldn't consider it to reflect the consensus of the WG.

--
Robin Berjon - http://berjon.com/




________________________________
________________________________________

Access Systems Germany GmbH
Essener Strasse 5 | D-46047 Oberhausen
HRB 13548 Amtsgericht Duisburg
Geschaeftsfuehrer: Kiyoyasu Oishi, 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.