[OGSA-BES-WG] BES Last Call

[Chris Smith]

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.

-- 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
> 
> Mark Morgan wrote:
>> Ladies and Gentlemen,
>> 
>> As per consensus at the BES session yesterday, 1 February 2007, at 6pm at
>> OGF19, I have made all noted modifications to the BES document.  It is
>> uploaded to the Gridforge website and is available as ogsa-bes-draft-v30.
>> 
>> If you feel that you deserve acknowledgements for work done, or to be listed
>> as an author, and you are not currently indicated properly in the document,
>> please speakup.
>> 
>> Once again, this is the last call for OGSA BES specification before we send
>> it off for public comment.
>> 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/ogsa-bes-wg/attachments/20070206/81d169ba/attachment.htm