Create a cvs file of the ontology during release

[marieALaporte]

The file will be used by non-ontology experts. Ideally the file should not contain top level classes that can be confusing for agronomists.

[KrishnaTO]

Creating a csv report on useful terms seems exactly what ENVO does using SPARQL reports creation pipeline, linked in #10 and

https://github.com/AgriculturalSemantics/agro/issues/10#issuecomment-223766814

Since the "subset reports" will be SPARQL-driven, perhaps the other reports from #11 can be done en passant:

Over in ENVO, we create simple tabular files for non-owl-inclined software developers to work with. These are dubbed "reports" and are simplistic exports of the ontology content. As this is SPARQL-driven (via arq and jena), perhaps you'd like to take a crack at impementing (and improving?) this @marieALaporte? Our sparql files produces reports. The Makefile drives this in these lines

@KrishnaTO to review ENVO's make recipe for reports BioPortal's csv file likely built using OWLAPI