The DAP4 schema has does not chime with the narrative in the specification:
With respect to dap4 Attribute values the scheme has this:The schema allows:
<choice>
<element name="Value">
<attribute name="value">
<choice> <!-- technical ambiguity -->
<data type="dap4_integer"/>
<data type="dap4_float"/>
<data type="dap4_opaque"/>
<data type="dap4_char"/>
<data type="dap4_string"/>
<data type="dap4_fqn"/> <!-- for enum types -->
</choice>
</attribute>
</element>
<element name="Value"><data type="dap4_text"/></element>
</choice>
But the narrative in section 1.5.14 the option to have the value(s) of the dap4 Attribute be held as the XML Text node of a element is not discussed, it only appears in the schema. Example:
<Value>An attribute value of some type</Value>
This should be illustrated in section 1.5.14
The DAP4 schema has does not chime with the narrative in the specification:
With respect to dap4 Attribute values the scheme has this:The schema allows:
But the narrative in section 1.5.14 the option to have the value(s) of the dap4 Attribute be held as the XML Text node of a element is not discussed, it only appears in the schema. Example:
This should be illustrated in section 1.5.14