This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
6.5.3, target Why do you consider the possibility that [target] not be an NCName? This is required by the Namespaces spec. One might be able to create a synthetic infoset in which it were not true, but equally you could create one with an element whose [local name] was not an NCName, and you don't consider that case.
Resolved at Raleigh f2f: remove the paragraph.
(In reply to comment #1) The XML Core WG accepts your resolution of this comment.