[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Namespaces, schemas, Simon's filters.

• From: Peter Piatko <piatko@r...>
• To: Ronald Bourret <rpbourret@r...>, xml-dev@l...
• Date: Sat, 25 Aug 2001 08:39:44 -0400

The non-normative part of the Namespace rec seems to agree with you [1] (The
"title" refered to here is an attribute):

"...In this example, there are three occurrences of the name title within
markup, and the name alone clearly provides insufficient information to
allow correct processing by a software module."

The implication of this sentence is that the type and the identifier should
have a 1-1 mapping.

I think it is pretty clear that the syntactic sugar of the Namespace rec
doesn't handle hierarchies all that well, and that Per-Element-Type
partitions introduce such hierarchies (of at least one level anyway).  So I
feel that the options are (a) enhance the syntax or (b) simplify (i.e.
flatten) the interpretation of what namespaces are.  The current situation
is just confusing.

Option (b) implies that an identifier might map to multiple types.  I think
the question boils down whether this ok or not.

Thanks,

Peter

[1] http://www.w3.org/TR/1999/REC-xml-names-19990114/#sets-no-good

----- Original Message -----
From: "Ronald Bourret" <rpbourret@r...>
To: <xml-dev@l...>
Sent: Saturday, August 25, 2001 4:02 AM
Subject: Re: Namespaces, schemas, Simon's filters.


> Peter Piatko wrote:
> > What was the problem with the simpler interpretation that unqualified
> > attributes were in the same namespace as their containing element?  Then
> > there would be no need for Per-Element-Type partitions at all (and hence
the
> > confusion of unqualified local elements).
>
> Without the per-element-type partitions, you can have one name referring
> to two different attributes, possible with different types, such as the
> foo attribute on elements bar and baz. This is certainly possible, but
> seems to negate the whole point of having namespaces (unless I'm missing
> something).
>
> -- Ron
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
>
>

• Follow-Ups:
  • Re: Namespaces, schemas, Simon's filters.
    • From: Evan Lenz <elenz@x...>
  • Re: Namespaces, schemas, Simon's filters.
    • From: Evan Lenz <elenz@x...>
  • Re: Namespaces, schemas, Simon's filters.
    • From: Ronald Bourret <rpbourret@r...>

• References:
  • Re: Namespaces, schemas, Simon's filters.
    • From: Ronald Bourret <rpbourret@r...>
  • RE: Namespaces, schemas, Simon's filters.
    • From: Tim Bray <tbray@t...>
  • Re: Namespaces, schemas, Simon's filters.
    • From: Peter Piatko <piatko@r...>
  • Re: Namespaces, schemas, Simon's filters.
    • From: Ronald Bourret <rpbourret@r...>

• Prev by Date: Out of the office
• Next by Date: Re: Namespaces, schemas, Simon's filters.
• Previous by thread: Re: Namespaces, schemas, Simon's filters.
• Next by thread: Re: Namespaces, schemas, Simon's filters.
• Index(es):
  • Date
  • Thread