Maybe openlink can verify but all these linked data  requests are
transformed to sparql describe queries.
And unfortunately, sparql describe does not have a normative definition.
This indicates that the results cannot be deterministic.

I think in VOS forward links are guaranteed but back links not (but not
100% sure)

On Jan 27, 2017 20:19, "Paul Houle" <paul.ho...@ontology2.com> wrote:

> I just tried
>
> http://dbpedia.org/data/David_Bowie.ntriples
>
> and then deserialized this successfully with Jena.  The difference in the
> data is more than just serialization,  because all of the facts in the
> ntriples file have ?s=:David_Bowie whereas the ttl file has facts like
>
> ?someSong dbo:writer :David_Bowie .
>
> The file at
>
> http://dbpedia.org/data/David_Bowie.nt
>
> on the other hand,  looks more like a Turtle file because it has prefixes,
>  unlike a real N-Triples file.  The .json file has back links,  but it is
> in a non-standard format.  The .jsonld file does NOT have the back links.
>
> I fell back on the .xml which does have the backlinks,  even if it makes
> me feel like I have become pond scum,  destroyer of soap.
>
> --
>   Paul Houle
>   paul.ho...@ontology2.com
>
> Try the Ontology2 Edition of DBpedia 2016-04
> https://aws.amazon.com/marketplace/pp/B01HMUNH4Q/
>
>
>
> On Fri, Jan 27, 2017, at 01:45 AM, Dimitris Kontokostas wrote:
>
> Hi Paul, I think this is a serialization issue.
> The IRI is valid as an IRI but cannot be prefixed in turtle. if it was
> serialized as a full IRI it request would be valid.
> Can you try to get it in another format like nt?
>
>
>
> On Fri, Jan 27, 2017 at 12:50 AM, Paul Houle <paul.ho...@ontology2.com>
> wrote:
>
> I turned my attention to somebody more people would care about (I think
> the only person who got a multiple page obituary in The Economist.)
>
> http://dbpedia.org/resource/David_Bowie
>
> I do a request with jena,  which gets the TTL file and gives the error
>
> Exception in thread "main" org.apache.jena.riot.RiotException: [line:
> 781, col: 29] Failed to find a prefix name or keyword: –(8211;0x2013)
>
> As indicated in the error message,  the character in question is an en
> dash,  which is unicode codepoint 0x2013.
>
> dbr:The_Deram_Anthology_1966–1968       dbp:artist      dbr:David_Bowie
> ;
>
> where the dash appears between "1966" and "1968".
>
> I think this is a DBpedia problem because looking at the productions in
> the Turtle Spec
>
> [163s]  PN_CHARS_BASE   ::=     [A-Z] | [a-z] | [#x00C0-#x00D6] |
> [#x00D8-#x00F6] | [#x00F8-#x02FF] | [#x0370-#x037D] | [#x037F-#x1FFF] |
> [#x200C-#x200D] | [#x2070-#x218F] | [#x2C00-#x2FEF] | [#x3001-#xD7FF] |
> [#xF900-#xFDCF] | [#xFDF0-#xFFFD] | [#x10000-#xEFFFF]
> [164s]  PN_CHARS_U      ::=     PN_CHARS_BASE | '_'
> [166s]  PN_CHARS        ::=     PN_CHARS_U | '-' | [0-9] | #x00B7 |
> [#x0300-#x036F] | [#x203F-#x2040]
>
> I don't see the en dash in any of those ranges and I don't see it in the
> list of characters you can escape with a \ so I think you have to encode
> this in something other than prefix form.
>
> Could we get this fixed?
>
> --
>   Paul Houle
>   paul.ho...@ontology2.com
>
> Try the Ontology2 Edition of DBpedia 2016-04
> https://aws.amazon.com/marketplace/pp/B01HMUNH4Q/
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> DBpedia-discussion mailing list
> DBpedia-discussion@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
>
>
>
>
> --
> Kontokostas Dimitris
>
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
DBpedia-discussion mailing list
DBpedia-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion

Reply via email to