#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 Ros,
Loading json files is trivial ... a one line command and then you get a
python object (e.g. a list or a dictionary). You then have to parse the
object .. the advantage of XML is that there is a well tested approach to
enforcing structure on the object, which, I find, tends to make parsing
more reliable. I can easily export it as json as well, as I suspect that
will make it more accessible to others.
Thinking about defining the structure, it will be easier to have rules of
the form:
`<rule targ="some_standard_name"><requiredAxis value="Z"></rule>`.
The `region`/`area_type` rule could be encoded more simply as
{{{
<rule targ="region"><charOrFlagIn value="CF Standard Region"\><\rule>
}}}
This would then give 4 rules to encode: requiredCoordinate, requiredAxis,
requiredBoundAxis, charOrFlagIn.
regards,
Martin
--
Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/153#comment:11>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
