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
It might be a good idea to, in each part of a multi-part standard, include an "Other parts" section that points to the other parts of the standard. For example, looking at OGC API Features - Part 1 - Core I can infer there are mutliple parts (from the "Part 1") and there is some mention in the text that other parts exist BUT there is no explicit section that references the other parts. This should be a section near the front of the document so that someone looking at it can see that there is also a Part 2 for CRS handling, a Part 3 (when it becomes a standard) for filtering, a Part 4 (when it becomes a standard) for transactions, etc.
Although OGC has gone to great length to create pages on the OGC site that links these parts together I think it would be a good idea if the related parts where themselves cross-linked somehow in a very explicit and obvious way.
The text was updated successfully, but these errors were encountered:
It might be a good idea to, in each part of a multi-part standard, include an "Other parts" section that points to the other parts of the standard. For example, looking at OGC API Features - Part 1 - Core I can infer there are mutliple parts (from the "Part 1") and there is some mention in the text that other parts exist BUT there is no explicit section that references the other parts. This should be a section near the front of the document so that someone looking at it can see that there is also a Part 2 for CRS handling, a Part 3 (when it becomes a standard) for filtering, a Part 4 (when it becomes a standard) for transactions, etc.
Although OGC has gone to great length to create pages on the OGC site that links these parts together I think it would be a good idea if the related parts where themselves cross-linked somehow in a very explicit and obvious way.
The text was updated successfully, but these errors were encountered: