[
Lists Home |
Date Index |
Thread Index
]
- From: ht@cogsci.ed.ac.uk (Henry S. Thompson)
- To: "Arnold, Curt" <Curt.Arnold@hyprotech.com>
- Date: 20 Apr 2000 17:29:37 +0100
"Arnold, Curt" <Curt.Arnold@hyprotech.com> writes:
> Curt wrote:
>
> > The param element reference in the named-template type
> > definition should have a minOccur="0" and a
> > maxOccur="unbounded". As written, a template has to have one
> > and only one param.
>
> Don wrote:
>
> My reading of rule 4.3 under the {content type} definition (found under
> section 4.3.3) implies that there is an implicit <choice minOccurs='0'
> maxOccurs='unbounded' > particle over the particle children of a
> content=mixed complex type. I'll defer to Henry on this.
Don is right, but as I've said I think this is sowing enough confusion
that the expected benefit is being overwhelmed.
> Curt reply:
>
> I guess it depends on what the intrepretation of "extending" a
> complex type that ultimately derived from a complex type that has a
> content of mixed. If extending means that param is magically added
> into the mixed content of its base type, then the multiplicity would
> be implied. If extension in this context means appears that content
> declared in the derived type appears after the base complexType's
> content has been satisifed then param is in the wrong place with the
> wrong multiplicity. Possibly the behavior is already explicit in
> the schema docs. But for me to get my mind around the schema doc, I
> have to work out from the schemas to schema to the prose and not the
> other way around.
I suspect there's some unclarity in this case -- I'll get back to you.
ht
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
W3C Fellow 1999--2001, part-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/
***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************
|