I'll start this discussion with a bold position. The term "resource" should be avoided entirely.
In English usage outside of modern computing platforms, the term is more commonly used in plural form.
What is a single "resource"? I believe "static scope" best describes this concept in the way we are using it.
In the spec meeting today, there was a question about how this relates to distributed context--I would call that dynamic scope.
There's a connection with programming languages, which use "lexical scope" and "dynamic scope" to describe these two kinds of scope.
If a "resource" can be a single cluster or a single rack or a single computer, then conceptually we shouldn't stop generalizing at the single process.
A resource can be a single shard, a single peer, a single vhost, ...