W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2013

A very preliminary draft of a URL spec

From: Charles McCathie Nevile <chaals@yandex-team.ru>
Date: Mon, 13 May 2013 04:34:32 +0100
To: "public-webapps WG" <public-webapps@w3.org>
Message-ID: <op.wwzyjudry3oazb@chaals.local>
Hi,

to close ACTION-693 I scribbled some stuff into a very preliminary draft  
of a URL spec:
<https://dvcs.w3.org/hg/webapps/raw-file/81f24bfc5970/url/url.html>

In the end I didn't copy Anne's spec beyond believeing him about some  
Unicode points when I was offline.

So far I have done nothing at all about an API, and am waiting for some  
formal confirmation from people who implement stuff that they would like  
to standardise an API for dealing with URLs. It seems to be a common task,  
judging from the number of people who seem to have some scrap of code  
lying around for it, so I expect to hear people say "Yes, great idea" -  
although I have been surprised before.

As the more astute (read " people who look at the spec for a few seconds  
with at least some level of attention") will notice, this needs work. I  
would be very pleased to receive comments that help clarify things the  
spec gets wrong, doesn't specify, or doesn't explain clearly.

I hope there will be a bugzilla component really very soon, but I  
neglected to request one so far. If Mike happens to be reading, I'd be  
grateful for him to do the magic before I get around to writing the  
request. In the meantime I guess you should just reply to the thread...

And no, it doesn't use futures. Sorry. At some point I will come back with  
the answer to a request for a way to change that.

cheers

Chaals

-- 
Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
       chaals@yandex-team.ru         Find more at http://yandex.com
Received on Monday, 13 May 2013 00:35:03 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:55 UTC