W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: [File API] opaque string

From: Arun Ranganathan <arun@mozilla.com>
Date: Mon, 15 Aug 2011 13:43:58 -0400
Message-ID: <4E495ADE.4020103@mozilla.com>
To: Anne van Kesteren <annevk@opera.com>
CC: WebApps WG <public-webapps@w3.org>
On 8/15/11 12:27 PM, Anne van Kesteren wrote:
> On Mon, 15 Aug 2011 18:06:30 +0200, Arun Ranganathan 
> <arun@mozilla.com> wrote:
>> On 8/14/11 9:00 AM, Anne van Kesteren wrote:
>>> Why can you not use characters legally allowed in IRIs?
>>
>> Are you referring to the "permissible charset" for ranges of 
>> characters or the condition disallowing reserved characters?  I've 
>> only omitted the ones that should be percent-encoded.  Honestly, we 
>> just need terse prose requiring something globally unique; I wanted 
>> to allow the Chrome Team's use of URL-tagging, and largely do allow 
>> it if they percent encode things.
>>
>> Is this nit backed by a use case?  Does Opera wish to URl-tag the 
>> opaqueString production as well, and does escaping characters fall 
>> short of that requirement?
>
> I do not really see why we should be escaping … or other characters 
> outside the ASCII range. After all these URLs are not going over HTTP 
> so we do not have the same restrictions.

These URLs are highly localized, but they also allow for fragment 
identifiers, so the "repertoire" of the opaqueString should be defined 
lest the fragment get hosed.  Being conservative, I reasoned that all 
the reserved chars should be banned.  It sounds like you think 
forbidding the URI-reserved chars is a bad idea.  OK, I'm willing to 
relax this restriction.  Do you have a proposal?
>
> I am not really sure what URL-tagging is in this context and I think 
> Opera can implement whatever is decided. I just would like it not to 
> be something arbitrary.
>

I'm sorry, I should be clearer.  Chrome folks want Blob URLs that look 
like this:

blob:http://localhost/c745ef73-ece9-46da-8f66-ebes574789b1 [1]

This string is still opaque, but seems to be useful to them to "tag" the 
blob URI with some metadata before something like a UUID sequence.  I 
want to allow this, but also want to make fragments valid.  *Enforcing* 
UUID would make my life simpler :)  But this use is also valid.

-- A*

[1] 
http://www.html5rocks.com/en/tutorials/workers/basics/#toc-inlineworkers-bloburis
Received on Monday, 15 August 2011 17:44:33 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT