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
We currently automatically generate class registry and imports context URIs as UUID URNs. This is mostly fine except that it's not apparent what these URIs refer to without actually trying to resolve them, which makes debugging somewhat more difficult. URNs, generally, permit three optional components, one of which is called the "r-component" which can hold information for "resolvers" which includes owmeta_core. owmeta_core doesn't need this information to actually resolve the URI and indeed must not use this information over the configuration information from bundles and projects, but including something like "?+context_type=class_registry_context" would be very useful for debugging.
The text was updated successfully, but these errors were encountered:
We currently automatically generate class registry and imports context URIs as UUID URNs. This is mostly fine except that it's not apparent what these URIs refer to without actually trying to resolve them, which makes debugging somewhat more difficult. URNs, generally, permit three optional components, one of which is called the "r-component" which can hold information for "resolvers" which includes
owmeta_core
. owmeta_core doesn't need this information to actually resolve the URI and indeed must not use this information over the configuration information from bundles and projects, but including something like "?+context_type=class_registry_context" would be very useful for debugging.The text was updated successfully, but these errors were encountered: