You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@jerdeb@badmotor the bad thing about LODE is that it relies on the ontology to be published somewhere, or uploaded, as it fetches it using JavaScript. Whereas SpecGen generates static HTML, which, I think, would fit better into an automated workflow. (However I checked the LODE sources; it should be possible to modify them.)
Parrot seems to be more promising: it allows for file upload and gives you a static HTML, so I'll continue with that.
Of course, when using LODE or Parrot, we should first upload our files somewhere, or modify them to generate static HTML offline, as uploading lots of files there is against the netiquette.
BTW here are some reasonable ways to invoke curl with a file upload:
@kurzum thanks for pointing me to https://github.com/NLP2RDF/ontologies/blob/master/publish.sh. Indeed LODE is a great documentation tool to consider. As we do not yet have a web server in place I modified the invocation so as to upload a file to the server where LODE is running, but actually for our ontology (sources at https://github.com/mobivoc/mobivoc/), LODE's documentation generated from the uploaded file is empty, and right now I do not have time for debugging.
@jerdeb @badmotor the bad thing about LODE is that it relies on the ontology to be published somewhere, or uploaded, as it fetches it using JavaScript. Whereas SpecGen generates static HTML, which, I think, would fit better into an automated workflow. (However I checked the LODE sources; it should be possible to modify them.)
Parrot seems to be more promising: it allows for file upload and gives you a static HTML, so I'll continue with that.
Of course, when using LODE or Parrot, we should first upload our files somewhere, or modify them to generate static HTML offline, as uploading lots of files there is against the netiquette.
BTW here are some reasonable ways to invoke curl with a file upload:
will tell you the URL where to retrieve the HTML documentation.
will download the file (but it's not really useful as it's not static).
The text was updated successfully, but these errors were encountered: