This is a misleading bit of RDF/XML; it looks as if the object of this triple is the IRI given by the curie gleif-repex:ExceptionReasonKindNoKnownPerson . But it isn't; this is the IRI gleif-repex:ExceptionReasonKindNoKnownPerson; that is, the IRI protocoal is gleif-repex, and the local part is ExceptionReasonKindNoKnownPerson. riot catches this, because protocol names in IRIs aren't supposed to be hyphenated. It's able to pretend to know what it means, so you get some output, but this just kicks the can down the road.
Correct would be
The problem with this is that there are thousands of these expansions, and the JDK has a limitation when it reads XML for how many of them it will do (64K. That's what the error message says; I guess that makes it true)
So, the really correct way to do this is
which represents the same IRI, but uses no expansion of any kind.
If you look at https://data.world/gleif/lei-data/workspace/file?filename=RepExData.rdf , you'll find expressions like this:
This is a misleading bit of RDF/XML; it looks as if the object of this triple is the IRI given by the curie gleif-repex:ExceptionReasonKindNoKnownPerson . But it isn't; this is the IRI gleif-repex:ExceptionReasonKindNoKnownPerson; that is, the IRI protocoal is gleif-repex, and the local part is ExceptionReasonKindNoKnownPerson. riot catches this, because protocol names in IRIs aren't supposed to be hyphenated. It's able to pretend to know what it means, so you get some output, but this just kicks the can down the road.
Correct would be
The problem with this is that there are thousands of these expansions, and the JDK has a limitation when it reads XML for how many of them it will do (64K. That's what the error message says; I guess that makes it true)
So, the really correct way to do this is
which represents the same IRI, but uses no expansion of any kind.