<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Dear GWS members,<br>
<br>
A quick overview of the status of the ongoing work on GWS standards
to prepare the next Interop in Sesto.<br>
<br>
VOSpace update to 2.1: <br>
Brian Major is in charge of it. Brian is working on the changes
discussed in Banff.<br>
The Roadmap decided in Banff was to be ready for the PR step for
Sesto.<br>
To be on time we need 2 implementations ready for Sesto.<br>
<br>
Reminder, from Banff discussions:<br>
- Clear up the rules of the parameter-based sync transfer as some
modes are not supported<br>
- Use of Capability and error reporting to be discussed further<br>
- Rewriting of the document in ivotex format<br>
<br>
<br>
UWS update to 1.1: <br>
Paul Harrison is in charge of it. Paul is preparing the document for
the PR step. <br>
Implementations will become crucial in the coming weeks if we want
to be on time following the Banff roadmap.<br>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<br>
Reminder, from Banff discussions:<br>
– Filtering: no disagreements but a discussion to continue
concerning the use of cookies to support the listing of jobs created
by the client<br>
– Schema change: everyone was accepting of it<br>
– Blocking: addition of stdID as part of the VOSI capabilities but
as UWS is used by VOSpace and UWS, it must be clarified<br>
– Race condition: no more concerns<br>
<br>
SSO Profile update (1.01 is the last version, version of the next
release should be cleared):<br>
Giuliano Taffoni and me are in charge of it.<br>
The roadmap for Sesto is to clean the document and to integrate the
proposals from Banff.<br>
We expect to propose a new working draft before June.<br>
We need no implementation for Sesto but in any case, if we have time
we will probably provide examples of use as illustrations for the
discussions.<br>
<br>
Reminder, from Banff discussions:<br>
- Remove “digital signature” from SSO document (formerly used for
SOAP) – Agreed<br>
- Add the support for “Federated Identity Based Authentication” -
Agreed<br>
- Shibboleth was proposed and discussed<br>
- Discussion about the use of eduroam and RSSO (Radius for Single
On)<br>
- Suggestion of a Note to state the position of the IVOA on
Authorization<br>
<br>
<br>
<br>
All comments are welcome.<br>
<br>
<br>
André<br>
</body>
</html>