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

RE: How compatible are XML Schema implementations?

• From: "Arnold, Curt" <Curt.Arnold@h...>
• To: "'xml-dev@l...'" <xml-dev@l...>
• Date: Thu, 11 Jan 2001 13:05:21 -0700

There isn't much overlap between platforms, so it seems at this instant you are tied to a specific implementation once you have chosen your platform.

Xerces-J doesn't support the Candidate Recommendation and probably will skip to whatever comes next, so if you use it you will not be interoperable with anything else.  I'd recommend avoiding it until
it catches up.

Oracle's Schema Processors for Java, C++ and C seem to be the only Candidate Recommendation implementations on those platforms.

XSV is written in Python (maybe it could also be called from Java using JPython).

I don't know if you could use XML Spy's COM interfaces to perform schema validation on Windows.

Until schema conformance tests are published and the implementations start becoming more complete, you basically have to check your schemas against multiple processors to make sure that you aren't
running into a bug, unimplemented feature, or misinterpretation of the spec.  OASIS has a working group for XML Schema conformance but I'm not aware of its state.  I started a test suite for the April
draft at http://xmlconf.sourceforge.net, but haven't revisited it for the Candidate Recommendation.  If and when OASIS publishes a suite, I assume that the xmlconf project will provide harnesses to
test the major implementations.

Did I leave anybody's favorite processor out?

• Prev by Date: RE: Schema localization? *Newbie alert*
• Next by Date: Re: Should xlink:arcrole or xlink:role be the primary way todispatchon related resources? was Re: URIs, names and well known RDDL names,
• Previous by thread: Re: How compatible are XML Schema implementations?
• Next by thread: URI references and UTF-8 based escaping
• Index(es):
  • Date
  • Thread