W3C home > Mailing lists > Public > public-iri@w3.org > May 2012

Re: comments on draft-ietf-iri-bidi-guidelines [forwarded by moderator]

From: Slim Amamou <slim@alixsys.com>
Date: Tue, 8 May 2012 13:59:35 +0100
Message-ID: <CA+8D4LA+3X9eC260ktZ_Ti9MdSZdpEkNM+oUb-DUuZU3783GgQ@mail.gmail.com>
To: Matitiahu Allouche <matitiahu.allouche@gmail.com>
Cc: "public-iri@w3.org" <public-iri@w3.org>
This is clearly dependent on scheme. We could define it for URLs for
example, but that needs to be in another RFC

On Tue, May 8, 2012 at 12:45 AM, "Martin J. Dürst"
<duerst@it.aoyama.ac.jp>wrote:

> (...)
>
> The document does not specify what the announced restrictions are (and the
> reference to RFC3987bis does not clarify anything, for me at least).
>
> My guess is that the authors are in favor of some special handling that
> would prevent interference between components (what appears between
> delimiters), but this is not detailed, and of course that would harm the
> transparency requirement.
>
>
> In fact, what is sorely missing is a precise definition of how an IRI with
> domain, path, fragment and query all potentially including RTL characters
> should be displayed. The problem is that currently there is no consensus on
> that matter. Since the target is not clearly painted, the arrow does not
> know where to go.
>
>
-- 
Slim Amamou | سليم عمامو
http://alixsys.com
Received on Tuesday, 8 May 2012 13:00:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 May 2012 13:00:10 GMT