- From: Sebastian Hellmann <hellmann@informatik.uni-leipzig.de>
- Date: Sun, 26 May 2013 19:36:22 +0200
- To: Felix Sasaki <fsasaki@w3.org>
- CC: "public-multilingualweb-lt@w3.org" <public-multilingualweb-lt@w3.org>, Phil Ritchie <philr@vistatec.ie>, Leroy Finn <finnle@tcd.ie>
- Message-ID: <51A24816.1030904@informatik.uni-leipzig.de>
Hi Felix, well I did a quick research, but couldn't find a solution to one particular question: The XPointers we use look like this: http://example.com/exampledoc.html#xpath(/doc/para%5B1%5D/span%5B2%5D) I was wondering: 1. Do we need to URL encode the part after # ? 2. should it be "xpath()" or "xpointer()"? I have to say I was confused when seeing this: http://commons.oreilly.com/wiki/index.php/XPath_and_XPointer/XPointer_Syntax#Using_XPointers_in_a_URI If I recall correctly we cleared that issue back then in a meeting, but I can't really remember details. Maybe we should clarify it again and put it in the spec(or at least link it to XPointer/XPath) to document how we derived it? I wasn't able to find any document for it. I am not a regular using of XPath or XML so I do not want to overstep my bounds in this matter. More RDF related stuff in another email. -- Sebastian Am 26.05.2013 18:40, schrieb Felix Sasaki: > Hi Sebastian, all, puttin Phil and Leroy into CC since they are > interested in the NIF testing topic, > > thank you for looking into the NIF section. This is now > https://www.w3.org/International/multilingualweb/lt/track/issues/125 > Most of the issues look pretty clear. All: I will implement them in > the spec on Tuesday if there are no further comments. > > One question, though: are the properties > nif:beginIndex > and > nif:endIndex > stable and does it express the same like "#char" in URIs? That is, > nif:beginIndex "11" > nif:endIndex "17" > is equal to #char=11,17 > ? > > FYI, I added input and output files for testing the NIF conversion, see > https://github.com/finnle/ITS-2.0-Testsuite/tree/master/its2.0/nif-conversion > At Leroy and Phil: since Phil asked for localization quality issue > (and XML) as test files and there was no other request, the input > files are all LQI. That also leads to blank nodes in the output, since > LQI in itsrdf requires these. Sebastian, the order of > "nif:convertedFrom" should be correct in the output > https://github.com/finnle/ITS-2.0-Testsuite/tree/master/its2.0/nif-conversion/expected > Let me know if s.t. is wrong. > > Best, > > Felix > > Am 26.05.13 15:12, schrieb Sebastian Hellmann: >> Dear all, >> We have recently produced a PDF document which gives a pretty good >> overview of NIF: >> http://svn.aksw.org/papers/2013/ISWC_NIF/public.pdf >> >> Furthermore, I have read the ITS 2.0 draft very closely once more >> and brushed up everything regarding NIF. There aren't any significant >> changes. Let's say we are going for "extra credit" ;) >> Please find a list of issues here: >> https://docs.google.com/document/d/1VagqM-Ty69mPYh0wHfkNTVUndOO34ub5cO4X9Eo572Q/edit# >> >> I will have a look at the other sections soon. >> >> All the best, >> Sebastian >> >> >> -- >> Dipl. Inf. Sebastian Hellmann >> Department of Computer Science, University of Leipzig >> Events: NLP & DBpedia 2013 (http://nlp-dbpedia2013.blogs.aksw.org, >> Deadline: *July 8th*) >> Venha para a Alemanha como PhD: http://bis.informatik.uni-leipzig.de/csf >> Projects: http://nlp2rdf.org , http://linguistics.okfn.org , >> http://dbpedia.org/Wiktionary , http://dbpedia.org >> Homepage: http://bis.informatik.uni-leipzig.de/SebastianHellmann >> Research Group: http://aksw.org > -- Dipl. Inf. Sebastian Hellmann Department of Computer Science, University of Leipzig Events: NLP & DBpedia 2013 (http://nlp-dbpedia2013.blogs.aksw.org, Deadline: *July 8th*) Venha para a Alemanha como PhD: http://bis.informatik.uni-leipzig.de/csf Projects: http://nlp2rdf.org , http://linguistics.okfn.org , http://dbpedia.org/Wiktionary , http://dbpedia.org Homepage: http://bis.informatik.uni-leipzig.de/SebastianHellmann Research Group: http://aksw.org
Received on Sunday, 26 May 2013 17:36:58 UTC