Re: attr() construct in generated content and namespaces

L. David Baron wrote:
> I think the general principle there is that you should need to use namespaces in
> order to end up with any of the others (either through the namespace
> awareness described in css3-namespace or through attr(xlink\:type) in
> non-namespace-aware CSS).

Excellent; that makes sense.  One niggling point.  What about the 
rendering of:

<div xmlns:xlink="whatever"
      xmlns:myNS="somethingElse"
      xlink:type="convoluted"
      myNS:type="confusing"
      type="confounding" />

styled with:

div::before { content: attr(*|type) }

?  Should that be considered an error causing the declaration to be dropped?