- From: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- Date: Mon, 06 Oct 2014 21:48:28 +0200
- To: "public-vocabs@w3.org" <public-vocabs@w3.org>
Howdy, While tweaking some schema:Action examples I've noticed inconsistent way of referring to what I would call a WebService. * http://schema.org/OrderAction gives Amazon type schema:Product * http://schema.org/IgnoreAction gives social.com type schema:WebPage * http://schema.org/BookmarkAction gives Instagram type schema:Product * http://schema.org/CheckInAction gives aa.com type schema:WebApplication * http://schema.org/FollowAction gives Twitter type schema:Product My first thought was to change them all to schema:WebApplication which I added to TODO checklist in https://github.com/danbri/schemaorg/pull/15 But in my recent work which heavily focuses on Cross Origin Resource Sharing[1], decoupled interfaces [2] and unhosted web apps [3] I see *fundamental difference* between an App and Service. For me an App runs on device *locally* and can interact with *any number of remote* Services. Also Twiter, Instagram, Amazon etc. fit for me more as sub type of http://schema.org/Service People can already use all kind of Apps to use those Services. +/-1 for Thing > Intangible > Service > WebService ? Which could add among other properties termsOfService - https://tosdr.org/ (BTW also unhosted.org spin-off) http://schema.org/WebApplication has stuff like downloadUrl, screenshot etc. which fits what I would consider an App :) Cheers! [1] http://enable-cors.org/ [2] http://decoupledcms.org/ [3] https://unhosted.org/
Received on Monday, 6 October 2014 19:50:41 UTC