Lists Home |
Date Index |
Thanks very much for the advice. I was not entirely sure what you meant by a
meta-schema, so I looked Googled it and found this article:
I don't think you meant that I should modify XMLSchema.xsd, but instead that
I should have an Events.xsd schema that is somehow modified to become
UCBerkeleyEvents.xsd. That is exactly what I did in the schemas I pointed to
in the first message, and I tried using redefines on one hand and
substitution groups on the other to accomplish this. Since you mention
having schemas in the same namespace, I'm guessing you're referring to a
process that involves redefines? But you also mention transformation & input
parameters, so I'm not sure...can you clarify?
----- Original Message -----
From: "Michael Kay" <firstname.lastname@example.org>
To: "'Allison Bloodworth'" <email@example.com>;
Sent: Monday, November 01, 2004 12:22 PM
Subject: RE: [xml-dev] Creating flexible & extensible schemas (for a
> > One question I'm struggling with is whether to make most of
> > the elements optional.
> There doesn't have to be one schema.
> It can be a bit tricky to manage multiple schemas for the same namespace
> (because there are parts of the spec that seem to assume that by
> the namespace, you have identified the schema), but it's definitely part
> the design thinking that the validation rules you want to impose might be
> stricter in some circumstances, weaker in others.
> The right solution here might be a meta-schema that can be transformed
> (using a set of input parameters) into the target schema you actually use
> for validation. For example, this allows the list of enumeration values to
> be varied.
> Michael Kay
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>