xml-dev - Re: Begging the Question (the novel)

[Uche Ogbuji <uche.ogbuji@fourthought.com>]

> On the contrary. It almost seems as if you haven't been reading any of
> the relevant specs covering these issues (XML Namespaces and XML
> Schemas).

Let's see.  I have implemented-- not used, implemented-- DOM Level 2,
XPath, XSLT, RDF, XLink, Schematron, a subset of SOAP and a host of
proprietary technologies that depend on namespaces.  I have read
REC-xml-names more often that I care to count.  I don't say I can
recite from memory since my memory is rather too
poor for that, but no one, yourself included, has shown me any
illumination from the spec I haven't seen myself.

I've read XML Schemas only once.  I hope not to have to repeat the
experience any time soon.  But I don't see that it is relevant.  I don't
use XML Schemas, but I do use namespaces.

> 1) RE: http://www.w3.org/TR/REC-xml-names
>
> The XML Namespaces recommendation states the following quite plainly
> (and very politely too):
>
> " [Definition:] The attribute's value, a URI reference, is the namespace
> name identifying the namespace. The namespace name, to serve its
> intended purpose, should have the characteristics of uniqueness and
> persistence. IT IS NOT A GOAL THAT IT BE DIRECTLY USABLE FOR RETRIEVAL
> OF A SCHEMA (IF ANY EXISTS)....However, it should be noted that ORDINARY
> URLS CAN BE MANAGED IN SUCH A WAY AS TO ACHIEVE THESE SAME GOALS."
>
> Translation:  The value of an XML Namespace URI doesn't have to be an
> actual URL referencing an XML Schema, BUT IT COULD BE, if you wished to
> implement it that way in an application.

What about what you quoted or said contradicts what I or anyone else has
been saying?

We all know that the REC is neutral on the issue.  That is the *precise*
problem.  Some of us are lobbying for an explicit deprecation, and you and
others keep waving at the REC.  What is it you think we'll see there that
we keep missing?  Certainly not the above.


-- 
Uche Ogbuji                               Principal Consultant
uche.ogbuji@fourthought.com               +1 303 583 9900 x 101
Fourthought, Inc.                         http://Fourthought.com
4735 East Walnut St, Ste. C, Boulder, CO 80301-2537, USA
Software-engineering, knowledge-management, XML, CORBA, Linux, Python