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 6171 - anyAttribute namespace="xsi"
Summary: anyAttribute namespace="xsi"
Status: CLOSED WORKSFORME
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.1 only
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-20 14:35 UTC by Michael Kay
Modified: 2008-10-30 10:36 UTC (History)
0 users

See Also:


Attachments

Description Michael Kay 2008-10-20 14:35:04 UTC
We have a rule that prevents attribute declarations in the XSI namespace, other than the four standard attributes defined in the spec.

In the same spirit of paternalism, would it be appropriate to ban attribute wildcards that permit the appearance of names other than these four in the XSI namespace? There seems little point in locking the front door and leaving the back door open, even if there's not much in the house worth stealing.
Comment 1 C. M. Sperberg-McQueen 2008-10-29 18:39:36 UTC
We discussed this at the ftf today.  The current behavior of the spec seems
to those present well defined, if perhaps (as pointed out in the bug
description) a bit quirky.  A simple implementation of the proposal would
apparently outlaw <xsd:any/>, which would be unfortunate; we infer that a
realistic implementation would be more complicated (and error prone); in
view of the fact that nothing seems to be actually broken, we decided to
class this as WORKSFORME.  

Some of those present preferred to avoid paternalism and all its works
in the first place, but that was not the consensus rationale.