It's a SOAP fault.  You wouldn't send a diagnostic for a malformed HTTP
Get request or broken TCP/IP package, you allow the underlying
transport mechanisms to take care of it, so we don't send a diagnostic
for a malformed SOAP package.

Secondly, if the soap package is malformed, most toolkits will reject it
before it ends up at the application layer, so many implementers would
not be able to return the diagnostic anyway.

Finally, the server couldn't tell which SRU response would to give to
encapsulate the diagnostic when it can't parse the request.

Rob

On Fri, 18 Aug 2006, marc wrote:

>Diagnostic missing for SRU SOAP malformed packages ??
>
>Upgrading a SRU GET/SOAP implementation from PHP4 to PHP5 for a
>customer, I detect sometimes SRU SOAP posted XML packages, which
>
>- either are not XML at all
>- or miss the correct SOAP envelopes
>
>Looking at the diagnostic list at
>
>http://www.loc.gov/standards/sru/diagnostics-list.html
>(by the way - why is there no link from the frontpage
>http://www.loc.gov/standards/sru/
>to this useful page  ?? You have to go over
>"Additional Information", "Info URi's",
>"Diagnostic Reference"  to get there ..
>)
>
>I can not find any error/diagnostic that fits. I suggest the addition of a
>
>number 9 "SOAP envelope XML coding error"
>
>in the general section (or a similar thing).
>
>And it strikes me that a similar diagnostic for wrong URL encoding of
>GET/POST parameters might be a good thing also ??
>
>Marc
>
>
>
>
>--
>
>Marc Cromme, cand. polyt, Ph.D
>Senior Developer, Project Manager
>
>Index Data Aps
>Købmagergade 43, 2
>1150 Copenhagen K.
>Denmark
>
>tel: +45 3341 0100
>fax: +45 3341 0101
>
>http://www.indexdata.com
>
>INDEX DATA Means Business
>for Open Source and Open Standards
>