OPC: contents of SignatureProperty

[MURATA Makoto]

I still believe that there is a conflict here, but I
would like to make a comment about the
schema.

The SigantureProperty element in question appears within
an Object element.  The complex type for Object has
<any namespace="##any" processContents="lax"/>.

Does this wild card allow the SignatureProperty element
to have any attributes and contents?  No, processContents="lax"
implies that "·validate· if you can, don't worry if you can't"
(W3C XML Schema Part 1)

Regards,
Makoto


2014-02-25 11:56 GMT+09:00 MURATA Makoto <eb2m-mrt at asahi-net.or.jp>:

> I am studying digital signature in Office for the standardization
> of XAdES.
>
> I find that both Word 2007 and [MS-OFFCRYPTO] ignores a requirement
> in 29500-2:2012.
>
> 13.2.4.1 "Modifications to the XML Digital Signature
> Specification" in 29500-2:2012 specifies that "A
> SignatureProperty element shall contain exactly one
> SignatureTime child element".
>
> However, Word 2007 creates a different child element.
>
>       <SignatureProperty Id="idOfficeV1Details"
> Target="#idPackageSignature">
>         <SignatureInfoV1 xmlns="
> http://schemas.microsoft.com/office/2006/digsig">
>           ...
>         </SignatureInfoV1>
>       </SignatureProperty>
>
> This appears to follow "2.5.2.5 idOfficeObject Object Element"
> in [MS-OFFCRYPTO]
>
> "A SignatureProperties element containing a SignatureProperty
> element, which MUST contain a SignatureInfoV1 element that
> specifies the details of a digital signature in a
> document. The following XML Schema specifies the contents of
> the SignatureProperty element: "
>
> I think that there is a clear conflict here.
>
> --
> Regards,
>
> Makoto
>



-- 

Praying for the victims of the Japan Tohoku earthquake

Makoto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20140225/aaa1e794/attachment.html>