[ogsa-rss-wg] Candidate Ordering Language

[Arvid Norberg]

I was thinking about the proposed ordering language. In one of the
examples Donal posted:

>   <sum>
>     <product>
>       <value> //price/@value </value>
>       <constant> 42 </constant>
>     </product>
>     <power exponent="-0.5">
>       <!-- Assume that somewhere there's some JSDL -->
>       <value> //JobDescription/Resources/IndividualCPUCount </value>
>     </power>
>   </sum>

The documents those XPath queries are looking in wasn't really
discussed. I presume that document is supposed to describe the
properties of a particular resource (which is to be ranked).

The example suggests having a whole jsdl document, which I'm not
sure makes alot of sense. There's no Application, file staging
or project involved.

The Resources element (from the jsdl spec) on the other hand is
(probably) capable of describing all important properties of a
resource. It could even contain the name/URL of the BES in
Resources/CandidateHosts/HostName.

just my $0.02
--
Arvid Norberg