Closed jonnyschaefer closed 5 months ago
Hello, thank You very much for finding this out!!!
There is multiple issues and I am currently working on fixing them all. Will let you know when the fix is ready.
The whole file that you provided should now be parsed fine when using the latest tag v1.0.3. Could you please try out?
Hello,
Thank you. I really appreciate the fix. I can now parse the file completely.
What I noticed is that when outputting the triples, some IRI fragments start with a slash, and some do not.
E.g. http://www.w3.org/1999/02/22-rdf-syntax-ns#type
and http://www.w3.org/1999/02/22-rdf-syntax-ns#/Property
.
I do not think that the /
is correct here, but I am not too familiar with the turtle standard.
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix schema: <https://schema.org/> .
schema:identifier a rdf:Property ;
rdfs:label "identifier" ;
rdfs:comment """The identifier property represents any kind of identifier for any kind of [[Thing]], such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See [background notes](/docs/datamodel.html#identifierBg) for more details.
""" ;
owl:equivalentProperty dcterms:identifier ;
schema:domainIncludes schema:Thing ;
schema:rangeIncludes schema:PropertyValue,
schema:Text,
schema:URL .
results in
Subject: https://schema.org/identifier
Predicate: http://www.w3.org/1999/02/22-rdf-syntax-ns#type
Object: http://www.w3.org/1999/02/22-rdf-syntax-ns#/Property
Subject: https://schema.org/identifier
Predicate: http://www.w3.org/2000/01/rdf-schema#/label
Object: identifier
...
Hello,
thank you for providing this package. I noticed that it does not parse https://schema.org/version/latest/schemaorg-current-https.ttl correctly.
The following code shows triples, that don't have a schema.org IRI as subject, i.e. places where Subject/Predicate/Object fields are confused:
Output:
I have not yet found the issue, but if it seems to break with this entry:
I hope that this helps improving this package.