[Esip-documentation] Strategic plan and ACDD

Sat Jan 18 11:09:53 EST 2014

Haven't looked recently, but there were some built-in flattening
capabilities in the NetCDF libraries export to NCML methods. It would be
good to revisit with some more recent NetCDF/HDF files with proposed group
examples.  An initial problem identified in the NetCDF library with
flattening was related to non-unique element names being produced and
colliding, a bug was filed and perhaps updates have been made Unidata.

If the XSL has an OR statement that allows both the 1.2 ACDD mappings along
with flattened 2.0 names seems like it could be a relatively painless
transition (at least in theory!).

Dave

On Sat, Jan 18, 2014 at 8:06 AM, Ted Habermann <thabermann at hdfgroup.org>wrote:

> Ken,
>
> When we agreed to go forward with a grouped version (2.0) we also agreed
> to have a standard approach to flattening the groups. That takes care of
> the grouping thing, but it does not take care of harmonizing the names of
> the flattened elements. Could be that the flattening needs to be more like
> an xsl that flattens and renames... It would be a bit like the ISO > FGDC
> transforms, admit at the start that you are not going to get everything but
> do you best...
>
> Another approach may involve writing flat NcML into a catalog and using
> that to access the data... A bit like the CF augmentation approach that is
> well known today.
>
> I know that we all agree that we want to do our best to maximize
> compatibility between the two approaches while moving forward at the same
> time. This group includes significant players that I'm sure will keep us
> honest!
>
> Ted
>
> On Jan 17, 2014, at 4:02 PM, Kenneth Casey <Kenneth.Casey at noaa.gov> wrote:
>
> Thanks.  I understand about the new standard applying to the enhanced
>  features.  I did not understand that one standard could not include both
> classic and enhanced.  That sounds to me like trouble in terms of getting
> people to adopt the standards. Do I now need to publish two versions of
> every NODC netCDF template? What if someone saves their data in a netCDF -4
> enhanced file but doesn't actually use any enhanced features?
>
> Ken
>
> --
> Kenneth S. Casey, Ph.D.
> Technical Director
> NOAA National Oceanographic Data Center
> 1315 East-West Highway
> Silver Spring MD 20910
> 301-713-3272 x133
> http://www.nodc.noaa.gov
>
> On Jan 17, 2014, at 4:14 PM, "Armstrong, Edward M (398M)" <
> Edward.M.Armstrong at jpl.nasa.gov> wrote:
>
> Ken,
>
>  The "new" version will be extended to handle things like HDF5 groups.  I
> guess it could be written so the is usable in the netCDF3 environment, but
> there are some very specific things that will be built into ACDD 2.x .
> Perhaps at some in the future they will converge....
>
>  On Jan 17, 2014, at 11:29 AM, Kenneth S. Casey - NOAA Federal wrote:
>
>  Why do you need to finalize a classic version?  Can't the new extended
> netCDF version be written in such a way that it works with classic files
> too?  Maybe a few "if classic do this, if extended do that" constructs
> would be needed… but that has a better feel to me than having two different
> standards in development.  I can not volunteer, sorry.
>
>  Ken
>  On Jan 17, 2014, at 2:20 PM, Ted Habermann <thabermann at hdfgroup.org>
> wrote:
>
>  Thanks to all of you that participated in the strategic plan discussion
> yesterday. The plan is available at
> https://docs.google.com/document/d/10lKi88rReL0rF4WhZ8yEMabBoQTuALX-vu2VXBVokCo/edit#heading=h.1lkb0jjpy3xb.
> I think it is open for editing...
>
>  One question that came up in the discussion was the future of ACDD... We
> have agreed that this future involves two paths: a final netCDF Classic
> compliant version (1.2) and a new netCDF extended / HDF / ISO compliant
> version (2.0). Ed and I both expressed some interest in pursuing 2.0, but
> we still need someone to shepard 1.2 forward... Any volunteers?
>
>  Ted
>
> <SignatureSm.png>
>
>   _______________________________________________
> Esip-documentation mailing list
> Esip-documentation at lists.esipfed.org
> http://www.lists.esipfed.org/mailman/listinfo/esip-documentation
>
>
>   [NOTE: The opinions expressed in this email are those of the author
> alone and do not necessarily reflect official NOAA, Department of Commerce,
> or US government policy.]
>
>  Kenneth S. Casey, Ph.D.
> Technical Director
> NOAA National Oceanographic Data Center
> 1315 East-West Highway
> Silver Spring MD 20910
> 301-713-3272 x133
> http://www.nodc.noaa.gov
>
>  <https://www.facebook.com/noaa.nodc>
>
> <facebook.png><RSS.png>
>  <http://www.facebook.com/feeds/page.php?id=178512945559611&format=rss20>
>  <http://www.facebook.com/feeds/page.php?id=178512945559611&format=rss20>
>  _______________________________________________
> Esip-documentation mailing list
> Esip-documentation at lists.esipfed.org
> http://www.lists.esipfed.org/mailman/listinfo/esip-documentation
>
>
>  -ed
>
>  Ed Armstrong
> JPL Physical Oceanography DAAC
> 818 519-7607
>
>
>
>
> _______________________________________________
> Esip-documentation mailing list
> Esip-documentation at lists.esipfed.org
> http://www.lists.esipfed.org/mailman/listinfo/esip-documentation
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.esipfed.org/pipermail/esip-documentation/attachments/20140118/821597f7/attachment.html>