[OGSA-BES-WG] BES Last Call

[Andreas Savva]

Chris,

Chris Smith wrote:
> UnsupportedFeatureFault indicates that a particular element or attribute
> contained within the JSDL document is either not supported, or (for
> extension content) not supported or recognized.
> 
> InvalidRequestMessageFault indicates that the value of some element is
> invalid input. For example, if TotalCPUCount in JSDL was given as -10.

This is nice text and I hope it is included in the BES spec. "...not
recognized" is not correct.

Also given the above, HPC Profile sections 3.9 and 3.10 specify the
wrong value for the returned fault. For example in 3.9 it says

> If the consuming system does not provide the requested operating system,
> or if the JSDL special token “other” is used as the content of the
> jsdl:OperatingSystemName sub-element, and if the consuming system does
> not understand the provided extension content, then the consuming system
> MAY return the BES InvalidRequestMessageFault to the requester.

It should be UnsupportedFeatureFault. (And why is the fault returned a
MAY and not a MUST for the profile?)

Andreas


> 
> -- Chris
> 
> 
> On 05/2/07 23:58, "Andreas Savva" <andreas.savva at jp.fujitsu.com> wrote:
> 
>> Mark,
>>
>> Sorry if this is an FAQ, but glancing through the document I'm not clear
>> on the distinction between the definitions of "UnsupportedFeatureFault"
>> and "InvalidRequestMessageFault".
>>
>> For example, "UnsupportedFeatureFault" says  "... well-formed, supported
>> JSDL document input element containing a sub-element that is not
>> implemented by this BES implementation."
>>
>> and "InvalidRequestMessageFault" says
>> "An element in the request message is not recognized. ... This does not
>> mean that the element itself is in error, but rather that it specifies a
>> syntactically correct value which does not in fact make sense."
>>
>> Suppose that the jsdl 'other' value is used to provide extra XML content
>> in order to specify an operating system not in the OperatingSystem
>> enumeration. If a BES container does not 'support' this operating system
>> which of the two faults should be returned?
>>
>> Btw, the CPU example is clear but it would not have been an example I
>> would have thought of given the normative definition ("..not
>> recognized") of the InvalidRequestMessageFault.
>>

-- 
Andreas Savva
Fujitsu Laboratories Ltd