search

ogcscotts / TC-Meeting-topics

place to discuss topics raised by Working Groups
10 stars 0 forks source link

WCS REST Extension #11

Open ogcscotts opened 6 years ago

joanma747 commented 6 years ago

Can I be provocative?. I thing that there are services that fits well with REST like WFS and WMTS and others that does not such as WCS and WMS. Can we simple forget about REST in the services that does not adapt well with the "resource" pattern?. To do a "half-REST" we already have KVP, that is restful enough to me. In the case of WCS let's focus provide more functionality instead of doing the same with other notations. --End of provocation--

pebau commented 6 years ago

on principle fully agreed, Joan. However, (i) the spec is already available (and very parallel to KVP in its mechanics - looking into the doc posted you might agree) and (ii) some people asked to have it (otherwise I would have left it in zombie land). So why not give it a try, maybe this time it's a low-hanging fruit ;-)

pebau commented 6 years ago

Following intense discussion with several stakeholders, it is clear that REST is simply not powerful to express multi-dimensional addressing in an adequate way. Maybe we indeed should not force each and every service into the Procrustes bed of REST, but apply it only where it is meaningful.