W3C home > Mailing lists > Public > www-ws-desc@w3.org > July 2006

CR022b: Testing for Component Equivalence

From: Arthur Ryman <ryman@ca.ibm.com>
Date: Thu, 20 Jul 2006 10:03:38 -0400
To: www-ws-desc@w3.org
Message-ID: <OF992488AD.6E948F6F-ON852571B1.004ACFF4-852571B1.004D5030@ca.ibm.com>
I am splitting CR022 into two separate issues: a) extension behavior wrt 
to <import> and <include>, and b) testing for component equivalent.

This note covers b).

I propose the following:

2.17.1 Testing for Component Equivalence

Components defined in WSDL 2.0 documents may refer to other components by 
key values. For example, the xs:QName valued interface attribute 
information item of a service element information item establishes a 
to-be-resolved reference from a Service component to an Interface 
component. In a valid component model instance, this key value reference 
resolves to an actual Interface component that has a {name} property with 
the corresponding xs:QName value. Note that in order to determine the 
validity of a component model instance it is sufficient to test components 
for equivalence by comparing their key value references to other 
components rather than recursing into the referenced components. If the 
referenced components are themselves inequivalent then the component model 
instance as a whole will be invalid. That is component equivalence modulo 
unresolved references is a weaker test but is sufficient for determining 
component model instance validity.



Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Received on Thursday, 20 July 2006 14:03:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:41 GMT