Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Incorporate References and Aliases from other standards #7

Open
amc-corey-cox opened this issue Mar 10, 2023 · 2 comments
Open

Incorporate References and Aliases from other standards #7

amc-corey-cox opened this issue Mar 10, 2023 · 2 comments

Comments

@amc-corey-cox
Copy link
Collaborator

We are currently leaning on the INCLUDE standard for see_also and aliases of our Base/Core standard. We should try to add other standards for these fields and to ensure that we are creating the central standard that covers multiple core cases that we intend.

One example to include is the BRIDG model as seen in slides here:
https://docs.google.com/presentation/d/10JSdu6BKAXswdHxLZkaeZRHR59TXeDEGbvcJL0_yXUw/edit#slide=id.gdf24c0ee1e_1_200

What other standards should we refer to a build off of to make sure we're meeting our goals here?

@amc-corey-cox
Copy link
Collaborator Author

Look at EDAM and MeSH to evaluate whether they are applicable.

@turbomam
Copy link
Collaborator

turbomam commented Mar 16, 2023

Look at EDAM and MeSH to evaluate whether they are applicable.

Can you give some examples of elements in the cmdr schema for which you would like to map external identifiers? Even if you don't know a EDAM or MeSH mapping yet?

I think we should provide identifiers from those namespaces if there's evidence that they're also being used by other prominent projects. And we can also demonstrate best practices by providing mappings to resources that follow good semantic practices.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants