- From: Cantor, Scott <cantor.2@osu.edu>
- Date: Sat, 3 Sep 2011 20:33:41 +0000
- To: MURATA Makoto <eb2m-mrt@asahi-net.or.jp>, "public-xmlsec@w3.org" <public-xmlsec@w3.org>
On 9/3/11 4:03 PM, "MURATA Makoto" <eb2m-mrt@asahi-net.or.jp> wrote: > >If the schema for Encryption 1.1 does not normatively reference >the schema for Signature 1.1, validity of this subtree against the >schema for Signature 1.1 is not required. Validators are required >to validate this subtree only when validity against both the schema >for Signature 1.1 and the schema for Encryption 1.1 is checked. >Is this really your intention? Yes. If an application expects to support both schemas, thatıs its responsibility to deal with. The import mechanism is for bringing in types that an importing schema needs to reuse in some way. It isn't appropriate to import a schema to make a conformance statement about what types an implementation that is using the importing schema might be required to also support. I have never seen that done, and it certainly isn't the purpose of the import mechanism. It is simply understood that if you want to conform to XML Encryption 1.1, you must also conform to the normatively referenced parts of XML Signature 1.1, schemas included. -- Scott
Received on Saturday, 3 September 2011 23:57:41 UTC