Mark, While there is a close relationship between NERC and CF, they are not the only two mechanisms publishing CF terms. The MMI vocabulary server, http://mmisw.org/orr, also publishes CF standard name vocabulary and term URIs.
The URI for the entire vocabulary is http://mmisw.org/ont/cf/parameter, or if you want specifically the version 23 vocabulary, http://mmisw.org/ont/cf/20130603T200127/parameter. It does not have the CF namespace directly; however, we have mechanisms by which we could alias terms to/from a CF namespace. (Your sub-domain suggestion is a good one for CF.) Each standard name also exists in MMI as an individual resource, for example http://mmisw.org/ont/cf/parameter/air_temperature (or in versioned form, http://mmisw.org/ont/cf/20130603T200127/parameter/air_temperature). Many of your querying and resolution proposals are already satisfied with this service. The vocabularies can be published in multiple forms; SPAQRL queries are supported (e.g., http://mmisw.org/ont/?form=json&sparql=SELECT ?s ?p ?o WHERE {?s ?p ?o. } LIMIT 20), where the output form is specified as json, csv, or html (see examples page at http://mmisw.org/ont/sparql.html); and while I haven't constructed a query by vocabulary lately, given a few moments this weekend I will steal/demonstrate examples in that category. Please consider the MMI server for your existing needs, and perhaps they are a good fit for long-term CF goals as well. John On Jun 13, 2013, at 09:14, "Hedley, Mark" <[email protected]> wrote: > Thank you for the reminder Roy, I should have posted this a while back > > I have written a paper on publishing standard names which I think might > provide some of the required functionality for the community. > > It would be very useful for me and work I am involved in. > > The paper is attached. I invite feedback on this proposal > > many thanks > mark > > > > From: CF-metadata [[email protected]] on behalf of Lowry, Roy > K. [[email protected]] > Sent: 13 June 2013 14:50 > To: Ajay Krishnan - NOAA Affiliate; [email protected] > Subject: Re: [CF-metadata] standard_name_vocabulary attribute > > Hello Ajay, > > If I've got it right, your example is a URL for a single standard name. The > version numbers refer to versions of the whole list and so including the > version number in a reference to a single standard name causes the standard > name to inherit the version number of the list of which it is a member. > Trouble is that most standard names are members of more than one list version > but the standard name is exactly the same in each of these versions. > Consequently, a given standard name ends up with multiple URIs. In version 1 > of the vocabulary server we run (NERC Vocabulary Server or NVS) we made the > mistake of list members inheriting the version numbers of their parent lists > and learned the hard way the problems it causes for operational systems. > Versioning in the current version of NVS (V2)has been done differently with > list member and list versioning totally decoupled and the versioning > information explicitly excluded from list member URIs. > > I am aware of work underway by Mark Hedley at the UK Met Office to provide > URLs for Standard Names in a CF namespace that follow linked data principles > by resolving into usable XML (SKOS RDF) documents. I'm not sure how far this > work has progressed, so I'll leave it Mark to say more on the list if he > feels he's ready. > > Cheers, Roy. > > > > From: CF-metadata [[email protected]] on behalf of Ajay > Krishnan - NOAA Affiliate [[email protected]] > Sent: 13 June 2013 13:44 > To: [email protected] > Subject: [CF-metadata] standard_name_vocabulary attribute > > > Hi, > > There seems to be some ambiguity about the usage of the > standard_name_vocabulary attribute. Based on the link below, the right value > would be to use something like CF 1.6 > http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html#standard_name_vocabulary_Attribute > > Is that the right usage or should we reference the version of the > cf-standard-name-table like v1..v23 etc.? > > Any info on this would be much appreciated. > > Thanks, > Ajay > <publishingStandardNames.pdf>_______________________________________________ > CF-metadata mailing list > [email protected] > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata --------------- John Graybeal Marine Metadata Interoperability Project: http://marinemetadata.org [email protected]
_______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
