Hi Paul,
thanks for the code! Looks good. A few minor things:
- public static class?
- In the comment, it should be
http://www.apps.ietf.org/rfc/rfc3987.html ,
not http://www.apps.ietf.org/rfc/rfc3986.html :-)
- I think Integer.toHexString(0x00FF (int)b)
may generate one-character codes.
- If
Richard,
is that URLs containing '' lead to broken (non-well-formed) RDF/XML.
Only if the XML serializer is broken - '' must be
encoded, that's standard practice in XML. There
was a problem in Virtuoso, but that has been fixed:
http://sourceforge.net/mailarchive/message.php?msg_id=28876318
In
Dear all,
I just checked a few specs to figure out what would be the best policy
for DBpedia regarding URI encoding.
In summary, I think DBpedia should encode as few characters as
possible, e.g. use '', not '%26'.
The URI spec [1] has a lot of special cases, but in the end it's quite
clear that
Excellent. I can once again go on a bear hunt with my Culture Grid
hack. :-) [1]
Now with working timeline ... all done with AJAX calls and XSLT 1.0.
Dbpedia data is used to redirect the search term to the relevant BBC
Wildlife concept.
Richard
[1] http://light.demon.co.uk/cg-search.htm
Hi,
I have met the same problem recently, on an example which worked not so
long before (2 weeks top):
http://dbpedia.org/data/Tetris (example from the page
http://wiki.dbpedia.org/OnlineAccess
http://wiki.dbpedia.org/OnlineAccess#h28-13).
If data didn't change recently on dbpedia sparql
Hi Julien,
I have met the same problem recently, on an example which worked not
so long before (2 weeks top):
http://dbpedia.org/data/Tetris (example from the page
http://wiki.dbpedia.org/OnlineAccess)
.
If data didn't change recently on dbpedia sparql endpoint could that
be a server
On 21 February 2012 10:41, Richard Light rich...@light.demon.co.uk wrote:
I've no idea how widespread this is, but I just failed to get a response for
Natural_history because the RDF/XML contains this URL:
http://dbpedia.org/resource/Brevard_Museum_of_History__Natural_Science
and is
On 21 February 2012 13:47, Richard Light rich...@light.demon.co.uk wrote:
Jimmy,
Not, I'm not confused. :-)
Fair enough.
I just thought that if the were URLencoded it wouldn't need to be XML
escaped, because as you say it would then read %26, and so wouldn't cause
problems to the XML
On 21/02/2012 15:40, Paul A. Houle wrote:
If you can wait a month or so a RDF product will be become
available that will will be broadly similar to DBpedia in scope but will
be lacking these problems and most of the other problems too. (Although
it won't have all of those delicious List
