Building on #72, we need a resource type for using published OBO resources. The only configuration we really require for this is the project's IDSPACE. With that we can find and fetch the latest published OWL file from the primary PURL and load it into the KnoDE database. We can also look at the version IRI of the ontology in the database, check for updates, eventually compare the update to the stored version, and decide whether to upgrade.
The knode.edn config file shold also allow specification of a specific version of the OBO project.
Building on #72, we need a resource type for using published OBO resources. The only configuration we really require for this is the project's IDSPACE. With that we can find and fetch the latest published OWL file from the primary PURL and load it into the KnoDE database. We can also look at the version IRI of the ontology in the database, check for updates, eventually compare the update to the stored version, and decide whether to upgrade.
The
knode.ednconfig file shold also allow specification of a specific version of the OBO project.This is very similar to ontofetch functionality.