RE: [xml-dev] What techniques do you employ to ensure that your data isp

It is an interactive process that evolves over time as your learn about the data in your ecosystem.

What you need is an adaptive validation framework.

This is why CAM templates are the preferred tool for people working in a multi-partner network of information exchanges. They allow you to contextually control the rules and content model dynamically.

This is vital. For example an auto industry parts distributor is using CAM templates to manage interaction with over 500 downstream partners.

You cannot predict when those partners make changes to their systems. So you have to be prepared and able to make changes in real time.

Also CAM allows you to do lookups to SQL databases - again essential for things like part numbers, customer numbers et al that cannot be static in XML files.

See IBM article for more details:

-------- Original Message --------
Subject: RE: [xml-dev] What techniques do you employ to ensure that
your data is precisely and unambiguously specified?
From: "Costello, Roger L." <costello@mitre.org>
Date: Mon, September 24, 2012 3:08 pm
To: "xml-dev@lists.xml.org" <xml-dev@lists.xml.org>

Michael Kay wrote:

> Being too careful can make things worse, because the longer and more
> formal the spec, the fewer people will read it.

Apparently the W3C does not agree. Consider:

- The XML Schema 1.1 specification is 380 pages
and is formally written.

- The XSLT 3.0 specification is 530 pages
and is formally written.

/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