Masahide, On 18 Feb 2008, at 14:22, KANZAKI Masahide wrote: >> 3. Use real international characters in the URI, e.g. >> >> <http://dbpedia.org/property/größe> >> >> I'm not quite sure if this is possible. RDF supposedly supports IRIs >> (the new style of i18ned URIs that can contain Unicode letters), and >> XML can certainly use these characters in element names, so it >> *should* be possible. But this is somewhat uncharted territory, >> someone would have to dig through the relevant specs to see what >> exactly is or is not allowed, and from prior experience I would >> expect >> a lot of trouble with tools in our toolchain that are not quite >> Unicode-ready. > > I definitely want this third approach, not only for properties, but > also for the resource names (URIs). %encoded names are totally > unusable for non-western language users. Instead, if DBPedia employs > IRI for those names, it will be really very, very good news for us !
With regard to resource URIs (as opposed to property URIs), it's worth pointing out that Wikipedia itself uses %-encoded URIs for article pages. I think this is a good reason for DBpedia to also stick with %-encoded URIs, because there is some value in the direct correspondence between Wikipedia URIs and DBpedia URIs, just replace http://en.wikipedia.org/wiki/ with http://dbpedia.org/resource/ and it will work. (Most browsers show the international characters when displaying %- encoded URIs, and automatically do the %-encoding when international chars are entered into the URL bar, so it's easy to forget that Wikipedia also does %-encoding everywhere under the hood.) > I have certain amount of experience to use Japanese characters in RDF > URIrefs (IRIs), and found most RDF libraries can handle IRIs. > Exceptions are characters in compatibility areas in Unicode (e.g. > Japanese counterparts to ASCII signs/punctuations etc), which some > libraries cannot use as local name of an URI (not necessarily causes > errors, but cannot generate correct local name). That's good news. > I'd not be able to involve in programming itself, but happy to provide > information as far as I can. Okay, I do have some questions for you. If you serialize a document with Japanese chars in class or property URIs as RDF/XML, how do the characters show up in XML element names? Do they really show up as Japanese characters in the XML names? Are there examples of RDF vocabularies or ontologies that have Japanese characters in URIs? This would be useful for testing purposes. In your experience, does QName expansion usually work with Japanese characters? One of the main attractions with allowing i18n chars in URIs would probably be that you could write SPARQL queries like this: SELECT * WHERE { people:神崎正英 foaf:interest ?interest . } Does something like that work in practice? Grateful for any information, Richard > > > best regards, > > -- > @prefix : <http://www.kanzaki.com/ns/sig#> . <> :from [:name > "KANZAKI Masahide"; :nick "masaka"; :email "[EMAIL PROTECTED]"]. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Dbpedia-discussion mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Dbpedia-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
