ogcapi-features (original) (raw)

I also made some formatting changes in an attempt to improve readabilty. Take a look at these and let me know if you want the same in API-Features.

The change is that you combined multiple requirements into one and created "sub-names" like A, B, etc.? I have concerns about this approach. Separate requirements should remain separate requirements, each with their own URI.

@cportele Can you provide an example of what you have in mind?

I want to be able to have links to each relevant element in the HTML version of the document. Currently I can only reference sections (eg http://docs.opengeospatial.org/DRAFTS/17-069r1.html#string_i18n references 7.10) or select document elements (eg http://docs.opengeospatial.org/DRAFTS/17-069r1.html#tldnr references table 1). I want to extend this so that one can create references to each table, example, requirement, recommendation or permission. And maybe more elements. I.e., there will be an anchor ("[[anchor]]") before every of these elements in the adoc source.