RE: [wss] Error in WSS interop example #2

["Hal Lockhart" <hlockhar@bea.com>]

Ok, I'm confused. Can anybody else comment? Is Merlin correct?

Hal

> -----Original Message-----
> From: merlin@baltimore.ie [mailto:merlin@baltimore.ie]
> Sent: Tuesday, June 03, 2003 2:46 PM
> To: Hal Lockhart
> Cc: Eric Gravengaard; [wss oasis] (E-mail)
> Subject: Re: [wss] Error in WSS interop example #2
>
>
>
> Hi,
>
> Sorry I missed this the first time around:
>
> The xmlenc schema does not specify anyAttribute; I think
> this means that the permitted attributes of EncryptedData
> are fixed, and the original unqualified Id attribute would
> then be correct.
>
> Or am I missing something?
>
> merlin
>
>   <complexType name='EncryptedType' abstract='true'>
>     <sequence>
>       <element name='EncryptionMethod' type='xenc:EncryptionMethodType'
>                minOccurs='0'/>
>       <element ref='ds:KeyInfo' minOccurs='0'/>
>       <element ref='xenc:CipherData'/>
>       <element ref='xenc:EncryptionProperties' minOccurs='0'/>
>     </sequence>
>     <attribute name='Id' type='ID' use='optional'/>
>     <attribute name='Type' type='anyURI' use='optional'/>
>     <attribute name='MimeType' type='string' use='optional'/>
>     <attribute name='Encoding' type='anyURI' use='optional'/>
>    </complexType>
>
>   <element name='EncryptedData' type='xenc:EncryptedDataType'/>
>   <complexType name='EncryptedDataType'>
>     <complexContent>
>      <extension base='xenc:EncryptedType'>
>      </extension>
>     </complexContent>
>   </complexType>
>
> r/hlockhar@bea.com/2003.05.01/16:22:37
> >OK, noted.
> >
> >I am not sure if wsu is going to continue as a separate schema or not.
> >
> >I recall that on the last call, somebody (Tony?) was going to publish the
> >correct URLs for our schemas, but I do not see it in the minutes.
> >
> >Once I get this info I will update the docs.
> >
> >Hal
> >
> >> -----Original Message-----
> >> From: Eric Gravengaard [mailto:eric@reactivity.com]
> >> Sent: Tuesday, April 29, 2003 7:22 PM
> >> To: [wss oasis] (E-mail)
> >> Subject: [wss] Error in WSS interop example #2
> >>
> >>
> >> On or about line 324 we found this problem with the example:
> >>
> >> 	In the second example request, the line:
> >>
> >> 	 <xenc:EncryptedData Id="enc-un"
> >> Type="http://www.w3.org/2001/04/xmlenc#Element"
> >> xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
> >>
> >> 	should read:
> >>
> >> 	 <xenc:EncryptedData wsu:Id="enc-un"
> >> Type="http://www.w3.org/2001/04/xmlenc#Element"
> >> xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">
> >>
> >>
> >> The "Id" attribute has no namespace.
> >>
> >>
> >> -----------
> >> Reactivity
> >> Secure XML
> >>
> >
>
>
> ------------------------------------------------------------------
> -----------
> The information contained in this message is confidential and is intended
> for the addressee(s) only.  If you have received this message in error or
> there are any problems please notify the originator immediately.  The
> unauthorised use, disclosure, copying or alteration of this message is
> strictly forbidden. Baltimore Technologies plc will not be liable for
> direct, special, indirect or consequential damages arising from alteration
> of the contents of this message by a third party or as a result of any
> virus being passed on.
>
> This footnote confirms that this email message has been swept for Content
> Security threats, including computer viruses.
> http://www.baltimore.com
>
>