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 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.
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.
We are currently leaning on the INCLUDE standard for
see_also
andaliases
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?
The text was updated successfully, but these errors were encountered: