From: Ellen K. 

I'm not talking about order, I'm talking about adding an attribute that
doesn't exist EXCEPT in the XSD and associated XML document(s).  In other
words, the class in the Business Object Model has 5 properties, but they
instructed us to add a 6th attribute to the corresponding element in the
XSD... and then we were instructed to create a rule that depended on that
6th attribute and use it to process the XML data.

Just to be perfectly clear, I am not talking about adding a second instance
of one of the existing attributes, I am talking about a whole new
attribute.

On Wed, 25 May 2005 14:21:37 +0100, Adam
 wrote in message
:

>Ellen K wrote:
>
>> Yeah, well the interesting part is that programmers don't have a clue about
>> data modeling and consider the database a necessary evil because

"It's
>> so hard to use it with objects." 
>>
>> In our ILOG training, when we got to the part about using XML, they had us
ADD
>> AN ATTRIBUTE IN THE XSD THAT WAS NOT PART OF THE BUSINESS OBJECT MODEL, then
>> process the XML data using a rule that used that attribute. Like, either the
>> business needs that rule or they don't, if they need it, the attribute
belongs
>> in the BOM.
>>
>
>Depends...
>
>e.g. XML elements have no order unless specified as a sequence & then if
>you have 1..n of the same element again you have no order.
>
>It may be necessary to enforce element order. However this is a purely
>xml problem & thus can be happily kept at the xml level.
>
>
>Adam

--- BBBS/NT v4.01 Flag-5