Re: BIDI?

Thanks.

That's a good question. The proposal does assume that software supporting
"schemeless" IRIs can periodically update its list of TLDs. For the
foreseeable future, I think that is feasible, especially for web software.
That is, it takes a while for a new TLD to build up presence. In the
meantime, a plaintext program missing that TLD doesn't affect the DNS
functioning of an IRI with it, just the BIDI display of that IRI.

However, we should also consider whether there are other alternatives to
that strategy.

Mark

*— Il meglio è l’inimico del bene —*


On Tue, Apr 26, 2011 at 17:31, Ted Hardie <ted.ietf@gmail.com> wrote:

> Hi Mark,
>
> Thanks for sharing the document.  I note that you believe part of the task
> is to cover cases like "example.com" encountered in plain text, even when
> a scheme is not present.  At least in language contexts with which I am
> familiar, there are a lot of potential non-URIs that have similar patterns.
>  With the likely growth of gTLDs, using the presence of a known TLD string
> will cease to be an effective marker for this.  Is it your thought that
> running this version of the  UBA on all such strings will be effective, even
> if they do not happen to be URIs, because its processing rules are derived
> from those which would run on plain text?
>
> In other words, if I run into the equivalent of  "Find.me" in a RTL
> context, I don't have to know whether this is from the authority section of
> a URI or not?
>
> regards,
>
> Ted Hardie
>
>
> On Tue, Apr 26, 2011 at 4:22 PM, Mark Davis ☕ <mark@macchiato.com> wrote:
>
>> Here are some rough thoughts on how we could handle bidi IRIs.
>>
>> http://goo.gl/QwSoo
>>
>> Feedback is welcome.
>>
>> Mark
>> *
>> *
>> On Wed, Apr 20, 2011 at 23:20, Shawn Steele <Shawn.Steele@microsoft.com>wrote:
>>
>>>   I'm wondering what the current thinking around BIDI IRIs is?  A few
>>> things in draft-ietf-iri-3987bis-05 jump out at me.
>>>
>>>
>>>
>>>
>>>
>>> -Shawn
>>>
>>>
>>>
>>>  
>>>
>>> http://blogs.msdn.com/shawnste
>>>
>>>
>>>
>>
>>
>