- From: Yaar Schnitman <yaar@google.com>
- Date: Thu, 16 May 2013 12:18:04 -0700
- To: public-vocabs@w3.org, jim.klo@sri.com, Steve Macbeth <Steve.Macbeth@microsoft.com>, Dan Brickley <danbri@google.com>
Received on Friday, 17 May 2013 10:18:29 UTC
Jim, your raised the issed that "potential" actions and "performed" actions on a Thing are hard to distinguish. The proposal suggests using the Action.status property just for that, and specifies that the Thing.action should be for "potential" actions only. You are right however that the status might be omitted and the action property misused, leading to ambiguity. I think that one simple solution for that would be to have instead two properties on Thing: * Thing.potentialAction (or tentativeAction, to match with the corresponding ActionStatus value) - an action that can be potentially performed on the Thing. Repeated values will mean that multiple actions are supported. * Thing.performedAction - an action that was performed on the Thing in the past. Repeated values will form an "activity stream" for the Thing. What do you think? -Yaar
Received on Friday, 17 May 2013 10:18:29 UTC