Re: New element definition added to 1.1 XML Signature Schema from Frederick.Hirsch@nokia.com on 2010-10-14 (public-xmlsec@w3.org from October 2010)

From: <Frederick.Hirsch@nokia.com>
Date: Thu, 14 Oct 2010 14:22:26 +0200
To: <eb2m-mrt@asahi-net.or.jp>
CC: <Frederick.Hirsch@nokia.com>, <public-xmlsec@w3.org>
Message-ID: <87BD0F70-C473-46A2-9810-B3FBB6ECF71F@nokia.com>

Makoto

Why is dsig11_X509Digest treated  differently than dsig11_OCSPResponse ?

They are both optional additions, currently the schema has:

ds_X509DataChild |= dsig11_OCSPResponse

Thus to be consistent I added:

ds_X509DataChild |= dsig11_X509Digest

should we have 

ds_X509DataForeignChild |= ddsig11_OCSPResponse

ds_X509DataForeignChild |= dsig11_X509Digest

Thanks

regards, Frederick

Frederick Hirsch
Nokia



On Oct 3, 2010, at 5:33 AM, ext MURATA Makoto (FAMILY Given) wrote:

> Frederick,
> 
> Thank you for providing a RELAX NG schema fragment.
> 
>> ds_X509DataChild |= dsig11_X509Digest
> 
> This line should be:
> 
>   ds_X509DataForeignChild |= dsig11_X509Digest
> 
> This is because ds_X509DataChild is intended to be fixed while
> ds_X509DataForeignChild is intended to be a customization point.
> 
>> dsig11_X509Digest = 
>> attribute Algorithm { xsd:anyURI },
>> xsd:base64Binary
> 
> This looks fine to me.
> 
> Cheers,
> Makoto
>

Received on Thursday, 14 October 2010 12:23:27 UTC