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 ________________________________ This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.
_______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
