[eml-dev] does url in eml-physical imply a get?

[Matt Jones]

Hi Sven,

>From my perspective, the HTTP spec is really what rules here.  Under HTTP,
the GET verb implies access to a url resource that will not modify that
resource (i.e., calling GET on the resource is always safe).  In contrast, a
POST to a url for a resource is used to access that resource in a way that
might modify it.  So it is not safe to call POST on a resource URL unless
you understand the application semantics of the POST call for that
particular application.  So, in the general case, you probably should only
use HTTP GET to retrieve the contents of a url referenced in an EML document
-- the POST could be dangerous (plus, presumably there is some access
control mechanism protecting against POST requests that are unwanted).

Matt

On Wed, Nov 11, 2009 at 5:17 PM, sven bohm <bohms at msu.edu> wrote:

> Hi,
>
> In the online element in eml-physical: does the url element imply that the
> data can be retrieved with an HTTP GET or should a client parsing the
> definition try both a GET and a POST?
>
> Thanks,
> --
> Sven Bohm -.- ..-. ---.. .-
> KBS-LTER Information Manager
>
>
>
>
>
>
>
>
> _______________________________________________
> Eml-dev mailing list
> Eml-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/eml-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/eml-dev/attachments/20091111/fc24d0d0/attachment.html>