Hi, We decided in the F2F in London to use JSDL as a set of properties for BES, and some people decided to look into CIM as a possibility. The initial results of this work are in the attached spreadsheet. The three columns on the left are the JSDL elements, and the following two ones are the corresponding CIM classes and properties. (BTW, there seem to be several glitches on the GGF mailing lists, and apparently Andrea's e-mails which had this spreadsheet didn't reach this mailing list). Our conclusion for now is that by using a number of CIM classes and associations, with some extensions, we can represent what is in JSDL, both for the status of the container and activities and also the requirements submitted as a JSDL document. So, this CIM subset is suitable to use as a model for BES. (Notice that I'm talking about the model semantics only -- how you represent this on Web services is a different issue, which we will tackle later). The discussions we had the two RM design team teleconferences were quite interesting, with for instance discussions on how the JSDL entities map to the container and activities. Working on the resource model will help clarifying the semantics of the BES entities. Andrew, please add a discussion on the model to the next OGSA-BES teleconference (in case we are having one). Regards, Fred Maciel Hitachi America R&D