W3C home > Mailing lists > Public > public-xg-lld@w3.org > September 2011

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

From: Felix Sasaki <felix.sasaki@dfki.de>
Date: Sat, 10 Sep 2011 12:59:39 +0200
Message-ID: <CAL58czqAHuzcEMQKhp=oC56yuAdUo72CAM+qaCZAtSHjV6L0Xw@mail.gmail.com>
To: Antoine Isaac <aisaac@few.vu.nl>
Cc: "Young,Jeff (OR)" <jyoung@oclc.org>, Tom Baker <tbaker@tbaker.de>, Jodi Schneider <jodi.schneider@deri.org>, Andrew Cunningham <andrewc@vicnet.net.au>, Karen Coyle <kcoyle@kcoyle.net>, duerst@it.aoyama.ac.jp, public-xg-lld <public-xg-lld@w3.org>, public-i18n-core@w3.org
2011/9/10 Antoine Isaac <aisaac@few.vu.nl>

> It is quite long, indeed, and would thus become a focal point of that scope
> section. IRI are worth mentioning, but they are *way* less important for a
> *general* library agenda than Linked Data or Open Data.
> And as Martin mentioned, IRIs is already taken care of in the RDF spec...
>

Well, "taken care" means "taken care in a technical sense". Martin wrote:

[
It's unfortunately somewhat hidden, so you may not be aware of, but in terms
of technology, in particular RDF, what it calls "URIs" are actually IRIs.
Please have a look at http://www.w3.org/TR/rdf-**
concepts/#section-Graph-URIref<http://www.w3.org/TR/rdf-concepts/#section-Graph-URIref>
**.

So (very roughly paraphrased), to write something like "Linked Data uses
URIs (ASCII only), but you might also think about supporting IRIs", would be
wrong. It would be better to write something along the lines ""Linked Data
uses URIs. By definition, this includes IRIs (see Section 6.4 of RDF
Concepts)."
]

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



>
> Thereá also a big "can of worms" flashing next to the sentence that has
> "URL". It's as clearly written as it can be. But for a while, I've made
> presentations to less technical colleagues in libraries, which included in a
> same slide both "URL" and "URI". It has never served me, I can tell you!
>
> Antoine
>
>
>
>  Tom,
>>
>> I'm happy with your amendments.
>>
>> Jeff
>>
>>  -----Original Message-----
>>> From: Tom Baker [mailto:tbaker@tbaker.de]
>>> Sent: Friday, September 09, 2011 4:42 PM
>>> To: Young,Jeff (OR)
>>> Cc: Jodi Schneider; Tom Baker; Andrew Cunningham; Karen Coyle; Felix
>>> Sasaki; duerst@it.aoyama.ac.jp; Antoine Isaac; public-xg-lld; public-
>>> i18n-core@w3.org
>>> Subject: Re: I18n and Linked Data - an important (but fixable)
>>> omission?
>>>
>>> On Fri, Sep 09, 2011 at 03:33:35PM -0400, Jeff Young wrote:
>>>
>>>> A Uniform Resource Identifier (URI) is a compact sequence of
>>>>
>>> characters
>>>
>>>> [in a standardized syntax] that identifies an abstract or physical
>>>> resource. [RFC 3986]. An Internationalized Resource Identifier (IRI)
>>>> [RFC 3987] compliments URIs by including characters from the
>>>>
>>> Universal
>>>
>>>> Character Set (Unicode/ISO 10646). While this report follows common
>>>> Linked Data practice of using the term "URI", readers should note
>>>>
>>> the
>>
>>> increasing prominence of IRIs as non-Latin script resources and
>>>> participants are being joined in the Linked Data environment.
>>>>
>>>
>>> Missing from this definition, as I see it, is a reference to a prefix
>>> ("URI
>>> scheme") that grounds the identifier in a global context.  Perhaps
>>> that's what
>>> the reference to "standardized syntax" is getting at, but I think we
>>> could be a
>>> bit more explicit on this point.  As written, the first sentence could
>>> be taken
>>> to mean that a bare ISBN is a URI, whereas it wouldn't really be a URI
>>> unless
>>> that ISBN number were embedded in a URN, e.g.,: "urn:isbn:0-486-27557-
>>> 4".
>>>
>>> The report also refers to "HTTP URIs", so the point could also provide
>>> an
>>> opportunity to define those (and relate them to the well-known URLs)
>>>
>> as
>>
>>> well.
>>>
>>> How about:
>>>
>>>      *Uniform Resource Identifier (URI)*.  A URI is a sequence of
>>>      characters, in a standardized syntax, which is used to identify
>>>
>> an
>>
>>>      abstract or physical resource within the global context of the
>>> World Wide
>>>      Web.  "HTTP URIs" -- URIs prefixed with "http://", also known as
>>> "URLs" --
>>>      imply that a representation of the resource can be obtained by a
>>> browser
>>>      using the most common Web protocol, HTTP.  While this report
>>> follows
>>>      common Linked Data practice in referring to "URIs", readers
>>>
>> should
>>
>>> note
>>>      the growing role of Internationalized Resource Identifiers
>>>
>> (IRIs),
>>
>>> which
>>>      compliment URIs by supporting non-Latin scripts.
>>>
>>> Hmm, a bit long...?
>>>
>>> Tom
>>>
>>> --
>>> Tom Baker<tom@tombaker.org>
>>>
>>
>>
>>
>>
>


-- 
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>
Received on Saturday, 10 September 2011 11:00:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 September 2011 11:00:12 GMT