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


From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Wed, 22 May 2013 00:57:08 +0200
To: "Charles McCathie Nevile" <chaals@yandex-team.ru>
Cc: public-script-coord <public-script-coord@w3.org>, "Lyle Troxell" <lyle@4d.com>
Message-ID: <7srnp8dt94a55mh88vuqtbchd6tvu83bmu@hive.bjoern.hoehrmann.de>
* Charles McCathie Nevile wrote:
>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).

>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...

I would expect anyone trying to model a data type like URIs to be fami-
liar with a large number of existing and popular attempts at the problem
like being familiar with the corresponding interfaces in, say, Perl's
URI.pm, Java, .NET, Qt, and others, to mention a few that I have used.

Above all else, the first and primary problem that needs to be addressed
is how to deal with unknown and unusual schemes or references. Anne van
Kesteren's proposal, for instance, fails to address this. As an example,
it proposes to have a `.origin` property that cannot be implemented, see
my <http://www.ietf.org/mail-archive/web/websec/current/msg01512.html>.
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Tuesday, 21 May 2013 22:57:40 UTC

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