XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Design XML Schemas to conform to these principles

Hi Folks,

I will be making an argument to some colleagues about how to design XML Schemas. Here's the pitch I will be making:

Before designing an XML Schema, create a list of principles that you want the schema design to conform to. I recommend the following three principles:

1. Design the schema so it can be easily changed when requirements change.

2. Design the schema to conform to the DRY (Don't Repeat Yourself) principle.

3. Design the schema simply. The schema should be easily understood even if the domain that it is modeling is not easily understood.

Do you agree with this list of principles? Are there other principles that you recommend adding? 

/Roger


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS