Well spotted. I agree: "activity" (hence activitySpecification) - we sometimes use the concept "(work)task" (as used in our Click Software) in our company - should be in.
Not sure, I can be wrong but I think I am missing some characteristics - char/val possibility - on this activity or work item.
Are there any commercial companies involved (Netcracker, Salesforce/Click Software, Oracle,...)?
As work is often created from the fulfilment / technical provisioning process as well as from the servicing/repair process, it might be wise for the use cases to make a link to these.
There's a link to an order (in our SID model & in the current beta API) but not to a repair/incident case or ticket I think (as such not a big deal as both are business interactions, but maybe we could model it more generically or put both links in)?
We are looking into this TMF697 as a candidate for a new implementation but there is of course the risk that this is still too beta (read = first one to try out..) - any idea when the first draft version of the user guide would be ready @Pierre Robitaille ?