Actions: properties, instances
Opening this issue to discuss in one place:
-
What additional actions are needed and/or what actions should be combined? In general, what is the sweet spot for definition of actions to get a balance of non-proliferation and enough semantic meaning to make them clear?
-
Right now we have actions defined as
rdf:Property
s and have set up a property inheritance structure to define decrement/increment. There are a number of other attributes that could be defined so that handling actions could be completely data driven, rather than hard coded.
There are some other ways to slice the above too. If we define 2), we could combine those into core behaviors, which could be referenced on actions, opening up the semantics to broader definitions, even user definitions. Or those core behaviors could be the actions, with less semantic meaning than we have now. And probably others.