Re: [geclipse-dev] GRIA questions

["David Johnson" <d.johnson@xxxxxxxxxxxxx>]

2008/4/29 Stuempert, Mathias IWR <mathias.stuempert@xxxxxxxxxx>:
> > Can we not hide some functions of the standard from specific
>  middleware?
>
>  No we can't. What the editor gets is a .jsdl file. It does not know to
>  which middleware this JSDL will be submitted and it should not know.
>
>

Hi everyone - thought I might put my thoughts in here...

Actually I kind of see what Jie means here, and I ask the same
question, and here's why (Obviously I've not worked on the GRIA bits
as yet, so if I'm wrong I'm wrong here, but hopefully I'm not wrong)

For a particular types of jobs, we have previously discussed the fact
that in fact we do 'know' what middleware a JSDL might submit to.

Consider this: It has been discussed about removing the job submission
wizard page that allows a user to select whether it's a gLite job or a
GRIA job, as it very much depends if we have a gLite compatible VO, or
a GRIA VO anyway. So surely if we're using JSDL's in a GRIA VO, we
'know' it's a JSDL that will be submitted to GRIA, and we could
perhaps 'disable' certain JSDL fields since they will never ever apply
in that context.

In a GRIA VO we kind of 'disable' submitting to gLite (and vice
versa), so why not apply this logic in this case?