W3C home > Mailing lists > Public > public-bpmlod@w3.org > September 2013

Re: Internationalized local names

From: Felix Sasaki <fsasaki@w3.org>
Date: Wed, 18 Sep 2013 22:16:36 +0200
Message-ID: <523A0A24.7040200@w3.org>
To: John McCrae <jmccrae@cit-ec.uni-bielefeld.de>
CC: Jose Emilio Labra Gayo <jelabra@gmail.com>, public-bpmlod@w3.org
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 <mailto: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#Հայաստա
>     <http://example.org#%D5%80%D5%A1%D5%B5%D5%A1%D5%BD%D5%BF%D5%A1%D5%B6>
>
>     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
>
>
Received on Wednesday, 18 September 2013 20:17:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:45:36 UTC