Re: CfC: Action name convention

Thank you very much. It is helpful for me.
I have looked through the list of intents which aggregates registry of android intents protocols. 
For web intents, I am just wondering if WebRTC is a common use case.
WebRTC is also a W3C spec (http://dev.w3.org/2011/webrtc/editor/webrtc.html) and in processing.
When there is a valid ID (e.g. telephone number, email) in a client page, user can click it to pick a WebRTC service page, then call remote peer. The function is similar to "android.intent.action.CALL", but the difference is that client page and service page both in the web browser.
Is it necessary to standardize this use case?

-----邮件原件-----
发件人: Friedger Müffke [mailto:friedger@gmail.com] 
发送时间: 2012年12月18日 18:18
收件人: Wangyahui
抄送: public-web-intents@w3.org
主题: Re: CfC: Action name convention

For Android intents, there is e.g. openintents.org. We have added a
column for Web Intents as well.

The most common use cases are supposed to be standardized (see media
gallery spec)

2012/12/18 Wangyahui <yahui.wang@huawei.com>:
> Hi all,
>
> I recently study the web intent spec, but I am confused about the action
> name.
>
> As I know, the client invokes intent by constructing an Intent object, and
> it contains requested Intent action and type. Then UA will match the action
> and type to find in the registrations of the Service page. However, If
> developers can define any new actions for service pages in their domains,
> how a client page can know these action names when it requests an Intent be
> handled?
>
> For example, I develop a web app which provides the service identified by a
> new action named” http://example.com/draw”. How can other developers know
> there is an action named ” http://example.com/draw”? Then they can add it to
> the intent object of client page.
>
> Shouldn’t it be standardized or managed by third party agent? Will the spec
> accept to add some other standard actions?
>
> I appreciate your any answer.
>
>
>
> Thanks and regards,
>
> Yahui
>
>

Received on Thursday, 20 December 2012 06:41:03 UTC