You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The N-Triples writer produces two triples per university which contain relative IRIs, but according to the W3C recommendation this is not allowed - at least not in RDF 1.1:
You can specify --base to RIOT to work around this
These triples are produced by the original code, the code was rewritten to specifically output identical output to the original code (and there are scripts in the repo that test this)
This is not ideal but for correctness wrt to the original code these are essential
Ok, didn't know the reason, but indeed comparability with the original data makes sense.
Regarding RIOT, this doesn't change anything because of
--base=URI Set the base URI (does not apply to N-triples and N-Quads)
which is quite obvious as it was never assumed to have relative URIs in N-Triples. The only drawback is that conversion with RIOT also fails, e.g. if I want to transform it to RDF/XML. But it's ok for me, I just transform the data with sed before.
The N-Triples writer produces two triples per university which contain relative IRIs, but according to the W3C recommendation this is not allowed - at least not in RDF 1.1:
This also leads to errors when using the Jena parser, e.g. with
riot --check ...
it outputs
The text was updated successfully, but these errors were encountered: