Are there any plans to add other flavors of ##other? The original definition of ##other allowed for unqualified attributes to match it, and now ##other has been "clarified" to require namespace-qualified attributes. Certainly there are use cases for both flavors of ##other, as well as another issue that I have mentioned to Henry Thompson awhile ago (which he said was a requirement under consideration) which was a version of wildcards with ##other that allowed for elements in the same namespace as the target schema other than those otherwise declared in the current content model. There are clearly a number of different flavors of ##other that do not require weakening the Unique Particle Attribution constraint that are very useful. Currently, we are having backwards-compatibility problems since the assumption that unqualified namespaces would match ##other is no longer valid, and we have to migration strategy so that we can change schemas appropriately to keep the original assumption valid. I don't think the E0-10 errata tightening the documents that validate with wildcards using ##other should be published without a mechanism to address backwards compatibility. --Eric Sedlar Oracle CorporationReceived on Monday, 2 June 2003 16:53:39 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 6 December 2009 18:13:02 GMT