Links: IvoaGridAndWebServices ::
Grid and Web Services mail archive
Participants
Timetable
Tuesday May 25, 2004
Friday May 28, 2004
Materials and notes from the work group and plenary sessions
Asynchronicity
Materials
Resolutions
- This proposal to be developed further.
- Use of WS-RF is acceptable.
- WS-BaseNotification should be optional.
Issues
- Does WS-BaseNotification do reliable messaging? Does it need to?
- Need some WS-RF prototypes.
Actions
- Find out if WS-BaseNotification has reliable-messaging semantics (GuyRixon).
VObs Support Interfaces (originally called "Standard interfaces")
Materials
Resolutions
- Renamed from "standard interfaces" to "VObs support interfaces".
- All three port-types to be specified.
- getRegistration (was getMetadata, now renamed) to be optional.
- getAvailability (a.k.a. "heartbeat") to be mandatory.
- harvestLog to be optional.
- Progress to concrete design (WSDL, XSD, prototypes) ASAP.
Actions
Issues
- May need to apply access control to harvestLog
- Unclear if registries will actually use getRegistration.
Access control
Materials
Resolutions
- A SSO system based on digital signature and WS-Security is basically suitable for the IVO.
- Use of community services (run by real-world, astronomical communities) is a good way to manage users.
- Split the current proposal into two IVOA documents: (1) wire protocol; (2) Public Key Infrastructure/community services.
- Only community services for authentication should be tackled now. Community authorization is separate and might not be required.
- We need to understand the technology better before deploying it.
Issues
- Is WS-Security compatible with "Shibboleth"?
- Is WS-Security compatible with grid services/portals?
- Will service providers acccept our SSO arrangements?
- Can we handle 100+ communities? Do we expect that many?
- How do we prevent spoofing of community services (allows stealing of passwords)?
- How do we delegate work from one service to another?
Actions
- Check compatibility of WS-Security with other systems (GuyRixon)
SOAP interoperability
Materials
Resolutions
- We adopt WS-I conformance as a goal, subject to support from our web-service toolkits.
Actions
- Collect existing conformance-reports for web-service toolkits (AndreSchaaff).
- Arrange testing programmes for implementations of IVOA services (AndreSchaaff)
- Collect and publish conformance reports donated by IVOA members (AndreSchaaff).
Issues
- Axis v1.1 may be too non-conformant to use; might need to adopt Axis v1.2 beta before its final release.
Distributed storage
Resolutions
- This is now a work package for GWS-WG.
- Aim for a common, standard facade to existing storage systems (MyDB, MySpace, SRB, etc.)
Actions
This topic: IVOA
> WebHome >
IvoaEvents >
InterOpMay2004 > InterOpMay2004GridAndWebServices
Topic revision: r17 - 2004-05-28 - GuyRixon