RE: [xml-dev] Design XML Schemas to conform to these principles

[<toby.considine@gmail.com>]

That's not a bad list.

I would add, don't assume it will be actually transmitted in XML. XML is a
great means to express an information model, and to define constraints, and
even to define extensibility, in a way that there are abundant software
tools able to use.

The actual message may then be sent using RESTful JSON, or in AMQP, or in
interaction patterns defined in RabbitMQ, or whatever else makes sense.
Systems that go back to a common information model, easily expressed in XML,
can always find a path to be transformed into each other.

 

-----Original Message-----
From: Roger L Costello <costello@mitre.org> 
Sent: Wednesday, January 12, 2022 9:27 AM
To: xml-dev@lists.xml.org
Subject: [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