- From: Cameron McCormack <cam@mcc.id.au>
- Date: Mon, 1 Dec 2008 11:12:13 +1100
- To: public-webapps@w3.org
Cameron McCormack:
> > OK. The hard coded prefix approach I suggested above would still have a
> > mechanism for overriding that. For example:
> >
> > module dom { interface Node { … }; };
> >
> > module svg { interface SVGElement : Element { … }; };
> >
> > [Prefix=org]
> > module acme { interace NiftyElement : Element { … }; };
> >
> > could result in interfaces org.w3c.dom.Node, org.w3c.dom.svg.SVGElement
> > and org.acme.NiftyElement. [Prefix] could take a scoped name, and then
> > language bindings other than Java could define how that module name with
> > the prefix is mapped to the namespacing mechanism of that languages
> > (changing to camel case, or whatever) if needed.
> >
> > Would that work for you (and Lachy)?
Kartikaya Gupta:
> Works for me.
Done:
http://dev.w3.org/2006/webapi/WebIDL/#idl-modules
http://dev.w3.org/2006/webapi/WebIDL/#Prefix
http://dev.w3.org/2006/webapi/WebIDL/#java-modules
--
Cameron McCormack ≝ http://mcc.id.au/
Received on Monday, 1 December 2008 00:13:04 UTC