Hi Steve, You removed table 1, because the Capability attribute was added to describe the service type the user searches for. I think the table should have been edited (not removed) to help to understand what GLUE Capability Keywords map to what SAGA packages(*). As it is, the user still does not know what keyword to use when searching for a URL suitable to construct a saga::job::service instance: executionmanagement.candidatesetgenerator executionmanagement.dynamicvmdeploy executionmanagement.executionandplanning executionmanagement.jobdescription executionmanagement.jobexecution executionmanagement.jobmanager executionmanagement.reservation Which one should I use for saga::job::service? Also, the GLUE enum is open, so arbitrary backend specific keywords can pop up, too. I still think that an implementation should translate something like 'saga.directory' into the respective GLUE keywords, as table 1 described before. BTW: the examples still contain |Type = 'org.ogf.saga.service.job'| and similar in various places, which seems to come out of the former table one. An oversight? Otherwise, it looks good to me to go (attrib names, ! Best, Andre. (*) I know I am complaining about the same item over and over again - sorry for that... Quoting [Steve Fisher] (Jul 15 2009):

Hi,

As nobody objected I have made the changes to the SD spec. I attach the .pdf file. There is a changelog as required by the new procedure. Also see the comments in the errata file (also attached)

For details of the changes see CVS and compare HEAD with the tag v-1

Steve

-- Nothing is ever easy.