[
Lists Home |
Date Index |
Thread Index
]
- From: "David Brownell" <david-b@pacbell.net>
- To: "Clark C. Evans" <cce@clarkevans.com>, "John Cowan" <jcowan@reutershealth.com>
- Date: Wed, 24 May 2000 21:10:51 +0200
Incorrect. The notion of a per-element context only
exists in a non-normative section, ergo it has no
force. I'm not even sure it was a Bright Idea (tm)
The only fully standardized name structures are the
tuple { URI, LocalName } and the original { Name },
with the latter applying to attribute names without
prefix and to element names where "xmlns=''" applies.
Except that some folk seem to disagree about the URI
bit ... sigh. This is proof, if anyone lacked it,
that the W3C's ability (and in this case, desire) to
rush a spec through in just a few months, without a
full and transparent discussion, is detrimental to
the public interest in stable WWW infrastructure.
- Dave
----- Original Message -----
From: Clark C. Evans <cce@clarkevans.com>
To: John Cowan <jcowan@reutershealth.com>
Cc: <xml-dev@xml.org>
Sent: Friday, May 19, 2000 8:53 PM
Subject: Re: XLink a special case in the self-describing Web?
> On Fri, 19 May 2000, John Cowan wrote:
> > That is correct as stated, but it reflects a misconception. Namespaces
> > provide nothing but a superficial mapping of GIs and attribute names
into
> > so-called "universal names", which are simply an ordered pair of the
> > form {string, Name} where "string" has the syntax of a URI. The
SGML/XML
> > semantic model is unchanged.
>
> Just for reference.. (please correct me if I'm wrong)
>
> The { string, Name } model of namespaces is what
> XPath specification uses. The namespace spec uses
> a 4-tuple { type, string, parent-local, local }
> where type is "element" or "global-attribute"
> or "per-element-attribute" and where parent-local
> is null except for the "per-element-attribute",
> in which case, it is the parent element's local.
>
> Clark
>
>
***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************
|