I got carried away and included some proposed wording to this effect in version 18. E.g.:

----------
The OGSA-BES Working Group also had to deal with the lack of community consensus on how to model information describing stateful entities (or, as they
 are often termed, resources), which in the case of BES comprise containers and activities. Thus, this BES specification is structured in two parts: (
1) the main body of the proposal, which describes the capabilities to be provided by a BES implementation, without specifying Web Service interfaces, 
and (2) appendices, which describe alternative renderings of these capabilities in terms of specific resource models. Two such renderings are defined 
in this document:

* A "Web Services Resource Framework" (WSRF) rendering, which models resources in terms of abstractions and interfaces defined in the WSRF [WSRF] and 
WS-Notification [WS-N] specifications. Thus, container and activity state is modeled as resource properties that can be accessed via WSRF and WS-
Notification interfaces.

* A "Resource Model Free" (RMF) rendering, which does not adopt any conventional modeling of BES resources but instead adopts BES-specific operations 
for retrieving container and activity state, requesting notification of changes in state, and so on.
-------------