Application Role
Application Roles reflect business roles. Application Roles represent groupings of functionality that an application can do. This includes Interactions an application can send, as well as interactions it can receive. In effect this means that one and the same interaction can be used by different application roles.
Application Roles will form the basis for a suite of Conformance Claims, in the same manner as was originally documented in the Version 3 Statement of Principles.
If simple stereotype roles are used these may use the stereotype names Placer, Fulfiller, Informer and Tracker. (Note: and shall not use confirmer and confirmation tracker as these tend to confuse people).
Discission
The answer to “what are the business application roles” is in the heads and in the implementation specifications of the many experienced (V2) implementers and implementations. We need to tap into what has already been done – not the V2 standard, but how it is implemented by most V2ers most of the time. This is how we define “application roles” in the real world all the time.
The domain committees will have to use this experience and include business role based application roles (even if only as informative material) in their ballot material. In cycles subsequent to the initial ballot, the committees will define specific specializations or instantiations of the generic application roles defined above.