RE: IRI and IDN in RDF

Martin:

Thank you.  In addition to "libidn" and "idnkit" there is also an open
source (BSD standard distribution) IDN SDK avaiable in both C and Java
versions from Verisign--I know as my team developed the C lib.

For reference on available libraries please see:
http://www.verisign.com/products-services/naming-and-directory-services/nami
ng-services/internationalized-domain-names/page_002201.html#01000007

Gary.
-----Original Message-----
From: Martin Duerst [mailto:duerst@w3.org]
Sent: Tuesday, January 11, 2005 1:35 AM
To: Krall, Gary; 'Chris Lilley'; Reto Bachmann-Gmuer
Cc: www-international@w3.org
Subject: RE: IRI and IDN in RDF


At 03:45 05/01/08, Krall, Gary wrote:
 >
 >Chris:
 >
 >Just for clarification does your answer imply that an RSS reader would
need
 >to support IDNA to make this work?

If it does resolve IRIs, which I guess most RSS readers do, then yes.
Otherwise no. RDF as such does not require resolution, and therefore
does not require IDNA support.

IDNA support is available in libraries (e.g. libidn or idnkit)
that can easily be integrated into other software (but are a bit
bulky because of the tables needed).

Regards,    Martin.

 >Thanks,
 >
 >Gary.
 >
 >-----Original Message-----
 >From: www-international-request@w3.org
 >[mailto:www-international-request@w3.org]On Behalf Of Chris Lilley
 >Sent: Friday, January 07, 2005 10:36 AM
 >To: Reto Bachmann-Gmuer
 >Cc: www-international@w3.org
 >Subject: Re: IRI and IDN in RDF
 >
 >
 >
 >On Friday, January 7, 2005, 7:23:22 PM, Reto wrote:
 >
 >
 >RBG> Hello
 >
 >RBG> I'm wondering how URLs based on IDN should be represented in RDF/XML:
 >RBG> - no particular encoding (= default of xml document)
 >RBG> - %... encoding
 >RBG> - punycode
 >
 >Since it is XML, the IRI can be expressed in regular characters (the
 >encoding of the document) and conversion to punycode, hex escaping etc
 >can be left to the URI resolver.
 >
 >
 >--
 > Chris Lilley                    mailto:chris@w3.org
 > Chair, W3C SVG Working Group
 > Member, W3C Technical Architecture Group

Received on Tuesday, 11 January 2005 18:26:23 UTC