[OSGeo-Standards] Was: "file" formats. Is: GeoWeb

[Baumann, Peter]

Hi Peter,

now I'm puzzled - so you say REST = http, and any http request is RESTful?
If I am free to compose URLs, then KVP fits in perfectly (which is fine with me, but I believe I heard other voices).

-Peter
--
Dr. Peter Baumann- Professor of Computer Science, Jacobs University Bremen
  http://www.faculty.jacobs-university.de/pbaumann
  mail: p.baumann at jacobs-university.detel: +49-421-200-3178, fax: +49-421-200-493178
- Executive Director, rasdaman GmbH Bremen (HRB 26793)http://www.rasdaman.com,
  mail: baumann at rasdaman.com
  tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
"Si forte in alienas manus oberraverit hec peregrina epistola incertis ventis dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata, nec preripiat quisquam non sibi parata." (mail disclaimer, AD 1083)




________________________________________
From: Rushforth, Peter [Peter.Rushforth at NRCan-RNCan.gc.ca]
Sent: Thursday, July 11, 2013 5:11 PM
To: Baumann, Peter
Cc: Raj Singh; standards at lists.osgeo.org
Subject: RE: [OSGeo-Standards] Was: "file" formats.  Is: GeoWeb

Peter,

I guess the Architecture of thw World Wide Web [1] is as close to normative as
I can come for that.  It doesn't actually use the term "REST", but that term
was coined to describe that architecture, and is defined in chapter 5 [2],
specifically under section 5.1.5 [3].  It has nothing to do with how you
compose your URLs.  I hope this helps?

Regards,
Peter

[1] http://www.w3.org/TR/webarch/#hypertext
[2] http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm
[3] http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1_5

> -----Original Message-----
> From: Peter Baumann [mailto:p.baumann at jacobs-university.de]
> Sent: July 11, 2013 10:22
> To: Rushforth, Peter
> Cc: Raj Singh; standards at lists.osgeo.org
> Subject: Re: [OSGeo-Standards] Was: "file" formats. Is: GeoWeb
>
> Hi Peter,
>
> there are some normative statements that you cite, which can
> clarify indeed Would you have an authoritative link for that,
> so that we can base design decisions (also in
> standardization) on documented evidence?
>
> thanks,
> Peter
>
>
> On 07/10/2013 05:21 PM, Rushforth, Peter wrote:
> > Peter,
> >
> >> excellent point - no need to care about syntax, about making URLs
> >> RESTful, or WhateverFul.
> > There is no such thing as a RESTful URL.  There are just
> URLs, and it
> > is a service implementer's job to define those to be served.
> >
> > Specifying URL structure in documents is not REST, not at all.
> > It may be good server documentation, perhaps.
> >
> > I don't know what to call it, but it shouldn't be called
> REST.  Maybe RPC.
> > Calling it REST mis-informs the reader as to what REST is, and just
> > creates blocks in discussions of this nature.
> >
> >> The interesting question starts exactly where REST stops:
> how can I
> >> get what I need?
> >> Discussing service functionality is so much more exciting.
> > I don't see the disconnect between REST and data services,
> personally.
> >
> > Regards,
> > Peter
>
> --
> Dr. Peter Baumann
>   - Professor of Computer Science, Jacobs University Bremen
>     www.faculty.jacobs-university.de/pbaumann
>     mail: p.baumann at jacobs-university.de
>     tel: +49-421-200-3178, fax: +49-421-200-493178
>   - Executive Director, rasdaman GmbH Bremen (HRB 26793)
>     www.rasdaman.com, mail: baumann at rasdaman.com
>     tel: 0800-rasdaman, fax: 0800-rasdafax, mobile:
> +49-173-5837882 "Si forte in alienas manus oberraverit hec
> peregrina epistola incertis ventis dimissa, sed Deo
> commendata, precamur ut ei reddatur cui soli destinata, nec
> preripiat quisquam non sibi parata." (mail disclaimer, AD 1083)
>
>
>