- From: Paul Kinlan <paulkinlan@google.com>
- Date: Fri, 1 Jun 2012 18:12:24 +0100
- To: KOMATSU Kensaku <kensaku.komatsu@gmail.com>
- Cc: "public-web-intents@w3.org" <public-web-intents@w3.org>
- Message-ID: <CADGdg3AaNcDaVXp8mQNHXLf68bd7aQqobaFrRm71umYLr6mNww@mail.gmail.com>
The original thought was that the url in the action SHOULD point to the detailed documetation/specification for the usage of that action and data. I think we all strongly agree that they should be specified and documented much more comprehensively than they have now under "webintents.org/*" My question is for all types that are under the namespace http://webintents.org/ do you want the process to be managed by the W3C under this group? or outside? P On Fri, Jun 1, 2012 at 5:30 PM, KOMATSU Kensaku <kensaku.komatsu@gmail.com>wrote: > Claes, > > I like your idea considering the standardization process for specific > combinations. I also agree that to make > interoperability better your proposal will be helpful. > > I want to clarify your idea. My opinion is that some combinations such as > Gallery or Contacts should > be standardized but everything should not be. I think there should be > sandbox spaces for some > Action and Types pair (and it should be documented in schema url). Anyway, > to list the candidates for > it is nice idea, I presume. It'll be helpful for developers who want to > make use of WebIntents. > > 2012/6/2 Nilsson, Claes1 <Claes1.Nilsson@sonymobile.com> > > Hi,**** >> >> ** ** >> >> To achieve interoperability between Client applications and Service >> applications Web Intents based APIs need to be specified. I assume that the >> combination of Action and Type enables a specified API to be used for >> interaction between Client and Service. So this has to be standardized.** >> ** >> >> ** ** >> >> It seems that this is an area where still a lot have to be done. I have >> only seen one tangible proposal for a Web Intents based API submitted to >> W3C, that is the Gallery API, >> https://dvcs.w3.org/hg/dap/raw-file/16185b62381d/gallery/index.html. >> Robin has also posted thoughts on a Web Intents based Contacts API, >> http://www.w3.org/wiki/WebIntents/ContactsAPI.**** >> >> ** ** >> >> I wonder if people on this list know of more tangible proposals for Web >> Intents based APIs than the two mentioned above? Which are your thoughts on >> driving the standardization on Web Intents based API further?**** >> >> ** ** >> >> This is essential in order to succeed with Web Intents.**** >> >> ** ** >> >> Best regards**** >> >> Claes**** >> >> ** ** >> >> ** ** >> >> [image: cid:3333625383_1036728] >> >> *Claes Nilsson M.Sc.E.E* >> Master Engineer, Research >> Technology Research - Advanced Application Lab >> * >> Sony Mobile Communications* >> Phone: +46 10 80 15178 >> Mobile: +46 705 56 68 78 >> Switchboard: +46 10 80 00000 >> E-Mail:* **mailto:claes1.nilsson@sonymobile.com<claes1.nilsson@sonyericsson.com> >> * >> Visiting Address; Nya Vattentornet >> SE-221 88 LUND, >> Sweden **** >> >> *Disclaimer: >> *The information in this e-mail is confidential and may be legally >> privileged. It is intended solely for the named recipient(s) and access to >> this e-mail by anyone else is unauthorized. The views are those of the >> sender and not necessarily the views of Sony Ericsson and Sony Ericsson >> accepts no responsibility or liability whatsoever or howsoever arising in >> connection with this e-mail.Any attachment(s) to this message has been >> checked for viruses, but please rely on your own virus checker and >> procedures. If you contact us by e-mail, we will store your name and >> address to facilitate communications. If you are not the intended >> recipient, please inform the sender by replying this transmission and >> delete the e-mail and any copies of it without disclosing it.**** >> >> **** >> >> ** ** >> > > -- Paul Kinlan Developer Advocate @ Google for Chrome and HTML5 G+: http://plus.ly/paul.kinlan t: +447730517944 tw: @Paul_Kinlan LinkedIn: http://uk.linkedin.com/in/paulkinlan Blog: http://paul.kinlan.me Skype: paul.kinlan
Attachments
- image/gif attachment: image001.gif
Received on Friday, 1 June 2012 17:12:54 UTC