[XML-DEV Mailing List Archive Home]
[By Thread]
[By Date]
[Recent Entries]
[Reply To This Message]
Re: Caution using XML Schema backward- or forward-compatibilit
- From: "Greg Hunt" <greg@f...>
- To: "Stephen Green" <stephengreenubl@g...>
- Date: Thu, 27 Dec 2007 18:08:24 +1100

And if we engage in "avoidance of making things mandatory" for any reason other than enforcing real business data constraints we reduce the value of schema-driven validation. Doing that requires the applications to do their own structural validation to enforce the business requirements for mandatory-ness which in turn makes implementing changes or assessing the impact of a change even harder.
Greg
On 12/27/07, Stephen Green <stephengreenubl@g...> wrote:
There are two cautions I am happy with here: 1. That forwards-compatibility places great constraints on versioning - that these constraints mean a lot of planning has to go into the earliest version to reduce such constraints,
e.g. avoidance of making things mandatory because they cannot then be made optional later without breaking forwards-compatibility (in terms of instance/schema validation). The problem with this seems to be that it is
in these early stages that designers are least likely to foresee such future requirements for which they must plan. 2. That mistakes made in these early stages can lead to designers wanting to change semantics to try to
compensate for such mistakes, e.g. because an element wasn't made optional it cannot be removed and so there is a temptation to change its semantics - to reuse it for something else rather than remove it. This is
what I believe Roger is warning is not actually any better than breaking perceived forwards-compatibility. It is just breaking compatibility but hiding the fact of doing so from the older schema.
> Designing a new version of an XML Schema to be forward-compatible with
> an old version necessitates that the only changes made in the new > version are "subset" changes, such as: > > - constrain an element's or attribute's datatype > - reduce the number of occurrences of an element
> - eliminate an optional element or attribute > - remove an element from a choice > > This is very restrictive. And to what avail? Answer: to enable > validation of new XML instance documents against an old XML Schema.
> But as described above, just because data can be validated doesn't mean > it can be processed. >
-- Stephen Green
Partner SystML, http://www.systml.co.uk Tel: +44 (0) 117 9541606
http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice
_______________________________________________________________________
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@l... subscribe:
xml-dev-subscribe@l... List archive: http://lists.xml.org/archives/xml-dev/ List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
|
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
RSS 2.0 |
 |
Atom 0.3 |
 |
|
Stylus Studio has published XML-DEV in RSS and ATOM formats,
enabling users to easily subcribe to the list from their preferred news reader application.
|
Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website.
they were not included by the author in the initial post. To view the content without the Sponsor Links please
click here.
|
|