W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2014

Re: [whatwg] [url] Feedback from TPAC

From: David Singer <singer@apple.com>
Date: Tue, 4 Nov 2014 15:24:42 +0000
Message-Id: <AB436721-690B-4C01-A12B-54F6E9964E3B@apple.com>
To: Sam Ruby <rubys@intertwingly.net>
Cc: WhatWG <whatwg@whatwg.org>, Graham Klyne <gk@ninebynine.org>

On Nov 4, 2014, at 15:09 , Sam Ruby <rubys@intertwingly.net> wrote:

> On 11/04/2014 09:55 AM, David Singer wrote:
>> I am pretty puzzled why the base URL <stuff://www.app.com/a/b/> composed with the URL <banana> results not in
>> 
>> stuff://www.app.com/a/b/banana
>> 
>> but
>> 
>> stuff:///banana
>> 
>> Is this a bug or feature of the spec., or a bug in this implementation?
> 
> Please refresh.  I've changed the implementation to match the spec. Spoiler alert: the results returned now don't match either of the values you mention above.

banana

really not good.

> Either of those results would be a bug in the implementation. Per the
> specification

proposal;  the existing specification is the RFC

> and dominant URL implementations

at the moment I am more interested in understanding what the best behavior might be than majority voting

> only a limited set of
> schemes support relative URLs.

Not good.  I mean, this means that we would have to change the base generic spec. whenever a new scheme comes along for which relative references make sense.  RFC 3986 is clear that relative references are a general feature.  I am obviously not understanding why it might be desirable to be so future-fragile here.  (Particularly since I am thinking of defining exactly such a scheme).


> 
> - Sam Ruby
> 
>> On Nov 4, 2014, at 14:32 , Anne van Kesteren <annevk@annevk.nl> wrote:
>> 
>>> On Tue, Nov 4, 2014 at 3:28 PM, Sam Ruby <rubys@intertwingly.net> wrote:
>>>> To help foster discussion, I've made an alternate version of the live URL
>>>> parser page, one that enables setting of the base URL:
>>>> 
>>>> http://intertwingly.net/projects/pegurl/liveview2.html#foobar://test/x
>>>> 
>>>> Of course, if there are any bugs in the proposed reference implementation,
>>>> I'm interested in that too.
>>> 
>>> Per the URL Standard resolving "x" against "test:test" results in
>>> failure, not "test:///x".
>>> 
>>> 
>>> --
>>> https://annevankesteren.nl/
>> 
>> David Singer
>> Manager, Software Standards, Apple Inc.
>> 

David Singer
Manager, Software Standards, Apple Inc.
Received on Tuesday, 4 November 2014 15:29:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:32 UTC