Issues found in spec:
The proposal adds the first/max parameters as used in the people requests.
This may conflict with the Portable contacts alignment, where I suspect that these will be renamed 'startIndex' and 'count'.
If we're going to add pagination for activities we should also add support for fields, sortOrder, fitlerBy, filterOp and filterValue. This consolidates much of the fetch logic for the different types of objects and seems to be the best way forward.
Suggested Modification
Refactor sort/pagination/filtering into it's own definition and apply this to fetching all forms of objects if possible. ... Or simply align with fetchPerson semantics and syntax.