I know this has already been changed based on comments from @fugu13 , but this doesn't read quite right either. This is an LMS requirement, but that's not clear -- I could very well see reading this to indicate that I can't use the same key in different ways for different agents and activities, when in fact I can. Other specifications that use Tin Can may (will) specify particular meanings for keys to be used across these scopes, but the only requirements we should be laying out here are that the LRS state resource won't mix up what's stored under say "bookmark" for one agent-activity combo with what's stored for another agent-activity combo.