Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries >Thread Prev - Inadvertently restricting mixed content [Thread Next] Re: Inadvertently restricting mixed contentTo: xmlschema-dev@--.--- Date: 2/3/2005 4:30:00 AM
I would expect the effect to be different depending upon the use of
extension or restriction. With extension it should automatically be
whatever the original definition was, not a new default of false.
For restriction, I could see requiring that you get the declaration
correct, but a default is not appropriate here either. My logic here is
that restriction requires me to replicate most of the original content
model anyway, I would expect the "mixed" attribute to be included in that
process.
..dan
At 11:45 AM 2/3/2005, G. Ken Holman wrote:
>It appears that one cannot redefine a type and leave the mixed= nature of
>the original type untouched, which would be important if it were not known
>or, more important, arbitrary.
>
>Looking at Part 1, Section 3.4.2, mixed= on <xsd:complexType> has a
>default value of false.
>
>Consider I might have a type with mixed content:
>
> <xsd:complexType name="abcType" mixed="true">
> <xsd:attribute ...>
> ...
>
>Now, I redefine that type in an importing schema fragment:
>
> <xsd:redefine ...>
> <xsd:complexType name="abcType">
> <xsd:complexContent>
> <xsd:extension base="abcType">
> ...
>
>The standard states there is an implicit mixed="false" because of the
>default value. This turns off my mixed content, when all I wanted to do
>was extend the existing type with some elements.
>
>In this case I know I can just add mixed="true" in the redefinition to
>ensure the content is mixed ... but am I missing a way in which I can
>redefine a type while preserving its mixed= property?
>
>My guess is no, because if I wanted to turn off the mixed content property
>I would intuitively say mixed="false" ... but my intuition to leave it
>unchanged is to leave the attribute absent ... but when absent the default
>value forces the redefinition to not be mixed. So, it appears I have to
>know a priori that a given type I'm redefining is mixed or not and the
>burden is on me to preserve it.
>
>Have I read anything incorrectly in this regard?
>
>Thanks for any guidance.
>
>............................... Ken
>
>--
>World-wide on-site corporate, govt. & user group XML/XSL training.
>G. Ken Holman mailto:gkholman@C...
>Crane Softwrights Ltd. http://www.CraneSoftwrights.com/x/
>Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995)
>Male Breast Cancer Awareness http://www.CraneSoftwrights.com/x/bc
>Legal business disclaimers: http://www.CraneSoftwrights.com/legal
>
---------------------------------------------------------------------------
Danny Vint
Specializing in Panoramic Images of California and the West
http://www.dvint.com
voice: 510-522-4703
fax: 801-749-3229
From gkholman@C... Fri Feb 04 01:12:46 2005
Received: from lisa.w3.org ([128.30.52.41])
by | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
