Open gkoum opened 4 months ago
At the risk of pointing out something obvious, there are (at least) three solutions:
/contrib
or /utils
)PaNET-tools
or PaNET-utils
) and accept community contributions.I don't have a strong opinion on which would be the best approach.
Option 1. has the advantage that a commit that introduces a new feature could update both the ontology and the code changes to take advantage of that new feature.
Option 2. has the advantage that we can (easily) offer different access rights and it might make it easier to manage.
Option 3. has the advantage of supporting independent development, removing ourselves as a potential bottleneck.
We need to have a repository for sharing our attempts to utilize(parse, reason, build, query etc) PaNET. A place where such scripts can be shared.
Probably it will need to shelter different approaches from python, java libraries and probably different reasoners. After collecting multiple approaches a docker image can be build to include all dependencies and demonstrate their applicability and differences.