Altova Mailing List Archives

Re: XML Schemas: Best Practices

From: "Roger L. Costello" <costello@-----.--->
To: xml-dev@-----.---.---
Date: 10/19/2000 4:32:00 AM
Caroline Clewlow wrote:
> The third approach seems to bear a resemblance to the reasoning behind
> object oriented approaches to programming.  i.e. re-use, 
> encapsulation, and data hiding ( namespace hiding in this case ;).  

Excellent observation.  I will note it in the online version of the Best
Practices document.

> To reflect this it may be an idea to name it the Object Design
> approach

I will mark this down as a possible name for the Third Design.
> The choice between the three approaches seems to again come down to 
> a style driven decision.  

Oh my, I do hope that it's not a matter of "style".  "Style" seems to
suggest "by intuition", or "by personal preference".  My hope is that we
are developing guidelines to empower a schema designer can make
intelligent decisions based upon a concrete decision space (i.e., all
the design alternatives are spelled out, and the pros and cons of each
design alternative is clearly understood).  

However, your point is well taken.  We have not clearly spelled out the
implications of the First, Second, and Third design.  Please keep us
focused until you (everyone) feel(s) comfortable that it is no longer a
"style" decision, but rather an "engineering" decision.  Thanks! /Roger


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.