AW: Design XML Schemas to conform to these principles

["Kottmann, Renzo (Finanzen, 44-5)" <renzo.kottmann@finanzen.bremen.de>]

Spontanously, I would add 

*  Define a consistent naming concept for attributes and elements as close as possible to the terms and names used in the domain that is being modeled 

ciao,

renzo

-----Ursprüngliche Nachricht-----
Von: Roger L Costello <costello@mitre.org> 
Gesendet: Mittwoch, 12. Januar 2022 15:27
An: xml-dev@lists.xml.org
Betreff: [EXTERN]-[xml-dev] 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

_______________________________________________________________________

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@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php