Hi; I totally agree. You make a very important point. That said, the simplest common case to define may be an array of available resources. Specifying richer policy restrictions can quickly lead down the slippery slope to very complicated, very difficult-to-provide designs and hence must be done with great care. Marvin. -----Original Message----- From: Karl Czajkowski [mailto:karlcz@univa.com] Sent: Friday, June 09, 2006 3:08 AM To: Donal K. Fellows Cc: Marvin Theimer; JSDL Working Group; ogsa-bes-wg@ggf.org; Ed Lassettre; Ming Xu (WINDOWS) Subject: Re: [jsdl-wg] Questions and potential changes to JSDL, as seen from HPC Profile point-of-view One thing Donal mentioned which I would like to emphasize: The discovery ought to be "what types of job are acceptable" and not what resources are there. Or rather, the latter is part of some administrative interface which is misleading for job-submitting users and middleware. This may sound pedantic, but it will be crucial for interop. The discovery has to capture realistic operating policy, and not just give enticing catalogues of resources which can never be combined in a single request! karl -- Karl Czajkowski karlcz@univa.com