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

Re: A URL API

From: Darin Fisher <darin@chromium.org>
Date: Fri, 17 Sep 2010 11:16:27 -0700
Message-ID: <AANLkTik8dgOLdBCUA1NG5hF6VmfCP+dOHhYueYNHhhQh@mail.gmail.com>
To: Adam Barth <w3c@adambarth.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, Anne van Kesteren <annevk@opera.com>, Boris Zbarsky <bzbarsky@mit.edu>, WebApps WG <public-webapps@w3.org>
On Fri, Sep 17, 2010 at 11:05 AM, Adam Barth <w3c@adambarth.com> wrote:

> On Fri, Sep 17, 2010 at 10:27 AM, Adam Barth <w3c@adambarth.com> wrote:
> > On Thu, Sep 16, 2010 at 3:25 PM, Darin Fisher <darin@chromium.org>
> wrote:
> >> On Thu, Sep 16, 2010 at 6:31 AM, Julian Reschke <julian.reschke@gmx.de>
> >> wrote:
> >>> That sounds good to me. In general I think it would be great if there
> were
> >>> standard APIs for URI/IRI construction, parsing and resolution...
> >>
> >> Yes, that sounds pretty good to me too.
> >
> > This has annoyed me for a while too.  I'll write up a spec.
>
> Here's a sketch:
>
>
> https://docs.google.com/document/edit?id=1r_VTFKApVOaNIkocrg0z-t7lZgzisTuGTXkdzAk4gLU&hl=en
>
> Adam
>

Nice!  Is there any implicit unescaping done when reading those members?
 I'd hope for the answer to be "no" :-)

When does canonicalization happen?  Only when you call href?  Or, does it
happen when you readback any attribute?

-Darin
Received on Friday, 17 September 2010 18:16:58 GMT

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