- From: <noah_mendelsohn@us.ibm.com>
- Date: Tue, 19 Sep 2006 08:30:48 -0400
- To: "Michael Kay" <mike@saxonica.com>
- Cc: "'Sandy Gao'" <sandygao@ca.ibm.com>, "'Wolfgang Jeltsch'" <wolfgang@jeltsch.net>, xmlschema-dev@w3.org
Fair enough. I think we've agreed that the spec. is not nearly as clear as it should be on the whole architecture surrounding this. I suppose I was trying to say that its intentions seem pretty clear to me, at least in this somewhat limited but very common case. -------------------------------------- Noah Mendelsohn IBM Corporation One Rogers Street Cambridge, MA 02142 1-617-693-4036 -------------------------------------- "Michael Kay" <mike@saxonica.com> 09/19/2006 04:07 AM To: <noah_mendelsohn@us.ibm.com> cc: "'Sandy Gao'" <sandygao@ca.ibm.com>, "'Wolfgang Jeltsch'" <wolfgang@jeltsch.net>, <xmlschema-dev@w3.org> Subject: RE: including a schema document multiple times > > The Recommendation says, as Sandy noted: > > "Note: The above is carefully worded so that multiple > <include>ing of the same schema document will not constitute > a violation of clause 2 of Schema Properties Correct > (§3.15.6), but applications are allowed, indeed encouraged, > to avoid <include>ing the same schema document more than once > to forestall the necessity of establishing identity component > by component." > > Though a language lawyer could surely find lots of wiggle > room, I don't think it's a great leap to suggest that this > does cover the case Well, it's a bit odd to claim that the spec is clear because it contains a non-normative note that claims the spec is clear, rather than pointing to the normative text that is claimed to be clear... If the spec really were carefully worded, then it wouldn't be necessary to say so. Michael Kay http://www.saxonica.com/
Received on Tuesday, 19 September 2006 12:31:25 UTC