W3C home > Mailing lists > Public > public-i18n-core@w3.org > July to September 2011

Re: I18n and Linked Data - an important (but fixable) omission?

From: Karen Coyle <kcoyle@kcoyle.net>
Date: Sat, 10 Sep 2011 08:04:45 -0700
Message-ID: <20110910080445.731720almcab5hu5@kcoyle.net>
To: Felix Sasaki <felix.sasaki@dfki.de>
Cc: Andrew Cunningham <andrewc@vicnet.net.au>, duerst@it.aoyama.ac.jp, public-xg-lld <public-xg-lld@w3.org>, public-i18n-core@w3.org
Quoting Felix Sasaki <felix.sasaki@dfki.de>:

> The output of the library linked data group will not be a technical, formal
> specification. It plays an important *educational role* about libraries and
> linked open data. As such, I think the point of the statement Martin made
> ""Linked Data uses URIs. By definition, this includes IRIs (see Section 6.4
> of RDF Concepts)."
> is very important. There is still a lot of confusion about the relation
> between URI and IRI, as this thread has shown, too.
> Felix

While this may be a "teachable moment" please keep in mind that this  
report will be read by a lot of folks who are not familiar with the  
term "URI." That concept has not penetrated the library world since  
URIs are not currently used in library data. So the library audience  
has few if NO assumptions about the technical details of a URI, and  
many of them will stumble mentally whenever the term is used in the  
report ("What was that again?"). Adding IRI to this report is not  
going to make things clearer for that group.

I support the brief mention that is given above, although at no other  
point in the report do we cite RDF documentation, if I recall  
correctly. In the context of this particular report, it might be best  
to spell out IRI in this one sentence, followed by "which can use most  
characters from the Unicode character set." This audience *IS*  
familiar with Unicode.


Karen Coyle
kcoyle@kcoyle.net http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet
Received on Saturday, 10 September 2011 15:05:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:01:49 UTC