-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
phase 3: add association
property to /meta_knowledge_graph responses
#599
Comments
association
to BTE's /meta_knowledge_graph response
Where would the association be found for TRAPI apis? |
@rjawesome The TRAPI KPs that we use may provide the However, I suggest working on another issue instead. This one is very low priority and optional. I have edited the opening post to make this clearer and add some detail. This issue also involves getting certain pieces into place first, like x-bte annotation or TRAPI KPs with this in their |
Update notes:
Note: in the TRAPI spec, |
association
property to /meta_knowledge_graph responses
I've posed the "unsure" questions in the opening post and the "TRAPI spec" commentary from the previous post to the TRAPI team here NCATSTranslator/ReasonerAPI#426 edit:
|
Note that COHD's dev instance seems to be on TRAPI 1.4 (we can access it through the registration we currently use, but they also registered a separate yaml for TRAPI 1.4). BUT I didn't see any From my post here: #597 (comment) |
Going to move this to "on-hold" since it seems to be a pretty low-priority issue. Right now, our ARA /meta_knowledge_graph response doesn't have any "association" values. Based on a quick check, TRAPI 1.4 instance meta_knowledge_graphs for COHD, CHP, and Automat KPs (pharos, hetio) don't have "association" values. So it's unclear if our /meta_knowledge_graph response for our ARA should have any "association" values inherited from our TRAPI KPs. I haven't added any x-bte annotation for this property, and I haven't really been asked to. |
With TRAPI 1.4, tools can specify the "type of association" in their
/meta_knowledge_graph
endpoint responses (edges
section). This property isn't being made required, and I'm not aware of a Translator-wide push to add it to as many MetaEdges as possible.This addition to the
/meta_knowledge_graph
MetaEdge info is buried in the MetaEdge qualifier change, which is bullet 4 of the changelog:This involves:
association
annotation to x-bte operations (edit SmartAPI yamls)Association
s that fit them in the biolink-modelBut there's something I'm unsure of:
/meta_knowledge_graph
response? Would that mean ingesting association info from TRAPI KP MetaEdges?association
? This is a hypothetical (not sure if this can actually happen)...The text was updated successfully, but these errors were encountered: