RE: Actions in Schema.org - Potential vs Performed Actions

Thanks for clarifying Charlie.

I noticed in that there is still an ActionStatus property but now it is on
ActionActivity, so how does it differ in solving Potential vs Performed
actions?

In schema.org, schemas are split into multiple types where there is
potential for many:1 or many:many relationships, or when there is potential
for re-use in other places. But here ActionActivity & Action will always go
hand in hand together, so why split into 2 types?


On Fri May 17 2013 at 5:29:25 PM, Charlie Jiang <chjiang@microsoft.com>
wrote:

>  This sure opens another set of problem to solve;-)****
>
> ** **
>
> What about: ****
>
> ** **
>
> ActionActity{****
>
>                 action: Action;****
>
>                 status: ActionStatus;****
>
>                 time: Time;****
>
>                 location: Location;****
>
> }****
>
> ** **
>
> In this way, general activity related attributes are in ActionActivity.
> Action specific “parameters” are in Action. Since in this way action is
> part of ActtionActivty, it is semantically clear that every attributes in
> that action (itemBought for example) are meant for the specific activity.*
> ***
>
>                 ****
>
> ** **
>
> *From:* Yaar Schnitman [mailto:yaar@google.com]
> *Sent:* Friday, May 17, 2013 4:32 PM
> *To:* Charlie Jiang
> *Cc:* Jim Klo; public-vocabs@w3.org; Steve Macbeth; Dan Brickley
>
>
> *Subject:* Re: Actions in Schema.org - Potential vs Performed Actions****
>
> ** **
>
> Hi Charlie,****
>
> ** **
>
> Do you suggest that every possible action (e.g. Buy) will have 2
> corresponding types (e.g. BuyAction and BuyActivity)? Do all the properties
> (e.g. itemBought) have to be duplicated on both?****
>
> ** **
>
> -Yaar****
>
> ** **
>
> On Fri, May 17, 2013 at 3:46 PM, Charlie Jiang <chjiang@microsoft.com>
> wrote:****
>
>  Default to “Tentative” makes more sense here. The caveat is “tentative”
> is hardly qualify for a value of status.****
>
>  ****
>
> What we are actually doing here is to try to work around complications
> introduced by over loading Action for both ActionActivity and ActionType
> using the status attribute. If we separate them, tentativeAction should be
> of ActionType whereas perfomedAction should be of ActionActivity (which has
> a status attribute).****
>
>  ****
>
> *From:* Yaar Schnitman [mailto:yaar@google.com]
> *Sent:* Thursday, May 16, 2013 6:26 PM
> *To:* Jim Klo
> *Cc:* public-vocabs@w3.org; Steve Macbeth; Dan Brickley
> *Subject:* Re: Actions in Schema.org - Potential vs Performed Actions****
>
>  ****
>
>  ****
>
>  ****
>
> On Thu, May 16, 2013 at 5:33 PM, Jim Klo <jim.klo@sri.com> wrote:****
>
>  >
> > I don't know if Action.status would be less likely to be omitted when
> the Action is the primary element. I think search engines / user agents
> should standardize what the default is in such case. I think its should be
> "Performed". I'll add that to the draft.****
>
> Hmm… this seems like it would be tough constraint to determine… and a
> context sensitive default value seems dangerous. I was thinking it should
> always default to "Tentative" unless the property specifies otherwise, such
> as the case of Thing.potentialAction / Thing.performedAction.  I only
> mention this because if the context of the instance changes and is missing
> explicit status (consider re-aggregated content as the example, site B
> slurps content from site A), the default value could change if site B
> nested the contents of site A inside some Thing (I think "edge case"  for
> sure).   The only way I can kind of rationalize a "Performed" as a default
> when primary object, "Tentative" otherwise is when describing sub-actions:
> Action.action.action.action… Where the parent needs to be "Performed"
> before the "sub-task" is tentative, still feels like screwy logic.. ****
>
>  Default=tentative makes sense too. ****
>
>
> I'm guessing most indexed pages will have actions that are usually
> "potential" as opposed to "performed", but would think you guys would
> probably have a better handle on the "characteristic" of the available data
> set than myself. ****
>
>  Its hard to predict. Every "potential" action in an email or a webpage
> will have a corresponding email or a webpage that confirms the action was
> performed.****
>
>  ****
>
>
>
> - JK****
>
>   ****
>
>  ** **
>