Technically, a subscription is a 'request' for information that is based on a 'definition' (Topic) and satisfied by an 'event' (Status).  SubscriptionTopic is already defined as a definition.  However, the event and request resources are not mapped to the pattern.  They're also quite different from most of the resources that implement the workflow patterns.  Is there value in providing the mappings?