[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

incompatible uses of XML Schema

• To: xml-dev@l...
• Subject: incompatible uses of XML Schema
• Subject: incompatible uses of XML Schema
• From: "Rick Jelliffe" <ricko@a...>
• Date: Thu, 21 Apr 2005 14:58:16 +1000 (EST)
• Importance: Normal
• In-reply-to: <20050420172216.35625.qmail@w...>
• References: <20050420172216.35625.qmail@w...>
• User-agent: SquirrelMail/1.4.2

I just got a call from a bespoke client (the XML guru in a large bank)
asking whether I knew of any XML Schema refactoring tools.

His problem is that one of their systems (from a big company)
does not handle recursive elements.  Another one of their
systems (from another big company) does not handle substitution
groups (or, at least, dynamic use of xsi:type.) Another of their
systems (from a third big company) does not handle wildcards.
(Some departments also used another tool that generated ambiguous
schemas.)

This is causing them a major headache: they are having to
refactor 7,000 element schemas by hand to munge them into
forms suited for each system.

Their schema-centricism has basically stuffed up the ready
interoperability they thought they were buying into with XML,
on a practical level. This is obviously a trap: moving to a
services-oriented architecture means that the providers can
say "we provide XML with a schema" and the pointy-headed bosses
can say "you service-user: this tool accepts XML with a schema
so you must use that!" and the service-user has little recourse.

Does anyone know of any XML Schema refactoring tools that can,
say, replace substitution groups with explicit lists of
elements in a schema?  I am half thinking of developing a Topologi
utility for this: any other requests in this area?

Cheers
Rick Jelliffe

• Follow-Ups:
  • Re: incompatible uses of XML Schema
    • From: Micah Dubinko <micah@d...>
  • Re: incompatible uses of XML Schema
    • From: James Fuller <jim.fuller@r...>

• References:
  • newbie help -- schema development
    • From: Scott Paulding <pldng@y...>

• Prev by Date: Re: A Stakeholder's Response: XQuery APIs for Middle
• Next by Date: RE: A Stakeholder's Response: XQuery APIs for Middle Tier and Clients
• Previous by thread: newbie help -- schema development
• Next by thread: Re: incompatible uses of XML Schema
• Index(es):
  • Date
  • Thread