- From: elf Pavlik <elf-pavlik@hackers4peace.net>
- Date: Wed, 3 May 2017 15:40:57 -0500
- To: 'Hydra' <public-hydra@w3.org>
Based on discussion which started in on of the PRs https://github.com/HydraCG/Specifications/pull/117#discussion_r114186138 I understand that we consider recommending using some subclasses of schema:Action as commonly recognized specific types of operations. I guess mostly * https://schema.org/CreateAction * https://schema.org/UpdateAction * https://schema.org/AddAction * https://schema.org/DeleteAction * https://schema.org/ReplaceAction IMO we could discuss it here + github and **possibly include as one of agenda points for the next telecon**. This relates to issue where started discussing long time ago, on how Actions on things other than web resources relate (translate) to Operations on relevant web resources. https://github.com/HydraCG/Specifications/issues/2 For example some Actions on things (non web) eg. * http://schema.org/FollowAction * http://schema.org/JoinAction Might not get used as Operation on the web resource describing that non web thing, but instead such Action would reference an Operation and different web resource to perform it on. For example 'add' Operation on collection of followers or 'add' Operation on collection of organization members etc. (both would expect IRI denoting a schema:Person) I don't think we need to address above Action (on now web thing) vs Operation (on web resource) just to suggest reusing few particular subclasses of schema.org/Action. At the same time once we suggest using some of schema.org actions, we may need to clarify later on various possible ways of handling other actions in schema.org Which reminds me of abandoned https://github.com/HydraCG/Specifications/tree/master/spec/latest/schema.org Cheers!
Received on Wednesday, 3 May 2017 20:41:38 UTC