Lists Home |
Date Index |
- To: 'Dare Obasanjo' <firstname.lastname@example.org>, David Carlisle <email@example.com>
- Subject: RE: [xml-dev] Schema Namespace name, schemaLocation, and Schema V ersioning
- From: Mark Feblowitz <firstname.lastname@example.org>
- Date: Thu, 18 Jul 2002 12:26:06 -0400
- Cc: email@example.com, firstname.lastname@example.org, "Duane Krahn (E-mail)" <email@example.com>, "Satish Ramanathan (E-mail)" <Satish.Ramanathan@mro.com>, "Andrew Warren (E-mail)" <firstname.lastname@example.org>, "Kurt A Kanaskie (Kurt) (E-mail)" <email@example.com>, Mark Feblowitz <firstname.lastname@example.org>, "Michael Rowell (E-mail)" <email@example.com>
Dare (and others) -
Before we commit the same grievous error, I'd like to more about the kinds
of difficulties you've witnessed.
Frankly, with all of the dire warnings about breakage to XSL and other
namespace-aware applications, we are seriously considering following the W3C
lead and fixing a generic namespace, leaving the version processing to a
required/fixed version attribute.
If this is risky in some major way, I'd really like to know now.
From: Dare Obasanjo [mailto:firstname.lastname@example.org]
Sent: Thursday, July 18, 2002 12:11 PM
To: David Carlisle
Cc: email@example.com; firstname.lastname@example.org
I hope this isn't official W3C policy because it is
very poorly thought out. We at Microsoft are already
having problems with the fact that RECs like W3C XML
Schema add backwards incompatible changes in errata
does breaking our customer's previously working
schemata when they get a patch or upgrade for no fault
of their own or ours.
For the W3C to actually have a policy where versions
of their standards never change their namespace URI
would have many negative effects across the software
industry where XML is used. Either applications that
worked perfectly in the past would continually break
as changes to the RECs were made or the W3C would have
to ensure that every change they made was backwards
copmpatible which is an difficult burden and one it
has shown to be incapable of doing.
Thus I hope and pray this is your opinion and has no
bearing on any stated W3C policy on namespace URI for