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

Re: Internationalized local names

From: John McCrae <jmccrae@cit-ec.uni-bielefeld.de>
Date: Wed, 18 Sep 2013 22:08:55 +0200
Message-ID: <CAC5njqoWhwcE1h_XLtZacOL53zG1b80_37n89q5MuribNvb5hQ@mail.gmail.com>
To: Jose Emilio Labra Gayo <jelabra@gmail.com>
Cc: public-bpmlod@w3.org

The issue is really what you mean by local names. I think you are referring
to the use local names in XML namespaces:


The choices of the namespace and the local name can be decided by the given
serialization, so I could for example abbreviate


As follows (in Turtle)

@prefix myprefix: <http://dbpedia.org/resource/te>

And that would work! However, as / is not allowed in such prefixed names, I
could not do this:

@prefix dbpedia: <http://dbpedia.org/>

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

What would make more sense to me is to base the guidelines of this group on
the structure of a URL, i.e.,


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


On Wed, Sep 18, 2013 at 9:28 PM, Jose Emilio Labra Gayo

> 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
Received on Wednesday, 18 September 2013 20:09:24 UTC

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