potentialAction for Classes?

Has there been any discussion around whether it would make sense to 
allow potential actions for all instances of a class, so that modelers 
don't need to repeat the same details over and over again? An example 
use case would be a page listing bugs in a bug tracker. Each bug would 
have an action to mark it as "resolved". If I understand the current 
design, the web page would need to include individual Action entries for 
each bug item, even if they differ with just a single ID. I believe it 
would be great if this information could be captured once, e.g. via a 
property "potentialInstanceAction" attached to the type of those bug 
items, where the urlTemplate is parameterized with a field from the 


Received on Wednesday, 21 May 2014 05:57:47 UTC