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

[Raj Singh]

Thanks for raising the discussion above the coding level. You mention the tension between a graph-oriented model of information and a multi-dimensional array. Let me add another "dimension" to the theoretical discussion. I think the biggest problem I have with designing RESTful resources around coverage data is the fact that most coverages represent natural phenomena that vary continuously across the earth's surface (or atmosphere, or sub-surface). This means that the actual cell values are only approximations of what is expected to be observed in nature. This is why I have a hard time calling anything a resource other than the full coverage. 

In contrast to coverages, I think features and sensor observations (a specialized type of feature) should be much easier. The resource is the feature. But the million dollar question is, what are the appropriate links between features? I think Peter Rushforth is saying don't worry about it -- let each service implementer design their own link structure. To that I say, maybe so, but show me some good strategies and maybe we can design some common best practices from there...

---
Raj
The OGC: Making location count.
http://www.opengeospatial.org/ogc/organization/staff/rsingh


On Jul 11, at 11:54 AM, "Baumann, Peter" <p.baumann at jacobs-university.de> wrote:

> hm, then we are out of the world of imagery - links embedded in NetCDF files is not the use case we have.
> Actually, this view of the Web at large points to graph-oriented structures - one of the core data structures relevant in our times. However, another fundamental structure is that of a multi-dimensional array. This structure is not supported very much these days.
> 
> -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:26 PM
> To: Baumann, Peter
> Cc: Raj Singh; standards at lists.osgeo.org
> Subject: RE: [OSGeo-Standards] Was: "file" formats.  Is: GeoWeb
> 
>> 
>> now I'm puzzled - so you say REST = http,
> 
> No, I don't.
> 
>> and any http
>> request is RESTful?
> 
> No:  Hypertext is the key ingredient in REST.  It doesn't matter what the
> protocol is, in fact, if the links are embedded in hypertext.  And, what
> matters is that the links represent *relationships* between resources.  Not
> the format of the link itself.
> 
> Does that help?
> 
> Cheers,
> Peter