xml-dev - RE: Varying the attlist for an element depending on the element's parent

[Andrew Layman <andrewl@microsoft.com>]

The paragraph quoted below beginning "Each Type..." is intended only to
describe scoping of attribute names matching the scoping expressed in DTDs
today.  That is, it simply says that the (unqualified) attlist for distinct
elements types is distinct; that the unqualified attribute types of distinct
element types are distinct.  

The namespaces proposal serves only to provide a mechanism for making names
universally identifyable by associating them with Universal Resource
Identifiers.  It is silent on any possible or speculative facilities for
defining syntax or semantics.

-----Original Message-----
From: james anderson [mailto:James.Anderson@mecomnet.de]
Sent: Sunday, December 06, 1998 7:37 AM
To: XML Dev
Subject: Re: Varying the attlist for an element depending on the
element's parent


i note that the xml-names-19980916 draft leave some room for hope that this
might become possible.

presume, for the sake of argument, that the standard eventually attends to
prefix/namespace bindings within the dtd.

in that event, the clause on "The Per-Element-Type Partitions" in appendix
A.2
describes the distinct names which could identify such attributes:

"Each type in the All Element Types Partition has an associated namespace in
which appear the names of the unqualified attributes that are provided for
that element. This is a traditional namespace because the appearance of
duplicate attribute names on an element is forbidden by XML 1.0. The
combination of the attribute name with the element's type and namespace name
uniquely identifies each unqualified attribute."

it would remain only to establish namespace scoping rules for an ATTLIST
form
similar to those for the element instances in order to to be able to
differentiate identity among the encoded attribute names.

Eric A. Stephens wrote:
> 
> After re-reading the spec last night it became (more) apparent that
> something like this would be the case.
> 
> Thanks.
> 
> On Thu, 3 Dec 1998, John Cowan wrote:
> 
> > Eric A. Stephens scripsit:
> >
> > > What I'm looking to do is have different ATTLIST defs for the element
TYPE
> > > depending on the element that TYPE is contained within.
> >
> > In a word, XML validation can't do it.  You have to declare the
> > attribute list definitions to be a union of the two cases, and
> > depend on hand-rolled validation inside the application to do the
> > job.


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following
message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)