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
On an SRI call @cmungall suggested that this service and node normalization should be fed by the same pipeline. We should have a single ingest pipeline that takes in different vocabularies / ontologies, and collects xrefs or other identity assertions, labels and lexical synonyms, and keeps that all in some form. Could be RDF triples but doesn't really matter IMO.
Then that set of information can be e.g. the starting point for creating a name resolution service. But at that point, I think it makes sense to have a single service that has functions for both id and name lookup. Related to #4
The text was updated successfully, but these errors were encountered:
On an SRI call @cmungall suggested that this service and node normalization should be fed by the same pipeline. We should have a single ingest pipeline that takes in different vocabularies / ontologies, and collects xrefs or other identity assertions, labels and lexical synonyms, and keeps that all in some form. Could be RDF triples but doesn't really matter IMO.
Then that set of information can be e.g. the starting point for creating a name resolution service. But at that point, I think it makes sense to have a single service that has functions for both id and name lookup. Related to #4
The text was updated successfully, but these errors were encountered: