RE: [widgets] Draft Agenda for 30 April 2009 Voice Conference

Hi Robin,

>>  - do we need to say anything about multiple instances of the same
>>widget?
I think so.
Since widget URI is to help in inter-widget communication, I assume it should be clarified on the URI level as well, how different instances are to be handled (or not handled).
What about e.g. inter-widget-instance communication (i.e. communication between two different instances of the same widget)?
Furthermore, as long as it comes to the identification of resources within a widget resource, we may however not want to have such a distinction.

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-webapps-request@w3.org [mailto:public-webapps-request@w3.org] On Behalf Of Robin Berjon
Sent: Thursday, April 30, 2009 1:14 PM
To: Arthur Barstow
Cc: public-webapps
Subject: Re: [widgets] Draft Agenda for 30 April 2009 Voice Conference

Hi,

On Apr 29, 2009, at 16:23 , Arthur Barstow wrote:
> 1. Review and tweak agenda

I'd like to tack the following onto the agenda:

  - who volunteers to handle the the URL path to Zip relative path
mapping (and back)
  - do we need UUIDs in widget URIs
  - general review of widget URIs
  - do we need to say anything about multiple instances of the same
widget?
  - widget URI resolution to contents of a widget (as part of the L10N
model discussion)

--
Robin Berjon - http://berjon.com/
     Feel like hiring me? Go to 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 Thursday, 30 April 2009 12:38:42 UTC