search

opengeospatial / CoverageJSON

Public repo for CoverageJSON project
Apache License 2.0
10 stars 8 forks source link

Several clarifications to the text requested - 5 #108

Closed chris-little closed 2 years ago

chris-little commented 2 years ago

@joanma747 identified several areas of confusion requiring improvements to the text. These have been split into 8 separate sub-issues:

  1. "The CoverageJSON media type SHALL be application/prs.coverage+json". Can you clarify what prs means?
chris-little commented 2 years ago

@joanma747 This is a valid media type. We could add an explanation: The prs media type is associated with non publicly available products or experimental media types. We could add changing it to a more public media type as future work, but this may be a breaking change.

letmaik commented 2 years ago

I don't think such comment belongs to a spec.

I think ultimately we want application/coverage+json but that requires a formal spec recognized by a standards body. I'm not sure if an OGC community standard counts as such, but if it does, then I think to avoid breaking existing clients/servers twice we should keep "prs" and change it to application/coverage+json once OGC recognizes it as community standard. It may also make sense to go through this process in the second version of CovJSON since that may introduce more changes and is a cleaner cut towards a recognized standard.

jonblower commented 2 years ago

There must be some precedents here - what do other OGC standards do when they want to associate with a new MIME type?

chris-little commented 2 years ago

@jonblower OGC policy is to use a "local" MIME type until OGC has formally registered with IANA (Scott can fastish-track it), then issue a corrigendum V1.0.1, or later, of the standard.

chris-little commented 2 years ago

@joanma747 Agreed not to add explanatory comment, especially as the media type may change from prs in the future. CoverageJSON Task Team meeting 2022-07-13