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 4432 - Equivlance based on lexical equivlaence or value equivalence?
Summary: Equivlance based on lexical equivlaence or value equivalence?
Status: RESOLVED FIXED
Alias: None
Product: WSDL
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.0
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Philippe Le Hegaret
QA Contact: WSDL Mailing List
URL: http://lists.w3.org/Archives/Member/w...
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2007-03-29 17:30 UTC by Jonathan Marsh
Modified: 2007-04-12 16:26 UTC (History)
0 users

See Also:

Attachments

Description Jonathan Marsh 2007-03-29 17:30:55 UTC 
[[
2.15 Equivalence of Components

* For values of a simple type (see 2.14 XML Schema 1.0 Simple Types Used in the Component Model), this means that they contain the exact same values. For instance, two string values are equivalent if they contain the same sequence of Unicode characters, as described in [Character Model for the WWW]
]]

Should we not be talking about value-space equivalence rather than strict lexical-space equivalent? For instance, 1 and true would not be equivalent according to this definition, whereas they would according to the XML Infoset.
Comment 1 Jonathan Marsh 2007-04-12 16:26:23 UTC 
Strike the word "exact", add the boolean example to the "for instance".