with error: "Bad syntax: EOF found in middle of path syntax"
this syntax is used in many open source / public domain ontologies for describing ontology / definition versions
if the value of the statement is fully qualified
<http://example.com/data/> myprefix:version <http://www.example.com/ontologies/test/1.18> .
it parses ok, it is the prefix / qname style syntax that throws the parsing error
I noticed this turtle/N3 syntax fails to parse
with error: "Bad syntax: EOF found in middle of path syntax" this syntax is used in many open source / public domain ontologies for describing ontology / definition versions
if the value of the statement is fully qualified
<http://example.com/data/> myprefix:version <http://www.example.com/ontologies/test/1.18> .
it parses ok, it is the prefix / qname style syntax that throws the parsing error