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 2830 - RQ-157 Specify infoset fixups, or specify that they don't occur (infosetFixup)
Summary: RQ-157 Specify infoset fixups, or specify that they don't occur (infosetFixup)
Status: CLOSED DUPLICATE of bug 2105
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.1 only
Hardware: Other All
: P4 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard: important, work
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2006-02-11 00:57 UTC by C. M. Sperberg-McQueen
Modified: 2007-05-02 17:15 UTC (History)
0 users

See Also:


Attachments

Description C. M. Sperberg-McQueen 2006-02-11 00:57:51 UTC
This issue was originally reported by Jonathan Marsh.

Jonathan Marsh pointed out (March 2002
(http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2002Jan/0090.html))
that if a schema declares a default attribute with a qualfied name
(a:b="some value"), it appears that the PSVI does not fixup the
[in-scope namespaces] and [namespace attributes] properties.  It is
therefore possible for these attributes to get out of sync.

The issue was registered as issue R-114
(http://www.w3.org/2001/05/xmlschema-rec-comments.html#pfiInfoset).

After discussion, the Working Group decided
(http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2002Jan/0084.html)
to classify the clarification of this issue and the appropriate
behavior of schema processors as a requirement for 1.1.
Comment 1 C. M. Sperberg-McQueen 2006-10-09 20:57:58 UTC
See also bug 2105.
Comment 2 C. M. Sperberg-McQueen 2007-01-08 22:22:48 UTC
The issue identified here is the first of three issues raised by
Jonathan Marsh in his email of 24 January 2002. The first is recorded
in bug 2102 (for 1.0) and both this bug (bug 2830) and bug 2105 (for
1.1); the second in bug 2103 (for 1.0) and bug 2748 (for 1.1); the
third in bug 4159 (for both versions).
Comment 3 C. M. Sperberg-McQueen 2007-02-23 21:22:18 UTC
This issue appears to be an unintentional duplicate of 2105.
The substantive point has now been resolved by wording adopted
in today's WG call, so I am closing the issue.

*** This bug has been marked as a duplicate of bug 2105 ***