it would be a powerful feature for aberowl if you were able, via the API, to access entities referred to in the database cross references described by classes, such as to SNOMED, ICD-X, UMLS, etc.
for 'databases' that are ontologies in aberowl, it should be quite easy. medical terminologies harder: as I understand it, one of the major problems is that we don't have any licence agreement to 'make subsets of them available programmatically', or whatever the licence says.
at the least I think it would make a nice follow-up to the synonym expansion paper... but it would be quite a useful resource, particularly for text mining and such, too.
it would be a powerful feature for aberowl if you were able, via the API, to access entities referred to in the database cross references described by classes, such as to SNOMED, ICD-X, UMLS, etc.
for 'databases' that are ontologies in aberowl, it should be quite easy. medical terminologies harder: as I understand it, one of the major problems is that we don't have any licence agreement to 'make subsets of them available programmatically', or whatever the licence says.
so, how about literally just redirecting the API call to Bioportal? e.g. http://data.bioontology.org/ontologies/SNOMEDCT/classes/http%3A%2F%2Fpurl.bioontology.org%2Fontology%2FSNOMEDCT%2F410607006
at the least I think it would make a nice follow-up to the synonym expansion paper... but it would be quite a useful resource, particularly for text mining and such, too.
bioportal has mappings: https://bioportal.bioontology.org/mappings/show/DOID?target=http://data.bioontology.org/ontologies/HP but i wonder if limiting them to the ones ontologies define themselves would help accuracy etc