Re: [sdw] Create a list of OGC standards that are "not yet Web-friendly enough" plus rationale for each

I agree with Clemens. Perhaps this group should be split into two categories:
1. those standards which are not webby enough (i.e., need modernization to fully support current web architectures) and
2. those standards which could have web-friendly implementations (i.e., encodings more friendly to developers, such as JSON, or profiles that simplify the content for non-expert use cases).

Many of the OGC W*S standards fit in the first category, many of the traditional encoding standards in the second (e.g., CityGML >> CityJSON, Moving Features CSV >> Moving Features JSON Best Practices).

It sounds counter-intuitive that "Web Something Service" is less "webby" than a standard without "web" in the name, but I cannot think of a better way to describe the problem than with "webby."

GitHub Notification of comment by ogcscotts
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 8 August 2018 12:20:54 UTC