| Question asked
|
I'm also curious about the choice of LSIDs … I'm also curious about the choice of LSIDs as identifiers. Is there anything about the LSID system which could not be achieved more simply (i.e. without an additional standard, additional tools including SOAP services and clients) using HTTP? The AuthorityID might as well be the domain name portion of an HTTP URI. The authority server then optionally redirects to the resolution service. The authors mention only querying and data retrieval, but perhaps a resolution service also provides metadata management services which require the RPC functionality of SOAP (and/or other protocols)? In that case, is a single client expected to be able to communicate with a variety of resolution services, using diverse protocols? olution services, using diverse protocols?
|
