- From: Frederick Hirsch <Frederick.Hirsch@nokia.com>
- Date: Mon, 31 Aug 2009 12:23:17 -0400
- To: XMLSec WG Public List <public-xmlsec@w3.org>
- Cc: Frederick Hirsch <Frederick.Hirsch@nokia.com>
- Message-Id: <33B68255-62A0-4B51-8D46-99A7DE42C3A7@nokia.com>
Forwarded, with permission. Contains revised RNG schema. regards, Frederick Frederick Hirsch Nokia Begin forwarded message: > From: "ext MURATA Makoto (FAMILY Given)" <eb2m-mrt@asahi-net.or.jp> > Date: August 31, 2009 11:05:45 AM EDT > To: "Hirsch Frederick (Nokia-CIC/Boston)" <Frederick.Hirsch@nokia.com> > Cc: Thomas Roessler <tlr@w3.org>, Murata <eb2m-mrt@asahi-net.or.jp> > Subject: Re: The RELAX NG schema for XML-Signature > > Frederick, > > Yes, please feel free to forward my mails to the xml security wg > public > list. But I have significantly improved the schemas. > > xmldsig-core-schema.rnc is derived from xmldsig-core-schema.xsd, but > it is quite different from the original. First, this schema does not > allow any element via wildcards. Rather, it is expected to be > customized for each top-level schema. Second, this schema explicitly > specifies each combination of the Algorithm attribute, and the > permissible child elements. > > any-containing-xmldsig.rnc is a top-level schema, which invokes > xmldsig-core-schema.rnc. Any correct use of XML digital signature > is expected be valid against this top-level schema. > > I have tried to create a schema for another special case, namely > the combination of OOXML OPC and xmldsig. However, I first have > to understand OOXML OPC more. The spec looks very confusing to me. > > > Regards, > > SC34/WG4 Convenor > MURATA Makoto (FAMILY Given)
Attachments
- application/octet-stream attachment: xmldsig-core-schema.rnc
- application/octet-stream attachment: any-containing-xmldsig.rnc
Received on Monday, 31 August 2009 16:24:02 UTC