W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2013

Re: [WebIDL] Definition of "single operation interface" questions

From: Cameron McCormack <cam@mcc.id.au>
Date: Fri, 02 Aug 2013 14:32:31 +1000
Message-ID: <51FB365F.1030907@mcc.id.au>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: "public-script-coord@w3.org" <public-script-coord@w3.org>
Boris Zbarsky wrote:
> I have a few questions about the definition of "single operation
> interface" at
> http://dev.w3.org/2006/webapi/WebIDL/#dfn-single-operation-interface :
> 1) Given that
> http://dev.w3.org/2006/webapi/WebIDL/#dfn-callback-interface says:
> Callback interfaces MUST NOT have any have any consequential
> interfaces
> why is the second item in the bullet list needed?

I guess it's not, if I change the definition to "single operation 
callback interface".


> 2) Should static attributes prevent an interface from being a single
> operation interface? It's not obvious to me why, but per spec
> right now they do.

Static attributes (and operations) shouldn't be allowed on callback 
interfaces at all.


> 3) The "no others" in the last bullet point is ambiguous: does it
> mean "no other regular operations" or "no other operations"?
> This is related to item #2 above, of course.

Now that static operations are disallowed, the ambiguity should be resolved.
Received on Friday, 2 August 2013 04:33:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:17 UTC