Roger --

I am having a little trouble understanding your notation; where are 
you talking about data structures and where are you talking about 
data values?

If these are examples of data content I agree that you have one 
possible interpretation of the business requirement. (That is, if any 
form could be preferred. If there could be only one preferred form at 
a time there might be a better way to record which form is preferred 
at the moment.)

-- Tommie


At 6:59 PM -0400 10/15/08, Costello, Roger L. wrote:
>Hi Folks,
>
>Excellent discussion! 
>
>I revised the example, based on your comments:
>
>
>EXAMPLE OF BUSINESS INTERESTS INFLUENCING A DATA SPECIFICATION AND THE
>RESULTANT XML DATA DESIGN
>
>During the course of developing a particular data specification a SME
>states,
>
>      There are three methods of payment that our
>      company accepts: Paypal, money order, or
>      cashier's check.
>
>The SME's statement is added to the data specification.
>
>Then, a business person reads the statement and says:
>
>      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.
>
>As a result of this business interest, another sentence is added to the
>data specification:
>
>      There are three methods of payment that our
>      company accepts: Paypal, money order, or
>      cashier's check. However, the preferred
>      method is Paypal.
>
>
>IMPLEMENTATION
>
>Without the input from the business person, the data specification is
>translated into this implementation:
>
>    <Accepted-Payment-Methods>
>        <Method>Paypal</Method>
>        <Method>money order</Method>
>        <Method>cashier's check</Method>
>    </Accepted-Payment-Methods>
>
>However, because of the input from the business person, the data
>specification is translated into this 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>
>
>Note that an attribute - preferred - is added to each <Method> element
>to indicate whether or not the payment method is preferred.
>
>Thus we see an example of a business interest impacting a data
>specification and the resultant XML data design.
>
>
>QUESTION
>
>Is this revised version a legitimate example of a business interest
>influencing a data specification and the resultant XML data design?
>
>/Roger
>
>_______________________________________________________________________
>
>XML-DEV is a publicly archived, unmoderated list hosted by OASIS
>to support XML implementation and development. To minimize
>spam in the archives, you must subscribe before posting.
>
>[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
>Or unsubscribe: xml-dev-unsubscribe@l...
>subscribe: xml-dev-subscribe@l...
>List archive: http://lists.xml.org/archives/xml-dev/
>List Guidelines: http://www.oasis-open.org/maillists/guidelines.php


-- 

======================================================================
B. Tommie Usdin                        mailto:btusdin@m...
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                           Phone: 301/315-9631
Suite 207                                    Direct Line: 301/315-9634
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in XML and SGML
======================================================================