Re: [galeon] spatial/temporal info in scientfic data types

• To: Ben Domenico <Ben@xxxxxxxxxxxxxxxx>
• Subject: Re: [galeon] spatial/temporal info in scientfic data types
• From: Peter Baumann <p.baumann@xxxxxxxxxxxxxxxxxxxx>
• Date: Fri, 30 Nov 2007 00:18:33 +0100

Hi all,

first of all, my thanks go to Ben for arranging this telecon. I realized
it is high time to intensify contacts, and I think we are on a good way.

Here my promised summary of the recent WCS.RWG developments:
- WCS corrigendum 1.1.1:
        contains fixes for 1.1.0
        status: done, but not yet published
- WCS corrigendum 1.1.2:
        contains further fixes for issues found meantime
        status: in progress
- WCS 1.2:

        new SWG to be established during the WCS.RWG meeting in Stresa Mon 
11:00+
        a few particular goals of this version:
                * make it simpler for implementers to understand and use

                * follow the core/extension model, achieve a modular spec set
  document set:
        * Grid Coverages Common:
                defines basic coverage model and service request structure
        * WCS "base" (as it's called for now, rather it resembles the "core")
                a combination of minimal aspects any WCS shall support
                (2-D x/y; single-band range; no covearge hierarchies; ...)
        * various extensions, currently:
                Complex range profile
                General Domain (allowing n-D coverages and arbitrary subsets 
thereof)
                WCS-T
                WCPS
                ...and several more; we are looking for writers!
  to somewhat guide extension spec writers a coverage aspect hierarchy is under
work (this was the document I mentioned in the telecon - see below). This
hierarchy lists all currently envisaged coverage model and service aspects, but
of course can be amended in future. This is tentatively small-grain to allow for
versatile combination in WCS implementations.
  further, a few predefined conformance classes bundle functionality which
appears useful for different application scenarios; this is aka suggestion for
developers while not constraining them.
  addtionally, among the ongoing work is harmonization with SWE/O&M

On our way to understand and materialize the core/extension model we ran into a
few issues, like for example: what means "extension" on XML level? Can/should we
fix a spec to certain modeling constructs to make sure an extension is a pure
extension? This topic should provide enough gun powder to lead to interesting
discussions in Stresa...

Now about the document promised, which attempts a classification of aspects
(as it is called in new core/extension terminology) and possible
extensions: I promised to attach it, but after WCS.RWG discussion we want to
brush it up a little before disclosing it ;-) ...early next week I will post it
here. As aka teaser: Very important for me is that we try to separate the
conceptual separation of the coverage model as such from the services provided
on them.

So much for now - just to reiterate, the WCS.RWG _is_ keen on your input
(preferrably in the shape of a Change Request) and participation!

'nite for now,
Peter

--
Dr. Peter Baumann
- Professor of Computer Science, Jacobs University Bremen*
               *formerly: International University Bremen
  www.faculty.iu-bremen.de/pbaumann, mail: p.baumann@xxxxxxxxxxxxxxxxxxxx
  tel: +49-421-200-3178, fax: +49-421-200-493178
- Executive Director, rasdaman GmbH Muenchen (HRB 147737)
  www.rasdaman.com, mail: baumann@xxxxxxxxxxxx
  tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
"A brilliant idea is a job halfdone."

• Follow-Ups:
  • Re: [galeon] spatial/temporal info in scientfic data types
    • From: Peter Baumann

• References:
  • [galeon] spatial/temporal info in scientfic data types
    • From: Ben Domenico