Skip to content
This repository has been archived by the owner on Apr 19, 2024. It is now read-only.

Document policy on identifiers #2

Open
Tracked by #611
cmungall opened this issue Aug 30, 2019 · 6 comments
Open
Tracked by #611

Document policy on identifiers #2

cmungall opened this issue Aug 30, 2019 · 6 comments

Comments

@cmungall
Copy link
Contributor

Should NMDC mint new identifiers, or reuse? Does this depend on the source? Do we also maintain mappings, e.g. between gold and ncbi?

@cmungall
Copy link
Contributor Author

I will link ESS-DIVE/ISGN presentation here later

@cmungall
Copy link
Contributor Author

When we use gold IDs etc we should always use CURIEs/prefixed IDs, and have these registered

@wdduncan
Copy link
Contributor

wdduncan commented Feb 9, 2020

Do we want to identify a namespace curie for the URIs?
e.g., nmdc: -> http:purl.nmdc.org

We use append custom obo-style ids.
e.g., nmdc:GOLD_0001, nmdc:EMSL_00001, nmdc:ESS-DIVE_00001 etc.

@cmungall
Copy link
Contributor Author

cmungall commented Mar 5, 2020

Yes, we should use jsonld contexts to map prefixes

but we shouldn't mint new IDs for GOLD. We can register GOLD etc on n2t/identifiers.org

@cmungall
Copy link
Contributor Author

cmungall commented Jan 8, 2021

Update to the above:

but we shouldn't mint new IDs for GOLD. We can register GOLD etc on n2t/identifiers.org

Reddy did this (https://registry.identifiers.org/registry/gold), so identifiers will now resolve

E.g. the CURIE GOLD:Gp0119849

Can be resolved via

http://identifiers.org/GOLD:Gp0108335

This doesn't work on nt2.net though, I will follow up with them

@aclum
Copy link

aclum commented Aug 30, 2023

@cmungall anything left to do here?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants