- From: Marcos Caceres <marcosscaceres@gmail.com>
- Date: Sat, 21 Jun 2008 15:46:25 +1000
- To: "Williams, Stuart (HP Labs, Bristol)" <skw@hp.com>
- Cc: "Jon Ferraiolo" <jferrai@us.ibm.com>, "public-appformats@w3.org" <public-appformats@w3.org>, "public-appformats-request@w3.org" <public-appformats-request@w3.org>, "www-tag@w3.org" <www-tag@w3.org>, "Larry Masinter" <LMM@acm.org>
On Fri, Jun 20, 2008 at 9:29 PM, Williams, Stuart (HP Labs, Bristol) <skw@hp.com> wrote: > Hello Marcos, > >> Regardless, we need the TAG's support resolving this >> issue sooner than later. > > We discussed this topic on our June 19th call. > > The TAG is interested in working with you to address the more general problem of referring to items within a packages - something that would generalised for .jars, .zip and the like. We expect that doing so would also address the needs that motivate the wiget URI scheme you are currently proposing. > Sounds like a great idea. > Can you be more specific about the TAG support you need? Firstly, thank you for taking the time to discuss this within the TAG. As a starting point, those in the TAG who are willing to help may like to look at section 4 and 5 of our packaging spec: http://dev.w3.org/2006/waf/widgets/#zip-archive http://dev.w3.org/2006/waf/widgets/#widget0 With regards to the URI scheme, the requirement the WebApps working groups has is as follows (copied from [1]): R5. Addressing Scheme A conforming specification must specify or recommend an addressing scheme to address the individual resources within the widget resource at runtime. The addressing scheme must be able to address individual widget instances, while potentially allowing widgets to address each other. The addressing scheme must not expose the underlying file system to the instantiated widget and an instantiated widget must not be able to address resources outside the widget resource via the addressing scheme. The addressing scheme should be one that web authors would feel comfortable using or are already accustomed to. Motivation: Ease of use, compatibility with other standards, current development practice or industry best-practices, security. Rationale: To allow resources to be resolved and normalized within DOM attributes. To make it easy for authors to address and load resources into their instantiated widgets, either declaratively or programmatically. For example, addressing a resource via an IRI (eg. new Image('../images/pane.png')). --- It might also be of value for people to review our design goals and requirements, particularly requirements related to the packaging format. Kind regards, Marcos [1] http://dev.w3.org/2006/waf/widgets-reqs/#r5.-addressing -- Marcos Caceres http://datadriven.com.au
Received on Saturday, 21 June 2008 05:47:09 UTC