[xsd-users] import, include, namespaces, restriction and schema versioning

[Bill Pringlemeir]

On 19 Aug 2009, boris at codesynthesis.com wrote:

> But the fist step is to really understand the use cases and it would
> be helpful to know how you plan to handle the other problems of
> versioning.

I can give several use cases not necessarily related to versioning,

1. You are a North American wishing to write an open source TV capture
application.

In order to do this you need schedule information.  There is a SOAP
service provided by Tribune Media Services,

  http://xmlbeans.googlepages.com/
   - entry TMS XTVD - Tribune Media Services eXtensible TV Data

It is highly unlikely that you will be generating the program
schedules in your program.  At the SOAP level, you wish to
generate/write the REQUEST messages and read the RESPONSE.  You might
wish to use the generate the RESPONSE schedule by reading from a
persisted file.  However, this would generally be a subset of the
returned data and you might choose another data storage mechanism such
as a database.  This would be a benefit if you wanted to query for any
recent 'movies' that will be airing and automate the capture of these
programs via a TV tuner card.  At first if might seem like XML
persistence is a good thing, but it would probably only be useful for
debugging.


2. You are part of a financial institution that is using the FpML
schemas as a standard.  Your application only deals with Mortgages.
Derivative, currency exchange, and many other data modeled in the FpML
are not in the scope of your application.  You want to use the FpML
schemas (and any future updates) and restrict the amount of generated
code needed by your application's domain.

These are both generally code size issues. Maybe these are similar
problems or a sub-set of the versioning issue?

Fwiw,
Bill Pringlemeir.