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 4431 - Definnition of equivalent value.
Summary: Definnition of equivalent value.
Status: CLOSED FIXED
Alias: None
Product: WSDL
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.0
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Arthur Ryman
QA Contact: WSDL Mailing List
URL: http://lists.w3.org/Archives/Member/w...
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2007-03-29 17:29 UTC by Jonathan Marsh
Modified: 2007-04-26 13:01 UTC (History)
0 users

See Also:


Attachments

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

Two component instances of the same type are considered equivalent if, for each property of the first component, there is a corresponding property with an equivalent value on the second component, and vice versa.

Instances of properties of the same type are considered equivalent if their values are equivalent.
]]

Re "property with an equivalent value", Should this not point instead to the rule in the next sentence?
Comment 1 Arthur Ryman 2007-04-15 21:44:16 UTC
Here is my proposed edit:

Two component instances of the same type are considered equivalent if, for each property of the first component, there is a corresponding property with an equivalent value, as defined in the following sentence, on the second component, and vice versa.
Comment 2 Jonathan Marsh 2007-04-19 15:29:24 UTC
"Two component instances of the same type are considered equivalent if, for
each property value of the first component, there is a corresponding property with an equivalent value on the second component, and vice versa."