You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that NamespaceManager got an init parameter, bind_namespaces. One of the values for this param is "cc", which the documentation indicates that would be for getting namespaces from prefix.cc. I'm wondering what the thought process is on this: is there a feature design somewhere that I missed? I'm concerned that this website should be a dependency of this component when getting prefix.cc prefix bindings is something you can already do without any interface change. If one wanted to add prefixes from this site, they could do that themselves without cluttering the interface of RDFLib.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I noticed that
NamespaceManager
got an init parameter,bind_namespaces
. One of the values for this param is "cc", which the documentation indicates that would be for getting namespaces from prefix.cc. I'm wondering what the thought process is on this: is there a feature design somewhere that I missed? I'm concerned that this website should be a dependency of this component when getting prefix.cc prefix bindings is something you can already do without any interface change. If one wanted to add prefixes from this site, they could do that themselves without cluttering the interface of RDFLib.Beta Was this translation helpful? Give feedback.
All reactions