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


From: Charles McCathie Nevile <chaals@yandex-team.ru>
Date: Mon, 20 May 2013 03:19:13 +0400
To: public-script-coord <public-script-coord@w3.org>
Cc: "Lyle Troxell" <lyle@4d.com>
Message-ID: <op.wxctqbv3y3oazb@chaals.local>

instead of asking this group to review my proposed API, I think there are  
a fair few designs for URI APIs around already. I am co-editing a URL  
specification for the Webapps group, and we assume that it should include  
an API for working with URLs (or URIs).

The very rough editor's draft is at  
https://dvcs.w3.org/hg/webapps/raw-file/default/url/url.html and the goal  
is to describe the URI schemes needed for the Web. This is in large part a  
case of referring to existing work. The syntax is generally described in  
IETF specifications, although as far as I can tell there is a great  
"generic URI syntax" spec in RFC 3986 that effectivelyt covers HTTP, but  
nothing specifically clarifying HTTP, and how it differs from for example  
FTP (primarily in the first / first two characters of the "scheme"  
component) or tel: (more or less everything except the colon).

I note that Anne van Kesteren's draft of a URL spec includes a draft of an  
API, that I believe is based on existing work, and that this is a common  
problem people have set out to solve.

So I would be grateful for guidance on which models make sense and which  
have problems (and what they are) before we even propose an API and  
request review...



Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
       chaals@yandex-team.ru         Find more at http://yandex.com
Received on Sunday, 19 May 2013 23:19:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:13 UTC