I'd argue that the only services that makes sense to include as 'first class citizens' (geospatial or not) are processing services. I don't see the logic of cataloging a data service (view, download) separately from the data it serves. What is an endpoint? Suggestion: an endpoint is a web location (identified by a base URL) at which one can access a particular service. That service might offer various processing and data access options, but in the end there should be a service specification that is implemented at that endpoint that accounts for the 4 aspects [mentioned above](https://github.com/w3c/dxwg/issues/1242#issuecomment-647195521). An endpoint is a particular implementation of a service, possibly with bindings to particular data. I'd suggest that 'service' be thought of as a specification that might have various software implementations, and each of those implementations might be exposed by various endpoints, and those endpoints might have binding to different data. Service: protocol, information model, interchange format(s) used, operations offered Endpoint: URL, service specification, coupled data (optional) -- GitHub Notification of comment by smrgeoinfo Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1242#issuecomment-653909819 using your GitHub accountReceived on Sunday, 5 July 2020 16:35:01 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:35 UTC