Good question. Too many of these contexts simply came directly out of the old impl. My way of asking the question is: in what context (larger sense of the word) would we want to supply those triples? My first thought is-- you might very well want them when you are _not_ in the context of examining a given node, so they're not from a NodeRdfContext at all and therefore certainly don't belong here. (There are many other triples being generated here that don't belong here, by the same logic, but I was trying to get something out the door.)

There are other contexts (e.g. NamespacesRdfContext) that aren't associated to a give Node. That's the right pattern, for my money. So we could have a WorkspacesRdfContext and that seems to me to be best. If we can find a larger abstraction that really makes sense, we can factor NamespacesRdfContext and a hypothetical WorkspacesRdfContext through it. Maybe RepositoryRdfContext?