Hi Folks, Scope out MMISW’s cf2rdf tooling - https://github.com/mmisw/cf2rdf I think this represents the first step of enabling use of semantics for CF standard names. Additionally, us SWEET (https://github.com/ESIPFed/sweet) developers would be very interested in aligning to such a resource. I recently presented ongoing ontology alignment activities at ESIP Winter meeting. You can scope them out at https://figshare.com/articles/McGibbneyL_sweet_20180110_pdf/5782122 Lewis
On 1/24/18, 8:54 AM, "CF-metadata on behalf of [email protected]" <[email protected] on behalf of [email protected]> wrote: Message: 1 Date: Wed, 24 Jan 2018 16:54:37 +0000 From: "Lowry, Roy K." <[email protected]> To: "Hollis, Dan" <[email protected]>, "[email protected]" <[email protected]> Cc: 'Heiko Klein' <[email protected]>, "Gregory, Jonathan" <[email protected]> Subject: [CF-metadata] CF Ontology Message-ID: <db6pr0601mb2117441ad90d2a7e4f50132099...@db6pr0601mb2117.eurprd06.prod.outlook.com> Content-Type: text/plain; charset="windows-1252" Thanks Dan, i've changed the subject to keep any further discussion clear of Heiko's proposal. My mapping work has focused on integration of CF data into aggregations of SeaDataNet data tagged with parameter labels from the BODC parameter dictionary. This is not a simple mapping for reasons other than taking cell methods into account. For example units of measure sometimes need to be considered because the BODC dictionary isn't as dimensionally pure as the Standard Names. It has also only been done on a 'needs must' basis and so only covers a small proportion of the dictionaries. Consequently, I haven't done much along the lines you suggest. I know others have done modelling work on CF, but I don't think that has gone as far as an ontology incorporating semantics (e.g. stating rules applicable to specific Standard Names). It would be a useful resource should anybody care to take the work on. If anyone has done anything in this area then please publicise on this list. In SeaDataNet our objective is to make NetCDF data CF-compliant. However, like you we also include our own semantics as additional (in our case namespace-labelled) parameter attributes. We also embed the semantics as a URI rather than plaintext. _______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
