Closed edeutsch closed 1 year ago
knowledge_level and agent_type were not included in Biolink 3.5.0 because it was deemed too disruptive before September. Instead, in Biolink 3.5.0, infores_catalog.yaml has knowledge_level and agent_type curated at a very high level for use in the UI.
ah hmm, okay, well, I don't know what the best solution is here, but at least we all know that MolePro is getting slapped with validator errors for starting to use them.
I wonder if it is not too awkward to have a custom list of exceptions in the validator.
dont_complain_about_these_attribute_type_ids = [ 'biolink:knowledge_level', 'biolink:agent_type' ]
How does that seem?
(cc: @sierra-moxon). I quietly agree with you @edeutsch.
I don't feel it is fair to punish Vlado for being so proactive with the new standards. Kudos to him!
I'll effect the code change sometime today, and issue a fresh Reasoner-Validator release (probably 3.7.3). Let me know if there are any other such use cases to cover today (although I might check the issue tracker for same... just that you know the log jams more intimately than I do at the moment).
resolved by release v3.7.3
So we have this guidance on using fancy annotations biolink:agent_type and biolink:knowledge_level here: https://github.com/NCATSTranslator/ReasonerAPI/blob/1.4/ImplementationGuidance/Specifications/knowledge_level_agent_type_specification.md
And our friends at MolePro are using it already as directed: https://arax.ncats.io/beta/?r=3d5321e2-307c-4317-a596-d731d9bfbb20
But the validator is objecting:
Is this stuff not yet in Biolink 3.5.0 or why is the validator complaining?