#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,
OK, I think the rules could be expressed in a simple XML format, one
element per rule. e.g.
`<rule target="area_fraction" requiredCoordinate="area_type"/>` to
specify that "area_fraction" must have and area_type variable as a
coordinate. Where a variable has more than one required coordinate, I
would list this in two separate XML elements.
Other rules would be of the form `<rule target="...."
requiredAxis="Z"/>`, to specify that a variable must have a dimension or
coordinate with "axis=Z" `<rule target="...." requiredBoundAxis="Z"/>` to
specify additional that the dimension or coordinate in question must have
bounds set.
The `region` and `area_type` rules have a choice, which we could encode as
follows:
{{{
<choice target="region">
<option type="char"\>
<option attribute="flag_values"\>
<\choice>
<rule target="region" dataValuesIn="CF Standard Region"\>
}}}
The data values referred to in the last case should be interpreted as th
flag values if present. On the other hand, it may be easier to just have a
named test for these two, rather than using a complex schema like this.
Cheers,
Martin
--
Ticket URL: <http://cf-trac.llnl.gov/trac/ticket/153#comment:9>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
