Hi Folks,
 
Recall that when we began discussing this thread the following
important observation was made:

    When creating a data specification 
    it is important to get inputs from 
    a diverse set of people. Different 
    people have different perspectives 
    on the data. Never assume that any 
    one person has the whole picture. 
    Get inputs from SMEs, TEs, users of 
    applications that will use the data, 
    as well as business people.

I am attempting to give an example of input from a business manager
influencing a data specification (and thereby ultimately influencing
the resultant XML data design).

The example I proposed is that during the development of a data
specification, a business manager inputs this business requirement into
the discussion:

     Our company has a partnership with Paypal. 
     We earn money each time a customer pays using 
     Paypal. While we do accept the other payment 
     methods, we earn no money with them. So, be 
     sure to add a sentence that Paypal is the 
     preferred payment method.

The result of this input is that a sentence is added to the data
specification about Paypal being the preferred payment method, and then
ultimately the business input trickles down to the resultant XML data
design. For example, suppose a "preferred" attribute is added to an XML
implementation:

   <Accepted-Payment-Methods>
       <Method preferred="true">Paypal</Method>
       <Method preferred="false">money order</Method>
       <Method preferred="false">cashier's check</Method>
   </Accepted-Payment-Methods>

So, my question is this: 

   Is the example I propose a reasonable illustration
   of a business requirement influencing
   a data specification and the resultant
   XML data design?

/Roger