Well if we are going to change that, what's the limit on change? What
do we need to keep to retain the essential "LSID"ness ?
-Alan
On Jul 18, 2007, at 2:25 PM, Phillip Lord wrote:
The LSID protocol defines a protocol for resolving LSIDs some of
which uses
web services. If it were a bring problem, the WS definition of this
API could
be replaced with something else, such as REST.
This is true with any API specification. In this case, the LSID API
is not
that complex, so the translation wouldn't be too hard.
"Alan" == Alan Ruttenberg <[EMAIL PROTECTED]> writes:
Alan> I'm intrigued by this remark. Phil, would it be possible to
sketch out
Alan> how one could graft REST style services into LSID space?
Alan> -Alan
Alan> On Jul 16, 2007, at 8:22 AM, Phillip Lord wrote:
The LSID use of web services should not really be seen as a
problem. Push
comes to shove, even this part could be replaced or made option
if a REST
style solution where desired.
--
Phillip Lord, Phone: +44 (0) 191 222 7827
Lecturer in Bioinformatics, Email:
[EMAIL PROTECTED]
School of Computing Science, http://
homepages.cs.ncl.ac.uk/phillip.lord
Claremont Tower Room 909, skype: russet_apples
Newcastle University,
NE1 7RU
