- From: Dare Obasanjo <dareo@microsoft.com>
- Date: Wed, 9 Feb 2005 17:56:39 -0800
- To: "David Orchard" <dorchard@bea.com>, "John Boyer" <JBoyer@PureEdge.com>, <www-tag@w3.org>
- Cc: "Bjoern Hoehrmann" <derhoermi@gmx.net>
> -----Original Message----- > From: www-tag-request@w3.org [mailto:www-tag-request@w3.org] > On Behalf Of David Orchard > Sent: Wednesday, February 09, 2005 5:24 PM > To: John Boyer; www-tag@w3.org > Cc: Bjoern Hoehrmann > Subject: RE: Significant W3C Confusion over Namespace Meaning > and Policy > > > I think that the general issue of namespace evolution is > currently covered in the extensibility and versioning > finding. There is a section on component version > identification choices which lists 4 broad based choices for > ns management. Further, the web arch v1 says that specs > should specify their namespace management policies. I assume you are talking about the document at http://www.w3.org/2001/tag/doc/versioning. If so I don't see how this addresses the core issue that the W3C has inconsistent practices when it comes to versioning core XML standards and tends to favor backwards incompatible revisions of specifications. That document is simply a laundry list of approaches to versioning XML formats and not guidance on what the W3C or the average vocabulary author should do when versioning a format. -- PITHY WORDS OF WISDOM New systems generate new problems. This posting is provided "AS IS" with no warranties, and confers no rights.
Received on Thursday, 10 February 2005 01:57:12 UTC