- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 13 May 2013 09:54:17 -0700
- To: Charles McCathie Nevile <chaals@yandex-team.ru>
- Cc: public-webapps WG <public-webapps@w3.org>
On Sun, May 12, 2013 at 8:34 PM, Charles McCathie Nevile <chaals@yandex-team.ru> wrote: > 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. I'm also curious about what the purpose of this draft is. There's nothing wrong with pursuing an idea in multiple places (so long as we settle on one eventually), but this message doesn't even mention what you think is wrong with Anne's spec which your spec is intended to fix. ~TJ
Received on Monday, 13 May 2013 16:55:15 UTC