Aaron and George,
I think that the main reason to require only 2D in core was to maximize potential implementations. Note that core does not imply the core concept of a (grid) coverage. Core means any sever/client must implement the capability defined as "core capability". Requiring n-D actually does not cause a problem in server implementation because a server can always offer only 2D coverage. However, it is not the case to client implementation. If n-D is required, then a client must be able to talk to a n-D coverage server, even if it needn't n-D data, otherwise it will not be considered compliant.
Regards,
Wenli
----- Original Message -----
From: George Percivall <gpercivall@xxxxxxxxxxxxxxxxxx>
Date: Friday, October 3, 2008 5:17 pm
Subject: Re: [galeon] WCS CF-netCDF profile document
Aaron,
I completely agree that the WCS core should be N-dimensional.
The misconception is that core is a profile implemented on its
own,
there fore it should be the minimal, i.e., 2-D set.
Core is the core concepts that are the made specific through
extensions.
So core should be N-dimensional (as in AS Topic 6) and there
should be
an extension for that together defines a 2-D profile.
George
