- From: Marcos Caceres <marcosscaceres@gmail.com>
- Date: Wed, 26 Nov 2008 16:08:44 +0000
- To: "Henry Story" <Henry.Story@sun.com>
- Cc: "Dan Connolly" <connolly@w3.org>, "Larry Masinter" <masinter@adobe.com>, "Arthur Barstow" <art.barstow@nokia.com>, "Jon Ferraiolo" <jferrai@us.ibm.com>, "Richard Cohn" <rcohn@adobe.com>, "Bill McCoy" <bmccoy@adobe.com>, "Michael Stahl" <Michael.Stahl@sun.com>, "www-archive@w3.org" <www-archive@w3.org>, "Svante Schubert" <Svante.Schubert@sun.com>, "eduardo.gutentag@oasis-open.org" <eduardo.gutentag@oasis-open.org>, "Philippe Le Hegaret" <plh@w3.org>, "Carl Cargill" <cargill@adobe.com>, "Stephen Zilles" <szilles@adobe.com>, "www-tag@w3.org" <www-tag@w3.org>, public-webapps <public-webapps@w3.org>
Hi Henry, On Wed, Nov 26, 2008 at 9:39 AM, Henry Story <Henry.Story@sun.com> wrote: > On 25 Nov 2008, at 21:01, Dan Connolly wrote: > >> In the recent join TAG/WebApps ftf session, I learned that >> a lot of that other stuff is not so unrelated. >> >> http://www.w3.org/2008/10/20-wam-minutes.html#item12 >> (Marcos's slides are attached to those minutes thru >> a rather indirect route, so here's a more direct link: >> >> http://lists.w3.org/Archives/Public/public-webapps/2008OctDec/att-0299/TPAC_URISchemes.pdf ) >> >> Software installation security policy requirements seem to dominate, >> for the purpose of WebApp widgets. I was surprised to learn that >> URIs using the scheme they have in mind aren't actually written down in >> absolute form; they're sort of conjured up at run-time, and it >> can lead to security/privacy problems if anybody else learns >> about them. Are those requirements relevant to ebook scenarios? > > I don't think they are relevant to the Open Office scenario. > > There the main problem is just that we would like to use relative URIs for > RDF inside the OpenOffice document package, and have a clear way of > transforming those into full URIs, so they can then be merged with other > information on the web. > > It seems that jar: urls both work quite well, and are well deployed in this > case. They also have been used to what amounts to something similar to a > widget, a java applet. > > Jar file formats are specified here: > http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html > I found a Jar URLs syntax proposal here: > http://pirlwww.lpl.arizona.edu/resources/guide/software/JavaHelp/Specification/misc/Jar.html > > > >> Oh... perhaps they are... I see earlier in this thread: >> "I seem to recall that we used some sort of scheme during the processing >> of a Mars document but didn't persist it in the file." > > I guess the thing would then be to build on jar: and make sure that it conforms to the URI Generic Syntax spec (and make sure it covers all the use cases). If we build on jar:, we also need to specify how to do the encoding to and from package to operating environment, etc. Current jar/zip implementations make a mess of this [1], and that is a real concern for WebApps from an i18n perspective. Kind regards, Marcos [1] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4244499 -- Marcos Caceres http://datadriven.com.au
Received on Wednesday, 26 November 2008 16:09:32 UTC