Closed jonnyschaefer closed 3 months ago
This is going to be a though one 🤔 let me think about this. Even when I do not find out how to parse the blank nodes and collections, I should at least check for their presence in the input and return an error so that you can be aware that the output is invalid.
In v1.1.0 I have just introduced a partial support for blank nodes and collection. This still does not make the Bricks.ttl file parse correctly, though.
@jonnyschaefer in the last version v1.1.1 all should be fine and the file https://brickschema.org/schema/1.3.0/Brick.ttl parses correctly.
Hallo again,
If I try to parse the brick schema (open-source ontology for building assets, subsystems and data) turtle file https://brickschema.org/schema/1.3.0/Brick.ttl many broken triples are returned, e.g.:
I think it has to do with two things:
I don't know if those are meant to be supported by this package.
Going with the example from the Turtle Wikipedia page having anonymous blank nodes https://en.wikipedia.org/wiki/Turtle_(syntax)#Example
The parsed triples are:
but should e. g. be (https://www.easyrdf.org/converter):
Note that
is not immediately recognizable as incorrect triple
What are your thoughts on this?