Single Constraint per Definition: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
 
No edit summary
Line 1: Line 1:
Current, a constraint expression is provided per container specified in a definition. For example:
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<request reqID="some_unique_value" >
    <define name="d">
<container name="mfp920504a" />
    </define>
    <get type="tab" definition="d" />
</request>
</pre>


[[Category:Development|Single Constraint per Definition]][[Category:Hyrax Development|Single Constraint per Definition]]
[[Category:Development|Single Constraint per Definition]][[Category:Hyrax Development|Single Constraint per Definition]]

Revision as of 15:58, 10 March 2010

Current, a constraint expression is provided per container specified in a definition. For example:

<?xml version="1.0" encoding="UTF-8"?>
<request reqID="some_unique_value" >
    <define name="d">
	<container name="mfp920504a" />
    </define>
    <get type="tab" definition="d" />
</request>