Non-deterministic prefix creation #1618
nicholascar
started this conversation in
TO-DO list
Replies: 3 comments
|
It is not possible to remove the auto-creation of prefixes because predicates must be qnamed for xml formats. |
0 replies
|
Since raising this issue I've come to realise this... I might make a PR that does remove the auto0binding but then re-applies just-in-time it for XML serlialisation (RDF/XML, TRIX etc). This would be better than what we have now: prefixes as-needed only. |
0 replies
|
There is a related issue, not sure if it is in scope for this particular effort - if serialize the |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Currently RDFib serializes using all bound prefixes - both those that are set automatically like RDF ("rdf") and OWL etc., as well as those you set manually (
g.bind(...)) but also invents some,ns,ns2etc. This invention is problematic as those prefixes are not in the Namespace Manager and won't always be the same between serializations.We should remove the auto-creation of prefixes.
We should also perhaps provide prefixes for all Namespaces/ClosedNamesapces/DefinedNamespaces given that many are well known. If we do, they should be default but able to be overridden manually.
While we are at it: remove the ability to import some Namespaces ("RDF", "RDFS") from rdflib and only use rdflib.namespace.
All reactions