Hey Jim.
Thanks for the response.
By analysis concepts do you mean things like software, algorithm types, etc? If so, that's definitely on the radar. I'm trying to use the draft checklist as a guide ([1] below for those who don't have it). It includes things like alignment & tree inference methods, with software etc subordinate to these.
Treebase already explicitly identifies analyses, analysis steps, inputs, outputs, software, algorithms, etc. A problem I've run into, noted below, is that a majority of the NeXML files I have from Rutger's supertreebase data dump do not utilize these attributes. I need to examine several files manually to see if this data is stored in a different way perhaps- haven't found evidence of this yet. I was expecting 'dirty' data though, so building support for these crucial data points, even if they aren't in many of the files we're using, maybe the best I can do this summer.
Phylont I wasn't familiar with but it looks promising. I'll be looking to Hilmar and the other mentors for guidance here & regarding ontologies more broadly, as this is also a crucial question for the ISA config and I'm not in a position to decide when CDAO vs OBI would be appropriate. There will be a tradeoff between expressivity and complexity in choosing how many/which ontologies to support.
I'll be putting out targeted calls soon, but do you have any comments or recommendations to share, in ontologies or otherwise? You're also welcome to join a call at some point if that's convenient. I may try to schedule a discussion/feedback call in the future if there's a critical mass of interested parties.
Best,
Elliott
[1] MIAPA draft as it stands after the October workshop:
Sent from the ePad