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 1597 - [FS] editorial: 4.5.1 Value Comparisons
Summary: [FS] editorial: 4.5.1 Value Comparisons
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 minor
Target Milestone: ---
Assignee: Jerome Simeon
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-14 23:22 UTC by Michael Dyck
Modified: 2007-02-25 23:14 UTC (History)
0 users

See Also:

Attachments

Description Michael Dyck 2005-07-14 23:22:01 UTC 
4.5.1 Value Comparisons

Notation
Table
    Maybe italicize 'ValueOp' in table headers (as in 4.4 & 4.5.2).

Table +
Norm / rule 1
    Why introduce the symbol 'ValueOp', when the non-terminal 'ValueComp'
    already means exactly that?
    (Personally, I think 'Op' is a better suffix than 'Comp', so I'd
    rather you renamed ValueComp to ValueOp than vice versa. But in any
    case, you only need one symbol.)
Comment 1 Mary Fernandez 2006-04-11 19:46:06 UTC 
Fixed as suggested.
Comment 2 Michael Dyck 2006-09-05 03:04:46 UTC 
The fixes do not appear in the 2006-06 CR.
Comment 3 Jerome Simeon 2007-01-16 17:55:00 UTC 
Replaced ValueOp by ValueComp.

- Jerome