GMOD

Talk:Stock Relationship Ontology

Probably a good idea to keep a history of all suggestions and discussion here, while maintaining the “latest” version on the main page.

main page subheadings

I put in each of the tables that have type_id, but that doesn’t mean that all of these types should have a centrally coordinated CV. It’s up to us to decide (and of course, it’s not compulsory to use the central CV).

API considerations

One benefit of having a centrally maintained CV is that the higher level APIs can make use of them.

CV

Isn’t this really a controlled vocabulary?

At VectorBase we have decided to get a set of terms together and share with GMOD partners ASAP via these wiki pages. Maccallr 14:44, 26 May 2010 (UTC)

Namespaces

Documentation

Community

Tools