Hi Folks, I’m fine with going with option 2 to clearly separate different vocabularies from NUG, CF and ACDD. But there is still the problem of how to best document overlap…. I believe there was a little misinformation earlier in the thread. For example, attributes “title”, and “Conventions” are clearly and uniquely defined and assigned in ACDD and CF even if they have the same language. For example see here:
http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Discovery_1-3 (look for Highly Recommended Global Attributes) From: Ethan Davis <[email protected]> Date: Monday, November 12, 2018 at 1:09 PM To: Jonathan Yu <[email protected]> Cc: Nan Galbraith <[email protected]>, "Armstrong, Edward M (398G)" <[email protected]>, David Neufeld <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, "Hedley, Mark" <[email protected]>, Adam Leadbetter <[email protected]>, Jim Biard <[email protected]>, Aleksandar Jelenak <[email protected]> Subject: Re: [Esip-documentation] Fwd: [esip-semantictech] ACDD vocab as RDF Hi Jonathan, all, Yes, Unidata could host something to capture the list of attributes included in NUG. We've started looking at making the NUG a bit more standalone (less intertwined with the C library docs). This might fit right in with that effort. Cheers, Ethan On Wed, Nov 7, 2018 at 4:56 PM <[email protected]> wrote: Hi Dave, Edward, and Nan, Thanks for that. Also, capturing semantics about global vs. variable level properties would be good too. On representing properties... It would be ideal if we had CF, NUG and ACDD properties represented too. We're in a bootstrapping phase at the moment - these do not yet exist for the 3 conventions. The issue also is around publishing resources that are governed by the respective communities. I wonder if I could ask which of the following options is preferable for capturing attributes used across CF, ACDD and the NetCDF user's guide - (where <=> is something like a sameAs or exactMatch relationship) ? -Option 1: Include equivalence statements across communities- acdd:title <=> cf:title <=> nug:title acdd:Conventions <=> cf:Conventions <=> nug:Conventions or -Option 2: Publish - nug:title nug:Conventions @Ethan - would Unidata consider hosting a Github repo with a CSV or RDF files for capturing the list of attributes included in the NUG? The ESIP COR might be an option for hosting Linked Data descriptions for them like http://cor.esipfed.org/ont/~jyu/test-acdd Regards, Jonathan -----Original Message----- From: Nan Galbraith [mailto:[email protected]<mailto:[email protected]>] Sent: Tuesday, 6 November 2018 7:00 AM To: Armstrong, Edward M (398G) <[email protected]<mailto:[email protected]>>; David Neufeld <[email protected]<mailto:[email protected]>>; Cluster Documentation <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Cc: Yu, Jonathan (L&W, Clayton) <[email protected]> Subject: Re: [Esip-documentation] Fwd: [esip-semantictech] ACDD vocab as RDF I'd like to clarify that we have printed some attributes in our documentation (e.g. title, source, Conventions) that are not just identical to CF or NUG, but actually belong to those conventions, not to ACDD. The text may not be quite as explicit as it was at one point, but we defer to CF or NUG for these definitions, and don't claim ownership of them. They're included in our documentation because they're such a necessary part of discovery. At least that's my take on this. Cheers - Nan On 11/5/18 12:22 PM, Armstrong, Edward M (398G) via Esip-documentation wrote: > > Hello: > > What about combining this or integrating this with CF in some manner ? > Some of the attributes like “title” and “source” are exactly the same. > > Be careful of mixing global vs variables attributes. For example > ‘*coverage_content_type*’ was on the list (but not units or long_name > etc.) > > I recommend you look at variable attributes but they have to be > treated separately. > > *From: *Esip-documentation > <[email protected]<mailto:[email protected]>> > on behalf of David > Neufeld via Esip-documentation > <[email protected]<mailto:[email protected]>> > *Reply-To: *David Neufeld > <[email protected]<mailto:[email protected]>> > *Date: *Monday, November 5, 2018 at 8:36 AM > *To: *Cluster Documentation > <[email protected]<mailto:[email protected]>>, > "[email protected]<mailto:[email protected]>" > <[email protected]<mailto:[email protected]>> > *Cc: *Jonathan Yu <[email protected]> > *Subject: *[Esip-documentation] Fwd: [esip-semantictech] ACDD vocab as > RDF > > Hi All, > > Just sharing this across some other communities as interest in a > machine readable format has been expressed previously for ACDD. > > Note there's a JSON-LD representation as well at the test repo link. > > Thanks Jonathan! > > Dave > > ---------- Forwarded message --------- > From: *Jonathan Yu via esip-semanticweb* > <[email protected]<mailto:[email protected]> > <mailto:[email protected]<mailto:[email protected]>>> > Date: Sun, Nov 4, 2018 at 7:38 PM > Subject: [esip-semantictech] ACDD vocab as RDF > To: > <[email protected]<mailto:[email protected]> > <mailto:[email protected]<mailto:[email protected]>>> > Cc: <[email protected]<mailto:[email protected]> > <mailto:[email protected]<mailto:[email protected]>>>, > <[email protected]<mailto:[email protected]> > <mailto:[email protected]<mailto:[email protected]>>>, > <[email protected]<mailto:[email protected]> > <mailto:[email protected]<mailto:[email protected]>>> > > Hi all, > > I’ve been observing the list for a while, but today have something to > share that might be of interest to this mailing list. > > I’m part of a working group developing a netCDF Linked Data > (netCDF-LD) standard with tools over at > https://binary-array-ld.github.io/netcdf-ld/ > > As part of this work, we’ve identified an opportunity for the ACDD > vocabulary to be ‘triplified’ with stable identifiers hosted by ESIP. > This would greatly help our efforts in providing a translation pathway > from netCDF files (using ACDD and CF) into RDF and RDF > profiles/flavours (like schema.org<http://schema.org> <http://schema.org>). > This might > hook into some of the discussion about schema.org<http://schema.org> > <http://schema.org> > and future work by ESIP Sem Web… > > To this end, I’d like to share some initial work to turn the ACDD > convention documented at > (http://wiki.esipfed.org/index.php/Attribute_Convention_for_Data_Disco > very_1-3) > into CSV. > > This is being developed over at https://github.com/ESIPFed/acdd (see > PR https://github.com/ESIPFed/acdd/pull/2). > > The aim is to eventually publish through the COR. I have a test repo > at http://cor.esipfed.org/ont/~jyu/test-acdd > <http://cor.esipfed.org/ont/%7Ejyu/test-acdd> . > > We’d appreciate any feedback or contributions to this work. An > ambitious target would be to have this stabilised by Christmas :) > > Regards, > > Jonathan > > p.s. if you’re interested, see > https://github.com/binary-array-ld/bald/wiki/Schema.org-mappings for > an initial schema.org<http://schema.org> <http://schema.org> mapping. > > *Jonathan Yu* > > Senior Experimental Scientist | Data Scientist > > Environmental Informatics <https://research.csiro.au/ei> | Water > Resources Management | Land and Water > > CSIRO > > *E*[email protected] > <mailto:[email protected]<mailto:[email protected]>> *T* +61 3 9545 > 2457 *M* +61 4 7773 0733 > > Bayview Ave, Clayton VIC 3168, AUSTRALIA *|* Postal Address: Private > Bag 10, Clayton South VIC 3169, AUSTRALIA > > www.csiro.au<http://www.csiro.au> <http://www.csiro.au/> > > ResearcherID: F-2336-2011 > <http://www.researcherid.com/rid/F-2336-2011> | ORCID: > 0000-0002-2237-0091 <http://orcid.org/0000-0002-2237-0091> | Google > scholar: _ikiM_EAAAAJ > <https://scholar.google.com.au/citations?user=_ikiM_EAAAAJ> > > ** > > *PLEASE NOTE* > > The information contained in this email may be confidential or > privileged. Any unauthorised use or disclosure is prohibited. If you > have received this email in error, please delete it immediately and > notify the sender by return email. Thank you. To the extent permitted > by law, CSIRO does not represent, warrant and/or guarantee that the > integrity of this communication has been maintained or that the > communication is free of errors, virus, interception or interference. > > /Please consider the environment before printing this email./ > > _______________________________________________ > esip-semanticweb mailing list > [email protected]<mailto:[email protected]> > <mailto:[email protected]<mailto:[email protected]>> > https://lists.esipfed.org/mailman/listinfo/esip-semanticweb > > > -- > > David Neufeld > -- ******************************************************* * Nan Galbraith Information Systems Specialist * * Upper Ocean Processes Group Mail Stop 29 * * Woods Hole Oceanographic Institution * * Woods Hole, MA 02543 (508) 289-2444 * *******************************************************
