Re: Internationalized local names

Yes, I was thinking more in terms of the link that Felix has sent.

Maybe, we could remove the "local names" and rename the approach as:
"Internationalized paths only" so it will be in line with that link.
Does anyone oppose to that change?

Best regards, Jose Labra

On Wed, Sep 18, 2013 at 10:16 PM, Felix Sasaki <fsasaki@w3.org> wrote:
> Am 18.09.13 22:08, schrieb John McCrae:
>
> Hi,
>
> The issue is really what you mean by local names.
>
>
> I think Jose means the path part of the URI vs. the domain part. See
> http://www.w3.org/International/articles/idn-and-iri/#problem
> The figure below "We will use the following fictitious Web address in most
> of the examples on this page: "
>
> Following that terminology one could say: a best practice is not to use IDN,
> but one is encouraged to use non ASCII characters in the path (if needed).
>
> It may also make sense to have a "basic concepts" section that introduces
> path and domain name by example.
>
> Best,
>
> Felix
>
>
> I think you are referring to the use local names in XML namespaces:
>
> http://www.w3.org/TR/xml-names/
>
> The choices of the namespace and the local name can be decided by the given
> serialization, so I could for example abbreviate
>
> <http://dbpedia.org/resource/test>
>
> As follows (in Turtle)
>
> @prefix myprefix: <http://dbpedia.org/resource/te>
> myprefix:st
>
> And that would work! However, as / is not allowed in such prefixed names, I
> could not do this:
>
> @prefix dbpedia: <http://dbpedia.org/>
> dbpedia:resource/test
>
> Generally, there is a best practice to make the local name as long as
> possible, so we normally see
>
> @prefix dbpedia: <http://dbpedia.org/resource/>
> dbpedia:test
>
> What would make more sense to me is to base the guidelines of this group on
> the structure of a URL, i.e.,
>
> scheme://server:port/path?query#fragment
>
> And we should define best practices for the use of non-ASCII characters in
> the server name, path, query and fragment separately, as these are handled
> differently.
>
> Regards,
> John
>
>
>
>
> On Wed, Sep 18, 2013 at 9:28 PM, Jose Emilio Labra Gayo <jelabra@gmail.com>
> wrote:
>>
>> During today's meeting, there was an issue raised with one of the
>> patterns/best practices.
>>
>> The pattern was called "Internationalized local names" to refer to
>> examples where the domain name is restricted to ASCII characters while
>> local names allow Unicode characters like:
>>
>> http://example.org#Õ€Õ¡ÕµÕ¡Õ½Õ¿Õ¡Õ¶
>>
>> The question that was raised was about the definition of local names.
>>
>> I am not aware of a concise definition of local names in this context.
>> Does anyone have a suggestion on how we could rename this approach? Or
>> how to define what a local name is in this context?
>>
>> Another possibility would be to remove this practice from the table.
>> However, in my opinion, it is good to document this practice because
>> it is employed, for example, by DBPedia International.
>>
>> The goal of this practice is to maintain the domain name in ASCII
>> characters to avoid the visual spoofing attacks while being more
>> liberal in the local names, allowing Unicode characters.
>>
>> Any suggestions?
>>
>>
>> --
>> Best regards, Labra
>>
>
>



-- 
Saludos, Labra

Received on Thursday, 19 September 2013 10:13:11 UTC