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
In my opinion, this should be done through content negotiation on the ontologies URI (which is already displayed in the generated HTML). That would be following best-practices. Providing such serializations through the HTML documentation, would make it less likely that people would implement through content negotiation, and thus it would promote an anti-pattern.
Doing it through content negotiation is the most natural way of providing different serializations, and it makes the ontology machine-readable.
... What could be useful though, if it was possible in HTML (I don;t know) to make links that request a specific content-type, so then we could combine the two, and the links not working would then be a good thing, as it would mean people would report that, and thus the ontology maintainers would be pressured to implement correct content negotiation.
Yes, both should be possible. The content negotiation does not preclude explicit IRIs that result in the same download. (I think there is a standard practice for including the requested format after the IRI.)
It would be nice for the end-user to provide a download link in the documentation to one or more rdf serializations of the ontology.
The text was updated successfully, but these errors were encountered: