I largely agree with Mike.

XML is flexible as compared to RDBMS data. In RDBMS, we need to
specify Schema first and then put the data in database.

Whereas in XML, we can write XML instances directly and
distribute/consume them, without the need of designing Schemas.

But as a database theorist, I would like to model first and then
create the instances, so any instances we produce, should conform to
the model.

On 7/11/08, Lyallex <lyallex@g...> wrote:
>
> Hi
>
> Now obviously I'm a beginner, I'm currently engrossed in
> http://www.w3.org/TR/xmlschema-0/
>
> I have written a (very) simple validator using classes from the Java
> jdk1.5.0_15 and I'm using this to play around with the examples in
> that document.
>
> I'm doing this because there may/will be a requirement to write xml
> for my current project.
>
> The question is, when you are 'designing' a new xml document/schema
> which do you do first ?
>
> I've started developing an xml document, then I will develop a schema
> that can be used to validate this document.
> Is this a sensible approach or do people usually do it the other way around ?
>
> Is it reasonable to simply present a client with a schema and say
> 'your xml must comply with this' or is it better to give them an
> example xml document and the schema to go with it so that they can see
> what is required and also have the ability to validate the document
> before transmitting it to us.
>
> Apologies if these questions are too basic for the experts, if this is
> not the place to ask such questions then rather than shout at me would
> you be so kind as to redirect me to the appropriate list ?
>
> many thanks
>
> lyallex


-- 
Regards,
Mukul Gandhi

From mathieu.malaterre@g... Mon Jul 14 00:30:01 2008
Received: from farnsworth.w3.org ([128.30.52.43]