[
Lists Home |
Date Index |
Thread Index
]
- From: "Roger L. Costello" <costello@mitre.org>
- To: xml-dev@lists.xml.org, "Ripley,Michael W." <rip@mitre.org>
- Date: Wed, 11 Oct 2000 06:42:41 -0400
[Here's a response that I received directly. Any comments on it?]
>"When should an item be declared as an element versus when should an
>item be declared as a type?"
I think it's a matter of style. As you showed in your examples, you
can basically get done what needs to get done with either method.
My take on the style would be:
- use an element when all components of the element declaration will be
reused and semantically the reuse will mean the same thing (Elevation,
BostonElevation, FrankfurtElevation, SidneyElevation, etc.)
- use a type when the type definition will be reused for semantically
different elements (e.g., a 'money' type definition that is reused for
elements UnitPrice, Subtotal, ShippingAndHandling, Total, etc.).
|