KMLM List

["Boerema, Cate" <Cate.Boerema@xxxxxxxxxxxxxxxxxxxx>]

In working through the requirements for our SUSHI client, we have identified a 
need to gather information from each provider about their web service 
(available report formats, report availability date etc.) This data could be 
collected manually, of course, but it would be much better if we do it 
programmatically.  I ran this by one of our developers and this is what he 
suggested:

Providers publish their service via 
UDDI<http://en.wikipedia.org/wiki/Universal_Description_Discovery_and_Integration>
 (or at least a SUSHI-approved WSDL doc at the minimum) and SUSHI could dictate 
a set of required and optional "properties" describing the providers services. 
Examples are:

1.    Available Reports Types: DB1, DB1, CR1, etc.

2.    Multiple Report Requests: Can a client request multiple reports at a 
time, or only one, or possibly by category (e.g. all DB reports, all CR 
reports, etc)

3.    Report Availability DateTime: Using GMT, what day of the month (and time, 
optionally, default=midnight) reports are guaranteed to become available to 
clients.

4.    Report Availability Granularity: Are reports available at the same 
datetime for all libraries and/or databases, or do Availability DateTimes vary 
by library and/or database?

5.    Authentication Methods: If we can't all align around a standard method 
(preferred approach), we could exchange methods permitted for use in connecting 
to the service (e.g. IP lists, user-pswd, https, etc.)

Has anyone else run into a similar need?  Any thoughts on how we might 
implement a programmatic solution?

Thanks,

Cate