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

>  
> 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.. 

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.


- JK

Received on Friday, 17 May 2013 00:33:48 UTC