Re: Interface Inheritance Clarification

Cindy,

The use-case is multiple inheritence, for example, to mix in behavior. 
This requirement came from Grid.

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



"Cindy McNally" <cindymcnally_6@hotmail.com> 
Sent by: public-ws-desc-comments-request@w3.org
12/14/2006 09:50 AM

To
public-ws-desc-comments@w3.org
cc

Subject
Interface Inheritance Clarification







Hi,

I believe a clarification is waranted within part 1: core language re: 
interface inheritance.

The following sentence appears to imply that an interface inherits faults 
and operations from interfaces defined within the extends attribute AND 
from 
interfaces extended indirectly, i.e. interfaces defined within the extends 

attribute of extended interfaces, etc ...

"To avoid circular definitions, an interface MUST NOT appear as an element 

of the set of interfaces it extends, either directly or indirectly."

The next sentence, however, seems to imply that an interface inherits 
content only from the interfaces listed within its extends attribute:

"The set of operations available in an interface includes all the 
operations 
defined by the interfaces it extends, along with any operations it 
directly 
defines. "

If the first supposition is correct, then what is the use case for being 
able to list more than one extended interface within the extends 
attribute?

Please advise.  Thanks.

_________________________________________________________________
WIN up to $10,000 in cash or prizes ? enter the Microsoft Office Live 
Sweepstakes http://clk.atdmt.com/MRT/go/aub0050001581mrt/direct/01/