- From: Anli Shundi <ashundi@tibco.com>
- Date: Mon, 27 Oct 2003 12:07:03 -0500
- To: "Henry S. Thompson" <ht@cogsci.ed.ac.uk>, marktt@excite.com
- Cc: xmlschema-dev@w3.org
Well, I think point 2 of #sch-props-correct [1] excludes such multiple definitions. From the semantics of <include> [2] (point 3) both definitions of such attribute are included -- they stem from two different locations. [1] http://www.w3.org/TR/xmlschema-1/#sch-props-correct [2] http://www.w3.org/TR/xmlschema-1/#src-include Anli Shundi ashundi@tibco.com TIBCO Software Inc. office: (919) 969-6518 www.tibco.com -----Original Message----- From: xmlschema-dev-request@w3.org [mailto:xmlschema-dev-request@w3.org]On Behalf Of Henry S. Thompson Sent: Monday, October 27, 2003 5:12 AM To: marktt@excite.com Cc: xmlschema-dev@w3.org Subject: Re: [xmlschema-dev] <none> "Mark Thomson" <marktt@excite.com> writes: > Suppose a schema <include>s two other schemas. The first one has a global attribute declared as follows: > > <attribute name="AA"> > <simpleType> > <restriction base="xsd:float"/> > <simpleType> > </attribute> > > and the second one has the same attribute, but declared as follows: > > > <attribute name="AA" type="xsd:float"/> > > > Is this ok? or should it be reported as an error? (i.e., are the > types equivalent?) (I didn't see anything in the specs that > disallows empty <restriction> elements). There's nothing disallowing it. The REC is not completely clear on what constitutes an "component identical" to another component, so I'm afraid schema processors have some license to differ on this one. The WG plans to tighten this up in the next version (although I won't predict which way it will go on this particular example). ht -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh Half-time member of W3C Team 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail really from me _always_ has this .sig -- mail without it is forged spam]
Received on Monday, 27 October 2003 12:08:33 UTC