-
Notifications
You must be signed in to change notification settings - Fork 0
Issues: ogcscotts/TC-Meeting-topics
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
How can we increase Geospatial’s role in defining our view of Metaverse?
#270
opened Oct 2, 2023 by
ogcscotts
Should the OWS Context SWG be reactivated and recharted to adapt the standard to OGC API Standards?
#269
opened Oct 2, 2023 by
ogcscotts
The need to establish a policy for the governance of building blocks.
#267
opened Oct 2, 2023 by
ogcscotts
Is the “fundamental model” of geospatial 2D or 3D or 4D or more D?
#266
opened Oct 2, 2023 by
ogcscotts
One of the factors contributing to the success of the OGC APIs is that the standards are purposely written to be “developer friendly”. This means that the standards are written to leverage existing tooling (e.g. OpenAPI, OpenLayers) and existing Web standards that are maintained outside the OGC. An implication of this is that OGC standards sometimes have to make accommodations for the tooling or standards. The question then arises to what extent such accommodations should be made especially when they lead to what some SWG members might consider sub-optimal design.
#265
opened Jun 12, 2023 by
ogcscotts
Automated processes: validation, conformance testing, and schema translation.
#263
opened Jun 12, 2023 by
ogcscotts
Complimentary Architectures for EO Use and Processing, AI, and emerging Best Practice for Common Band Names
#261
opened Jun 12, 2023 by
ogcscotts
Should the OGC-NA deprecate all registered HTTP URIs and register their HTTPS URI equivalents?
#257
opened Jun 12, 2023 by
ogcscotts
Document a high level abstract conceptual model for time to underpin future dynamic features
#256
opened Oct 6, 2022 by
ogcscotts
Currently the URIs of items registered in the Definitions Server are of the form MAJOR.MINOR meaning that requests are directed to the latest minor revision of a document (MAJOR.MINOR). Should it instead be configured to direct requests to the latest patch (MAJOR.MINOR.PATCH)?
#250
opened Oct 6, 2022 by
ogcscotts
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.