SRM Conf call 09 Nov.2005

JLAB: Michael, Bryan, Chip
RAL: Owen
CERN: peter
LBNL: Arie, Alex

SFN  
part of the SURL. need to defined in SRM document?
explanation of SURL to be composed of host, port, end point, and some identifier would be good.

Dynamic XML schema driven interface
Michael concerns giving up WSDL based interface advantage. didn't want to go this way unless there is a very compelling reason. 
peter has no strong opinion one or the other. 
arie, adv is flexibility, disadv is parsing
peter, don't have tech problem. how about going toa mixed model?
alex, yes, discussing with michael about the mixing
arie, core parameters go into WSDL and additional ones in XML schema
alex, we'll come up with a mixed model exmaple

httpg
peter, currently we use httpg. globus moved away as well. non std. https with delegation port type is preferred. will send a link

wildcard
arie, we've been using this for star project sinve v1
chip, useful and not hard to implement, simple wildcard, not reg exp
peter, I have this requirement as well
michael, wildcard for ls only.
arie, have in all
all, wildcard on ls only

voting mechanism. arie will circulate some idea

func spec v3 new draft to be circulated this year

requirement doc
michael, purpose is to see what SRM does. 
arie, requirement doc is an introduction to the use case
peter, enough to have a well defined use case doc
owen, volunteer to collect terms and put on twiki
peter, simply to have a high level use case doc that includes requirements
alex, will make a formal use case doc, collecting from twiki (owen and peter's case) and add lbl's case

operation id
owen, resurrected from the email thread
alex, will see the email thread

next conf call in 2-3 weeks or skip the next one because of the thanksgiving in the us