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
In the knowledgebase we employ many prefixes in our data models (JSON, LinkML). We would like to pull in resources with an associated BICAN PURL (e.g., /taxonomy/CCN202210140) as well. This can lead to confusion if the labels are relatively close (NCBITaxon vs. CCN taxonomy).
As a preemptive measure, could we add some language that would encourage distinctness/discourage confusion with the PURL namespaces? Perhaps something like:
If you propose a new namespace or prefix through this system, please take care to ensure that your proposed namespace or prefix is unique and is not easily confused with another, existing, namespace or prefix already in use. Bioregistry is a good place to look if you would like to check if a namespace or prefix is already in use.
In the knowledgebase we employ many prefixes in our data models (JSON, LinkML). We would like to pull in resources with an associated BICAN PURL (e.g., /taxonomy/CCN202210140) as well. This can lead to confusion if the labels are relatively close (NCBITaxon vs. CCN taxonomy).
As a preemptive measure, could we add some language that would encourage distinctness/discourage confusion with the PURL namespaces? Perhaps something like:
If you propose a new namespace or prefix through this system, please take care to ensure that your proposed namespace or prefix is unique and is not easily confused with another, existing, namespace or prefix already in use. Bioregistry is a good place to look if you would like to check if a namespace or prefix is already in use.
@satra @lydiang
The text was updated successfully, but these errors were encountered: