Re: SOAP Faults in XKMS

Thanx Rich,

Can we also use the same convention for names of XKMS elements that are defined to be QNAME in XKMS specification ..? I am using example of <KeyUsage> element to explain my question:

CASE-1
======

<KeyUsage>Signature</KeyUsage>
<KeyUsage>Encryption</KeyUsage>
<KeyUsage>Exchange</KeyUsage>

CASE-2
======

<KeyUsage>xkms:Signature</KeyUsage>
<KeyUsage>xkms:Encryption</KeyUsage>
<KeyUsage>xkms:Exchange</KeyUsage>

Now what is the recommended way to follow in XKMS Messages

1- CASE-1 is correct
2- CASE-2 is correct
3- Both CASE-1 and CASE-2 are correct

Any details on this issue will be very helpful for me.

Thanx & Regards,

Yasir Khan

----- Original Message ----- 
  From: Rich Salz 
  To: Yasir Khan 
  Cc: www-xkms@w3.org 
  Sent: Wednesday, October 08, 2003 7:49 PM
  Subject: Re: SOAP Faults in XKMS



  > <env:Envelope xmlns:env="http://www.w3.org/2002/06/soap-envelope">
  >  <env:Body>
  >   <env:Fault>
  >     <env:Code>
  >       <env:Value>env:Sender</env:Value>
  >       <env:Subcode>
  >         <env:Value>xkms:MessageNotSupported</env:Value>

  Those value elements are defined -- by SOAP -- to be QNAME's,
  i.e., names with a namespace prefix.  You are correct that
  the examples are wrong, because an "xmlns:xkms" declaration
  is not in-scope.

  (The pro's and con's of using QNAME's we can discuss elsewhere.:)
          /r$

  --
  Rich Salz                  Chief Security Architect
  DataPower Technology       http://www.datapower.com
  XS40 XML Security Gateway  http://www.datapower.com/products/xs40.html
  XML Security Overview      http://www.datapower.com/xmldev/xmlsecurity.html