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 10:20:40 -0700
Message-ID: <20110910102040.5443716t9ht9li7c@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>:

> This is written in German
> http://nestor.sub.uni-goettingen.de/handbuch/artikel/nestor_handbuch_artikel_336.pdf
> but see page 47:
> "Die DNB verwendet als Schema für die Identifizierung digitaler Ressour- cen
> den *Uniform Resource Name *(URN)."
> "Der URN ist ein *Uniform Resource Identifier *(URI)"
> That is, the German national library uses URN for identifying digital
> resources. URNs are URIs.
> And of course there is "*RFC 3188*, Using National Bibliography Numbers as
> URNs" - also defining a kind of URN - that is, a URI.
> RFC 3188 is nearly 10 years old ...  So I would disagree with your statement
> above about the penetration of URIs in the library world. It is just the
> knowledge that is missing about the relation between URNs, URIs, and IRIs.
> The report of this group is the perfect place to make that relation clearer
> - if not in detail, then at least with pointers to details.

Felix, I know you don't want to believe me, but I write for and  
lecture to large groups of librarians as my primary activity. A single  
RFC is hardly proof of wide-spread penetration.

As we have created this report we have tried very hard to aim it at a  
broad audience and to make it accessible to that audience. We have  
edited out a whole lot of language that those of us in the group use  
daily but that we know will make the report less accessible to our  
target audience. It's a tricky moment for libraries and library  
culture, and we really do want this community to embrace linked data.  
I believe that the language that I proposed will be understood by the  
folks we want to reach.


>> 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 disagree, see above.
> Regards,
> Felix
>> 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.
>> kc
>> --
>> Karen Coyle
>> kcoyle@kcoyle.net http://kcoyle.net
>> ph: 1-510-540-7596
>> m: 1-510-435-8234
>> skype: kcoylenet
> --
> Prof. Dr. Felix Sasaki
> Senior Researcher, Language Technology Lab
> DFKI GmbH, Alt-Moabit 91c, 10559 Berlin, Germany http://www.dfki.de
> phone: +49-30-23895-1807 (fax: -1810)
> ------------------------------------------------
> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
> Firmensitz: Trippstadter Strasse 122, D-67663 Kaiserslautern
> Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
> (Vorsitzender), Dr. Walter Olthoff
> Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
> Amtsgericht Kaiserslautern, HRB 2313
> Register for the W3C MultilingualWeb Workshop!
> Limerick, 21-22 September 2011
> http://multilingualweb.eu/**register <http://multilingualweb.eu/register>

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 17:21:25 UTC

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