It might be safest to represent the scope as a list. Sounds like a complete PITA to implement in a database, though. Maybe it'll be enough to just make sure that the only accessor for this field returns a list (or better yet a set), so callers can ask "is this desired scope in the set?" instead of doing string-matching that'll inevitably be vulnerable to some weird sort of confusing bug.