On Sun, Feb 9, 2014 at 2:27 PM, Costello, Roger L. <costello@m...> wrote:
> Hi Folks,
>
> I see many XML instances (and corresponding XML Schemas) with an "other" catchall element.
>
> I wish to convince you that an "other" catchall element is contrary to one's objectives and should be avoided.
>
> First, a quote from the book, "Principles of Program Design" (Jackson Design Methodology):
>
>         The structure of a program must be
>         based on the structures of all the data
>         it processes.
>
> A corollary to that is:
>
>         Data should model the real world.
>
> So there is this deep connection:
>
>         real world --> data model --> program structure
>
> In the real world there is no "other" component: When was the last time you drove an "other car" or purchased an "other vegetable"?
>
> So it is wrong to create a data model for a nonexistent real world entity. Likewise it is wrong to write a program component for "other" data.
>

This is the point where you should read something like

http://www.amazon.com/Understanding-Uncertainty-Dennis-V-Lindley/dp/0470043830/ref=cm_cr_pr_product_top

_______________________________________________________________________

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