expect contention
suggested maybe additional examples covering faculty, staff members?
should be SP specific for each eduPersonEntitlement; in practice, it's unlikely you'll be able to avoid doing that. The dominant use case is that roles and privs do not overlap between services. It's easier to start with unique and work backwards to shared; every new service will be considered unique to start, and Grouper is often used to facilitate when there are common policies behind those entitlements
It would be nice to have a research project as a use case (if we can find one that's willing to be shared)
Maybe be worth noting that issues with categorizing entitlements is similar to issues with categorizing affiliation; should use some more text there.
This is ready for consultation