Quoting [Steve Fisher] (Apr 16 2009):
Also, the glite adaptor is free to define the schema glite://, and translate that internally to ldap://. We do that, for example, with gridftp, which is translated to gsiftp. Also, we do that for ssh:// URLs, which are translated into local file URLS (for sshfs mounted file systems).
I think that SAGA adapters should not require changes to the underlying middleware so I don't like this idea.
The change (i.e. URL translation) is in the adaptor, not in the middleware. the middleware is not touched. I completely agree that this would be a NO-NO.
I am not saying that you should not remove the URL - just want to make sure I understand why the URL is a problem, really.
Having had this discussion I now feel that the problem with the SD is not serious however making proper use of the returned URLs is a problem for all the other SAGA components. It is however an implementation problem so I will move it to the developers list.
agree.
Nobody commented on the CamelCased attribute names - I would propose to change all out attribute names in the spec to be CamelCased like the rest of SAGA and to change the Java and C++ now to match. We want to get the code released rather soon into gLite.
+1 I guess that no comment simply means silent agreemen :-) Thanks, Andre. -- Nothing is ever easy.