Lists Home |
Date Index |
- To: firstname.lastname@example.org
- Subject: Re: [xml-dev] maxoccurs='unbounded' under xsd:all group.
- From: Roxette Lurge <email@example.com>
- Date: Wed, 18 Jan 2006 06:41:37 -0800 (PST)
- Cc: David Carlisle <firstname.lastname@example.org>
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=NeTuF7LL5V1ot6vSGiRfREmnVrfEvow+TUj5uD0ln3+skMXNz8ASdjJdkeBFKSyAn/ri+HLKZ58mudNGi6MZAMMt5PIze7CvUKpihOlTRN2kopstFLavGtBBbgCTKFv5JQ3F7vKrg2gifR6KqwEqHz4AqyTDUdI5zXNNuSEtgdM= ;
- In-reply-to: <200601172259.WAA10100@penguin.nag.co.uk>
The application allows "on-the-fly" uploading of
schemas (performing in-memory), their validation and
then validation of the xml sent along with proper
So then, all the validation has to be done by the
schema. Even the "unique" and "keyref" is used for
cross validation and uniqueness.
--- David Carlisle <email@example.com> wrote:
> > I don't see any other way other than to change xml
> > structure to get rid of this issue.
> do you _have_ to express this constraint at the
> schema level?
> There are always some things a schema (even a relax
> ng one) can't catch
> and have to be caught in the application. If
> changing the xml format is
> inconvenient just schema type it as
> so at least the schema checks that the set of child
> elements is
> plausible, and defer the cardinality checks to
> whatever application is
> handling the schema validated input.
> This e-mail has been scanned for all viruses by
> Star. The
> service is powered by MessageLabs. For more
> information on a proactive
> anti-virus service working around the clock, around
> the globe, visit:
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around