On 07/04/13 23:00, G. Ken Holman wrote:
To repeat and expand:
... schema-first or schema-centric design, any situation in which the
schema is considered more than a snapshot of current conversational
practice, is actively harmful.
Well ... now I think that might be a step too far.
Perhaps if you are trying to respond to a flexible environment where
data structures are allowed to change to a changing set of criteria or
stimuli.
But if you have a schema that, say, reflects general accounting
principles that are adopted (or mandated; or even legislated), there can
be benefit in treating the schema as sacrosanct and going through hoops
with your data to match the schema.
uk.gov tax submissions are an example Ken.
Of no interest which came first, an instance or the schema,
but they are needed in many scenarios, but Simons not listening.
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
_______________________________________________________________________
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