[Requests] Comments on OGC API Common (19-072)

Matt Sorenson Msorenson at strategicaci.com
Fri Mar 27 19:18:43 EDT 2020


Not sure if this is the right link but its where the OGC public comment website sent me.


PART A

1. Evaluator:      Matt Sorenson, msorenson at strategicaci.com

2. Submission:  19-072, OGC API - Common

PART B

Item 1 of 7

1. Requirement: [General]

2. Implementation Specification Section number: [Chapter 1, section v]

3. Criticality: Editorial

4. Comments/justifications for changes:

Does OGC policy recommend or require multiple submitters (at least three)? More people supported drafting this and should be listed/credited.

Item 2 of 7

1. Requirement: General

2. Implementation Specification Section number: 9.2

3. Criticality: Major

4. Comments/justifications for changes:

a. Given the constant churn in multiple hackathons, testbeds, and pilots, the use of collections seems confused and incomplete. While the document as written is clear, the in-progress implementations show that additional work to clarify and/or apply them is needed. This is especially true where multiple resources are involved (see specifically Testbed 15 OPF, Vector Tile Pilot, 3D Container Pilot)

b. The list of collection types needs clarification based on in-progress implementations. Are Maps and Tiles spatial resources? How do you handle mixed collections (imagery tiles, vector tiles). If people trying to work with it are having problems, it needs to be revisited.

Item 3 of 7

1. Requirement: General

2. Implementation Specification Section number: 8.4 table 3 and 9.5

3. Criticality: Major

4. Comments/justifications for changes:

Need to expand the discussion on information resources. Review ongoing IP and SP activities. Give examples of informational resources. Even if they are not yet part of standards, indicate whether styles, routing engines, CRS libraries, schema tranforms are considered types of information resources. The intent to provide links or references in table 3 is good but more concrete examples are required.

Item 4 of 7

1. Requirement: General

2. Implementation Specification Section number: 9.4

3. Criticality: Minor

4. Comments/justifications for changes:

As with information resources, the experiences in providing parameter definitions should allow linking to examples, even if they are only information. Link to parameter modules for reuse

Item 5 of 7

1. Requirement: General

2. Implementation Specification Section number: 9.6

3. Criticality: Minor

4. Comments/justifications for changes:

The discussion of CRS only covers how the the default is implemented. Additional instructions on how to extend or modify when needed would be helpful.

Item 6 of 7

1. Requirement: General

2. Implementation Specification Section number: A.3.4

3. Criticality: Minor

4. Comments/justifications for changes:

Test Aa.3.4 is not complete. This should be expanded beyond a feature specific test before publication.

Item 7 of 7

1. Requirement: General

2. Implementation Specification Section number: General

3. Criticality: Major

4. Comments/justifications for changes:

This is definitely an initial standard meant to expand as more APIs are implemented and new modules mature and are ready for reuse. The process for extension and addition is not well outlined in general terms. An API Developer Guide and module/extension registry would be useful.


Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

The information contained in this e-mail and any attachments from Strategic Alliance Consulting, Inc. may contain confidential and/or proprietary information, and is intended only for the named recipient to whom it was originally addressed. If you believe you received this e-mail and/or attachments in error, please notify the sender immediately, delete the e-mail from your computer and do not copy or disclose it to anyone else.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opengeospatial.org/pipermail/requests/attachments/20200327/4537ffd3/attachment.html>


More information about the Requests mailing list