• To: 'Joe Gregorio' <joe.gregorio@g...>, sean.mcgrath@p...
• Subject: RE: REST, SOAP, Speech Acts and the mustUnderstand model of SOA communications (was: Re: What Does SOAP/WS Do that A REST System Can't?)
• From: "Bullard, Claude L (Len)" <len.bullard@i...>
• Date: Fri, 1 Apr 2005 08:39:21 -0600
• Cc: xml-dev@l...

Thus lawyers and HR emerged from the pristine pastures of 
content to ensure they would devolve into swamps 
of innuendo and outright fabrication.

The web has no meaning.  Only purpose.

len


From: Joe Gregorio [mailto:joe.gregorio@g...]

Excellent, an enumeration is the right way to go with this. The advantage
is that you can then dip into negative numbers:

xml:mustUnderstand="-1" - The recipient MUST NOT understand 
the message fragment. 

xml:mustUnderstand="-2" - The recipient MUST willfully misinterpret
the message fragment. 

xml:mustUnderstand="-3" - The recipient MUST willfully misinterpret
part of the message while generating error messages that include
ad hominem attacks on the author of the message fragment.

xml:mustUnderstand="-5" - The recipient MUST willfully misinterpret
part of the message in a libelous manner while claiming to have 
invented the format and claiming you are using it wrong.

• Prev by Date: Re: REST, SOAP, Speech Acts and the mustUnderstand model of SOA communications (was: Re: What Does SOAP/WS Do that A REST System Can't?)
• Next by Date: Re: REST, SOAP, Speech Acts and the mustUnderstand model of SOA communications (was: Re: What Does SOAP/WS Do that A REST System Can't?)
• Previous by thread: Re: Problem parsing XML file with Xerces-J
• Next by thread: RE: REST, SOAP, Speech Acts and the mustUnderstand model of SOA communications (was: Re: What Does SOAP/WS Do that A REST System Can't?)
• Index(es):
  • Date
  • Thread