[ESIP-all] New ESIP Cluster proposal - request for comment

[Ethan Davis]

Hi all,

Thanks for your comments.

The scope of the cluster was intended to be fairly broad, allowing for
discussions and activities cutting across various file formats, APIs,
metadata standards, and data models. So, I think UDUNITS, CF standard
names, time, and the like could certainly be within scope. ASCII vs Unicode
seems like more of an edge case. But we can figure out those types of
details as the cluster moves forward.

I will announce here when the cluster is up and we have an email list where
we can continue these discussions in more detail.

Cheers,

Ethan

On Thu, Mar 22, 2018 at 9:47 AM, Robert Casey <rob at iris.washington.edu>
wrote:

>
> Sounds like a good cluster concept.  One thing that may creep into data
> model structures are data representation *standards*, such as ISO
> representation of time, SI units of measurement, representing tilt vs earth
> normal, ASCII vs Unicode, and so forth.  Is the notion of standard
> representation within scope or out of scope when discussing these data
> models?
>
> -Rob
>
>
> On Mar 21, 2018, at 4:02 PM, Moroni, David F (398G) via ESIP-all <
> esip-all at lists.esipfed.org> wrote:
>
> Hi James,
>
> I agree that this is an extremely good idea, and I think it would be good
> to also think about streamlining certain metadata procurement processes
> within these existing data models, such as within the UDUNITS database
> (leveraged by CF) and the CF standard name table. The approval process for
> new metadata attributes in these areas is a bit of a black box, not very
> transparent, and also presents a significant bottleneck for PI’s of newer
> remote sensing projects that are providing newer flavors of measurements
> that are not currently captured by both UDUNITS and the CF standard name
> list.
>
> I had thought about organizing a breakout session at the 2018 summer ESIP
> meeting to address some of these issues, but perhaps your cluster is a
> better fit for this.
>
> Cheers,
> David
>
> *From: *ESIP-all <esip-all-bounces at lists.esipfed.org> on behalf of James
> Gallagher via ESIP-all <esip-all at lists.esipfed.org>
> *Reply-To: *James Gallagher <jgallagher at opendap.org>
> *Date: *Wednesday, March 21, 2018 at 3:53 PM
> *To: *Ethan Davis <edavis at ucar.edu>
> *Cc: *ESIP-all <esip-all at lists.esipfed.org>
> *Subject: *Re: [ESIP-all] New ESIP Cluster proposal - request for comment
>
>
>
>
> On Mar 21, 2018, at 16:18, Ethan Davis via ESIP-all <
> esip-all at lists.esipfed.org> wrote:
>
> Hi all,
>
> Here is a description / mission statement for a new ESIP cluster:
>
>
> The mission of the Data Model Cluster is to support efforts to advance
> existing and developing data models for earth system science data.
>
>
> Discussion and project topics will likely involve
>
> ·         Existing abstract data models (e.g., CF and OGC)
> ·         Web APIs, traditional APIs, and related data models (e.g.,
> OPeNDAP and OGC WCS)
> ·         File formats, other encodings, and related data models (e.g.,
> netCDF, HDF, GRIB)
>
> Current efforts include:
>
> ·         Supporting efforts to advance netCDF-CF
> ·         Investigating OGC MetOcean Profile for OGC WCS 2.1
>
> Thoughts, comments, and suggestions are welcome.
>
>
> I think this is a good idea. I’d like to be part of it. I’m particularly
> interested in expmanding support for what Chris Little calls Natural Axes
> subsetting (subsetting by lat, lon and time) and Trajectory subsetting in
> DAP.
>
> James
>
> PS. GRIB? ;-)
>
>
>
> Thanks,
>
> Ethan
> _______________________________________________
> ESIP-all mailing list
> ESIP-all at lists.esipfed.org
> http://www.lists.esipfed.org/mailman/listinfo/esip-all
>
>
> --
> James Gallagher
> jgallagher at opendap.org
>
>
>
>
>
> _______________________________________________
> ESIP-all mailing list
> ESIP-all at lists.esipfed.org
> http://www.lists.esipfed.org/mailman/listinfo/esip-all
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.esipfed.org/pipermail/esip-all/attachments/20180329/00e67dee/attachment.html>