[
Lists Home |
Date Index |
Thread Index
]
Did anyone consider using XSLT to transform this into a more usable XML
format?
e.g.
<reportDefinition>
<officers>
<secretary>
<name />
<appointmentDate>
<dateOfBirth />
. . .
Then the XSD would be much easier to create, since the previous values are
now element names.
I know it is an extra step, but the original XML looks like another of those
key/value pairs created to make it easy to get into an RDBMS or some other
table mechanism. and since there are not a lot of XPATH generators, the
XPATH statements in the new structure would be much simpler and more obvious
to code by hand.
Just a thought . . .
Owen
----- Original Message -----
From: "Cross, Neal - Senior Developer" <ncross@icc.co.uk>
To: "Chiusano Joseph" <chiusano_joseph@bah.com>
Cc: "Philippe Poulard" <Philippe.Poulard@sophia.inria.fr>;
<xml-dev@lists.xml.org>
Sent: Wednesday, September 08, 2004 7:47 AM
Subject: RE: [xml-dev] [schema] which assertions can't you express ?
> Firstly there is only one element name in the whole structure so every XSD
tool I have used can only see the one element.
> Am I missing something here?
>
> -----Original Message-----
> From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
> Sent: 08 September 2004 14:40
> To: Cross, Neal - Senior Developer
> Cc: Philippe Poulard; xml-dev@lists.xml.org
> Subject: Re: [xml-dev] [schema] which assertions can't you express ?
>
>
> Hmmm...Unless I'm missing something, this all should be able to be
> handled in XML Schema. What is it about it that makes you think
> otherwise?
>
> Kind Regards,
> Joe Chiusano
> Booz Allen Hamilton
> Strategy and Technology Consultants to the World
>
> "Cross, Neal - Senior Developer" wrote:
> >
> > I have found that a schema is of no use to us at all because of the way
that our XML is structured:-
> >
> > <section id="report definition">
> > <section id="officers">
> > <section id="secretary" limit="2">
> > <section id="name"/>
> > <section id="appointment date"/>
> > <section id="date of birth"/>
> > <section id="occupation"/>
> > <section id="address"/>
> > <section id="disqualified flag"/>
> > <section id="disqualified reason"/>
> > <section id="disqualified start"/>
> > <section id="disqualified end"/>
> > <section id="previous address" limit="1">
> > <section id="address"/>
> > </section>
> >
> > etc, etc.
> >
> > Now, how do I create a schema to represent this considering that is is
indexed by the attribute value of id?
> >
> > -----Original Message-----
> > From: Philippe Poulard [mailto:Philippe.Poulard@sophia.inria.fr]
> > Sent: 08 September 2004 12:54
> > To: xml-dev@lists.xml.org
> > Subject: [xml-dev] [schema] which assertions can't you express ?
> >
> > hi,
> >
> > An XML Schema is the expression of some assertions expected on an XML
> > document class. Assertions on XML documents ensure that applications
> > will process them without causing faults. Expressing assertions with
> > schemas ensure that applications developpers will spend most of their
> > time in designing data process and few of their time in controlling
them.
> >
> > Any schema technology is designed to cover numbers of assertions
> > expressed. However, if think that the existing schema technologies (DTD,
> > W3C XML Schema, Relax NG, Schematron) can't express some constraint
types.
> >
> > I have some ideas of what these constraint types might be, but I'd like
> > to know, helped by your own experiences, which kind of useful assertions
> > can't be expressed with these schema technologies (so frustrating).
> >
> > For example :
> > -i'd like that the number of occurrences of an element is equal to a
> > value of a given attribute (Schematron could do that)
> > -i'd like that the value of a given attribute exists in my RDBMS
> > -etc...
> >
> > Thanks in advance
> > --
> > Cordialement,
> >
> > ///
> > (. .)
> > -----ooO--(_)--Ooo-----
> > | Philippe Poulard |
> > -----------------------
> >
> > -----------------------------------------------------------------
> > 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>
> >
> >
############################################################################
#########
> > This e-mail message has been scanned for Viruses and Content.
> > BOSS
> >
############################################################################
#########
> >
> > -----------------------------------------------------------------
> > 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>
>
> --
> Kind Regards,
> Joseph Chiusano
> Associate
> Booz Allen Hamilton
>
############################################################################
#########
> This e-mail message has been scanned for Viruses and Content.
> BOSS
>
############################################################################
#########
>
> -----------------------------------------------------------------
> 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>
>
>
|
