EBISPOT / DUO

Ontology for consent codes and data use requirements
Other
64 stars 15 forks source link

make distributable release that does not include BFO #20

Closed mellybelly closed 5 years ago

mellybelly commented 5 years ago

It is difficult for a naive user (or even an advanced one) to use DUO with all the BFO content in there. no need, it can be in a bridge file.

mcourtot commented 5 years ago

Totally agreed and is in the works :) We've discussed with @simonjupp and @kreinold and will make a "core" release at the next iteration. Relates to https://github.com/EBISPOT/DUO/issues/18 and https://github.com/EBISPOT/DUO/issues/14

mcourtot commented 5 years ago

See https://github.com/EBISPOT/DUO/blob/master/src/ontology/duo-basic.owl If the group agrees this is what we'll load on OLS (with an option to get the full version if desired)

mcourtot commented 5 years ago

@kreinold tested the basic version which works well. Group was happy with it at last call too.