I do not think that is a correct assumption. I am not familiar with the "MUST" issue you are focusing on. What version of what document are you referencing here?

I think Marty is referring to the HPC Profile document. It has (if I remember correctly) a statement that 'exact' must be implemented by all HPC Profile compliant JSDL implementations while the other range elements are recommended. I was unsure why the table had "JSDL-WG" against this issue since I think it is an issue for the HPC Profile and not for the JSDL spe. Andreas Karl Czajkowski wrote:

On Nov 21, Marty Humphrey modulated:

...

RangeValue_Type element clarifications

-- If a single min value and a single max value are to be specified, should it be done with Boundary_Type’s or a single Range_Type?

They are semantically equivalent. The boundary parts are for defining semi-spaces, which cannot be expressed with the range pair.

...

-- I assume Exact takes precedence over any specified Boundary_Type or Range_Type’s since Exact is a MUST and the others are optional.

I do not think that is a correct assumption. I am not familiar with the "MUST" issue you are focusing on. What version of what document are you referencing here?

The entire range-value element is meant to be expressing a disjunction of simple semi-space, exact, or interval constraints. So, if I expressed:

OR [the combining logic of all range value elements] x > 0 [as a boundary sub-element] x = 4 [as an exact match sub-element] 5 < x < 7 [as a range sub-element]

it would be semantically equivalent to just the first constraint x > 0.

karl