DS3: Stage 5 Plan

The DS3 Stage 5 Plan is based upon the presentations and discussions at the ESO meeting.

---

---

Stage 5 Task List

Reports

No	Task	Who
R01	VO France Workflow and Grid WGs	CDS
R02	CEA Implementation Note	AG/ESO
R03	SSO Architexture	AstroGrid/INAF/ESO/CDS

Standards

No	Task	Who	Deliverable
S01	VOSpace	AstroGrid/ESO	VOSpace 1.0
S02	VO Application Data Model	ESO	Standard and schema
S03	CEA Data Model	ESO/AstroGrid	Standard and schema
S04	UWS-PA	AstroGrid/ESO	UWS UWS-PA as part of CEA
S05	WS Basic Profile	CDS
S06	VOStandard	ESO	Standard and schema

Prototypes

No	Task	Who
P01	JLOW and AIDA	CDS
P02	VOSpace trial implementation	CDS

Production Components

No	Task	Who
C01	UWS-PA	AstroGrid
C02	SSO	AstroGrid/ESO
C03	VOSpace	AstroGrid/ESO
C04	Registry	AstroGrid
C05	VOEvent	AstroGrid
C06	DSA	AstroGrid
C07	STILTS	AstroGrid
C08	ADQL Parser	AstroGrid
C09	WS Basic Profile tooling	CDS

Studies

No	Task	Who
T01	Cross matching	AstroGrid
T02	Interoperability Use Cases	INAF
T03	SSO VOMS and EGEE Interop	INAF
T04	VOSpace interface to EGEE DMS	INAF
T05	Test workflow tools against Use Cases	CDS
T06	Identify CDS services as candidates for UWS	CDS
T07	Vizier SkyNode interface feasability study	CDS
T08	Investigate gridShib attibute delegation certificates	ESO

---

Description of Tasks

Reports

R01. VO France Grid ans Worflow WGs

Continue the report of these 2 working groups work.

R02. CEA Implementation Note

An IVOA note describing the actual CEA implementation details.

R03. SSO Architexture

In collaboration with VOTech partners, develop a Single Sign-On architecture document. Ensure architecure informs and maintains compatibility with IVOA standards.

---

Standards

S01. VOSpace

Ensure VOSpace V1.0 currently in Working Draft gains approval at IVOA Interop in Beijing, May 2007. From this and in collaboration with EuroVO and NVO colleagues, define VOSpace V1.1 which will include metadata structure and linkage elements.

S02. VO Application Data Model

The current document needs some more cleaning up, but it the aim is to make it a 1.0 WD for the Beijing, May 2007 interop.

S03. CEA Data Model

The schema are essentially ready, but the document again needs more explanatory text to be added in time for the Beijing Interop meeting, with a view to publishing a 1.0 WD.

S04. UWS-PA

Release an IVOA Note explaining the relationship of UWS, UWS-PA and CEA.

Redraft UWS as a REST protocol; this will be v0.3 of the UWS standard. Prepare this in time for the Beijing Interop-meeting. Subsequently, refine UWS to v1.0 WD.

While UWS is evolving from v0.3 to v1.0, write the UWS-PA standard, tracking UWS changes. Aim to bring UWS-PA to v1.0 WD at the same time as UWS, or shortly after. The first draft of UWS-PA should be available for the Beijing meeting.

S05. WS Basic Profile

Bring the document to 1.0

S06. VOStandard

This is a small registry schema for describing Standards in the registry. There is a draft that needs a little tidying up with a view to promoting to WD status at Beijing interop.

---

Prototypes

P01. JLOW and AIDA

Package JLOW and give support to potential users. Use JLOW to develop a Workflow plugin for Aladin. Use AÏDA to implement Workflow use cases (from VO France Workflow WG).

P02. VOSpace trial implementation

Make CDS VOSpace useable (availability, robustness, ...) by implementing (SRB, iRods) behind it

---

Production components

C01. UWS-PA

Deploy working services based upon the UWS-PA standard.

Produce resusable web-applications that have the UWS-PA interface. These should have the scope of application of the existing CEA services.

C02. SSO

Refine current SSO services and deploy more in collaboration with EuroVO partners. In particular develop: * Servlet containers for HTTPS with RFC3820 proxy-certificates * Delegation service (allows delegation of credentials to colocated services). * Attribute service, possibly based on VOMS service. The delegation and attribute services depend on successful definition of a standard; if the standard is mired, produce prototypes instead. The delegation service depends on the results of study T03.

C03. VOSpace

Based upon VOSpace V1.1 spec, develop a working service to replace the AstroGrid MySpace prototype.

C04. Registry

Develop and deploy Registry services based upon the V1.0 schema. Ensure self registering Astrogrid services are updated to support the V1.0 schema.

C05. VOEvent

Add PLASTIC/XML­RPC end points in AR for VOEvent injection and receipt.

C06. DSA

* Support for VOSpace V1.n * UWS­PA support * TAP if agreement within IVOA reached by mid summer

C07. STILTS

Complete service implementation of STILTS complete with UWS interface.

The service should have both the old CEC and interface and a new interface implementing UWS.

This is probably an early use of UWS-PA rather than an application of UWS directly to STILTS. Therefore, it depends on production of the UWS-PA standard (S04) and possibly on the production of a reusable UWS-PA web-application (P01).

C08. ADQL Parser

Publish the ADQL Parser work from AstroGrid Query Builder as a callable library.

C09. WS Basic Profile tooling

Finalize online tool and WS-I Test tools guideline.

---

Studies

T01. Cross matching

Investigate options for cross matching of data in remote databases. Work with OGSA-DAI to identify opportunities for using their technologies. Investigate current cross matching applications and options for offering them as UWS compliant services.

T02. Interoperability Use Cases

Suggestion by GiulianoTaffoni based on DCA WP5 discussions. Design two use cases that may represent the activity of an Astronomer: a data oriented use case and a theoretical use cases. Briefely

• data orineted: get data from archive (DAL) but on VOSpace process in the Grid, save the results on VOSpace, eventually visualize the results
• theoretical: define the "simulation", execute it in the Grid, save data in the VOSpace, visualize with VO tools.

use cases definition needs discussion to define final terms of the study.

T03. SSO VOMS and EGEE Interop

Suggestions for study by GuyRixon based on DCA WP05 discussions (INAF to choose final terms of study):

• Deploy a VOMS service and load it with names of candidate EuroVO-users. These users then experiment with submitting jobs to EGEE, initially using grid UIs rather than VObs applications.
• See if VObs services can be made to use this VOMS instance.
• Experiment with hierarchical VOrgs: is it possible to run a VOMS at a user-registration site (university deparatment, laboratory or data centre) and then automatically add those users to the EuroVO VOMS?
• Request a new VOrg on EGEE for experiments (Add by GiulianoTaffoni) ?.

T04. VOSpace interface to EGEE DMS

Suggestion by GiulianoTaffoni based on DCA WP5 discussions. On the basis of the use cases we will collect some requirements for VOSpace.

• Is it possible to interface VOSpace with EGEE DMS? In this way data is stored in the storage system of EGEE but may be accessed from VObs.
• How can we authenticate with the Grid from VOSpace? Delegation service (see SSO)

T05. Test Workflow tools against Use Cases

T06. Identify CDS services as candidates for UWS

First implementations of UWS at CDS. Report.

T07. Vizier SkyNode interface feasability study

Take into account VOQL TEG work after the China Interop

T08. Investigate GridShib^?

This is complementary to the VOMS investigation T03. It might be that the gridShib solution is also a useful/necessary method of producing attribute certificates.

---

-- KeithNoddle - 23 Mar 2007