This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4531 - [UPD] Section 2.4.1 and others: allow resolving namespace binding conflicts
Summary: [UPD] Section 2.4.1 and others: allow resolving namespace binding conflicts
Status: CLOSED WONTFIX
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Update Facility (show other bugs)
Version: Working drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Andrew Eisenberg
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-04 23:29 UTC by Michael Rys
Modified: 2008-05-15 19:42 UTC (History)
0 users

See Also:

Attachments

Description Michael Rys 2007-05-04 23:29:14 UTC 
"whose implied namespace binding conflicts" => should we allow implementations to resolve the conflicts instead, by creating a new prefix?
Comment 1 Liam R E Quin 2007-06-05 16:53:31 UTC 
The Working Group discussed this.  The suggestion adds complexity and reduces interoperability, and the WG decided not to make this change.
Comment 2 Michael Rys 2008-05-15 19:42:58 UTC 
While I accept the resolution, I think that creating a new prefix would not impact interoperability, since prefixes are not information-bearing according to the XML Namespaces and XML Infoset recommendations.