[ogsa-hpcp-wg] Type for file elements in HPC Profile Application extension

[Christopher Smith]

During the HPC Profile working group session yesterday (after JSDL session
1), Mark Morgan expressed an opinion that the file elements for
input/output/error should be left as strings rather than changed to anyURI.
The idea is that either the back end system accepts the string, or doesn't,
and we don't put any constraints on the format. The description of those
elements would then contain some statement that the implementation should
return a particular kind of fault if it doesn't accept the provided string.

I tend to like this approach purely from the laziness position that I don't
have to craft some statements about exactly which formats are supported,
blah, blah, blah. Mark also mentioned that it greatly eases implementation.
There are some downsides from the interop point of view, but I think those
exist anyway, as some systems might support some form of URIs, whereas
others would not, etc, etc.

So ... I would like to propose to keep the type of these elements as a
string. 

Comments? 

Mark ... please chime in if I've misrepresented you in any way.

-- Chris