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 1790 - [FS] technical: normalization rules "not required"
Summary: [FS] technical: normalization rules "not required"
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Last Call drafts
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Jerome Simeon
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-20 20:47 UTC by Michael Dyck
Modified: 2005-09-27 08:42 UTC (History)
0 users

See Also:


Attachments

Description Michael Dyck 2005-07-20 20:47:27 UTC
Various sections
    4.1.1 Literals
    4.1.2 Variable References
    5.4 Default Collation Declaration
    5.6 Construction Declaration
    5.10 Schema Import
    5.12 Namespace Declaration
    5.13 Default Namespace Declaration
say something like:
    All X are Core expressions, therefore no normalization rules are
    required for X.

I disagree that they are not required. The normalization of 'higher-level'
constructs (e.g., an Expr, or a PrologDeclList) depends on (is defined in
terms of) the normalization of its sub-constructs.  If you don't provide a
mapping rule for the sub-construct, then that normalization isn't defined,
and the higher-level normalization fails.

No big deal, just replace the above wording with:
    [[ X ]]_whatever == X

Note that some sections *do* supply identity normalization rules, e.g.:
    4.2.1.1 / Norm  (under "all other forward/reverse axes")
    4.7.1 / Norm / rule (6|7)
    5.15 / Notation / rule 2

(This is a leftover from 3 years ago. See attached URL.)
Comment 1 Jerome Simeon 2005-07-20 21:35:18 UTC
The working group aggrees with you. We will add the identity normalization rules
for the cases you mention.
- Jerome