Is there more than the list of 5 basic activities that can be considered generic, I wonder? Perhaps it might make sense to describe what a generic server supports, in the form of Use Cases, in a similar way as the motivational use cases in the ActivityStreams vocubulary spec. Then for each use case a consistent pattern can be specified that MUST be implemented (either refer to AP spec if robustly defined there and/or add additional info on format, behavior, msg exchange).
1 Like