W3C home > Mailing lists > Public > public-web-intents@w3.org > July 2012

Re: Local Discovery addendum update for mDNS

From: Rich Tibbett <richt@opera.com>
Date: Fri, 27 Jul 2012 16:32:41 +0200
Message-ID: <5012A689.8060206@opera.com>
To: "public-web-intents@w3.org" <public-web-intents@w3.org>
Norifumi Kikkawa wrote:
> Claes and I updated the addendum to support mDNS.
> http://w3c-test.org/dap/wi-addendum-local-services/
> The basic idea is same as that for UPnP. The discovery protocol is used
> to obtain the location of the WebIntents page.

I haven't gone through the proposal in detail just yet but my 
understanding at this point is that it essentially provides a way to 
bootstrap the registration of standard Web Intents Providers via common 
discovery protocols (mDNS/DNS-SD and SSDP).

As I mentioned at the F2F a couple of weeks ago I think that there is a 
big opportunity here to re-use the mDNS/DNS-SD parts of this spec to be 
able to bootstrap the registration of Web Intents providers from 
wide-area networks i.e. the web.

The UA (though probably not individual web pages) could query the root 
DNS record of e.g. 'google.com' (by setting the mDNS search domain to 
'.google.com') and then register any and all web intent services that 
are included therein automatically in the UA.

It means that as a user navigates different domains on the web the UA 
itself could simultaneously and orthogonally make a query for Web Intent 
service records included in that domain's root DNS record (according to 
the format defined in this spec) and register those Web Intents in the 
UA for future invocation by any web pages.

It would be an alternative (bootstrap) mechanism for registering web 
intent providers and it could be complimentary to both the programmatic 
and declarative way to register Web Intents that we have now. In some 
ways it may be even cleaner than the other registration methods since 
there is only ever one single authorative record of the Web Intents that 
any given domain provides (in the domain's root DNS record). That avoids 
the issue of different web pages on the same domain potentially 
contradicting each other wrt the Web Intent Providers available on the 

I'm wondering if it's worth discussing this further here, if you have 
had any thoughts in this general direction and if it's something we 
might want to cover in this specification or elsewhere.

Would be good to get input on having this type of bootstrap registration 
process for Web Intents.

br/ Rich
Received on Friday, 27 July 2012 14:33:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:14:47 UTC