#153: Requirements related to specific standard names
-----------------------------+------------------------------
Reporter: martin.juckes | Owner: cf-conventions@…
Type: enhancement | Status: new
Priority: medium | Milestone:
Component: cf-conventions | Version:
Resolution: | Keywords:
-----------------------------+------------------------------
Comment (by martin.juckes):
Dear Jonathan,
I'm happy with that proposal .. perhaps with one extra line in the
conventions document to say that "Use of some standard names introduces
additional constraints on the variable attributes and/or values, as
detailed in `link to: Requirements Related to Specific Standard Names` . "
I also agree on the need for a machine readable form. I was thinking that
something would be needed to assist the proof reading. E.g. a JSON file
which can be used to generate a spreadsheet displaying the definitions of
all the variables listed under each constraint.
I think the more legible wiki form is also necessary, in order to provide
the usage examples. In the earlier email discusion, Roy Lowry suggested
encoding the rules in RDF and serving them through the NERC Vocab Server
alongside the standard names. This would be neat, but I think it may be
worth generating wiki and JSON versions first, in order to get a clearer
view of the range of constraints that we are dealing with,
regards,
Martin
--
Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/153#comment:4>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
