DS3: Stage 4 Plan

The DS3 Stage 4 Plan is based upon the presentations and discussions at the Strasbourg meeting.

---

---

Stage 4 Task List

Reports

No	Task	Who
R01	DS3 Design Study Report	AstroGrid/CDS/ESO

Standards

No	Task	Who
S01	VOSpace 1.0, VOSpace 1.x (esp. containers and links)	AstroGrid/ESO
S02	Single Sign-On	AstroGrid/ESO
S03	UWS	AstroGrid/ESO
S04	CEA V1.0 Schema WD	ESO
S05	ADQL refactoring	AstroGrid
S06	Simple Table Access Protocol	AstroGrid
S07	Simple time-series Access Protocol	AstroGrid
S08	VOA WS Basic Profile	CDS

Prototypes

No	Task	Who
P01	VOSpace 1.0. Probably VOSpace 1.1 as well	AstroGrid/ESO
P02	SSO: community services & TLS support	AstroGrid/ESO
P03	UWS-PA	AstroGrid
P04	Cross-match between remote databases	AstroGrid
P05	VizieR SkyNode	CDS
P06	VOSpace	CDS
P07	UWS	CDS

Production components

No	Task	Who
C01	DSA/Catalogue (asynchronous ADQL engine with refactored ADQL)	AstroGrid
C02	DSA/Simple Table Access Protocol	AstroGrid
C03	DSA/Simple Time Access Protocol	AstroGrid
C04	Registry with V1.0 interface and v1.0 resource-schemata	AstroGrid
C05	(Possibly) vos:// protocol handler	AstroGrid
C06	Community (with certificate authority and MyProxy)	AstroGrid
C07	(eSTAR) VOEvent: parser and registry integration	AstroGrid
C08	JLOW evolution and support	CDS

Studies

No	Task	Who
T01	Workflow - Grid	CDS

---

Description of Tasks

Reports

R01. Design Study Report

See: Report

Standards

S01. VOSpace 1.0

Collaborate with the IVOA GridAndWebServices^? working group to finalise the version 1.0 specification for VOSpace services, contributing to the specification itself and also working on an interop implementation required to validate the specification.

S02. Single Sign-On

Form a "tiger team" within IVOA GWS-WG to speed up the standardization of the community services. Coordinate the VOMS community prototype (task 8) with the IVOA work.

S03. UWS

Revise the specification for the UWS pattern in light of the UWS-PA prototype as shown in Moscow. Reduce emphasis on WS-RF. Formalize the UWS-PA service-contract in light of the successful prototype shown in Moscow. Collect use cases (e.g. from Theory-WG) that show where the CEA parameter-typing might be extended.

S04. CEA Schema

Publish WD V.1.0 Application and CEA Schema IVOA Standards

S05. ADQL refactoring

Participate in the IVOA VOQL working group to produce a new version of the ADQL query language. The new language will be SQL-like and there will be no parallel XML standard. Produce a prototype ADQL/sql grammar and parser based on SQL-92, which will form the basis of a grammar and parser reference implementation for the new ADQL/sql standard.

S06. Simple Table Access Protocol

Participate in the IVOA VOQL working group to produce an initial proposal for a simple Table Access Protocol (TAP). A TAP interface will be added to the AstroGrid DSA/catalog component and made available to VOTech partners once a basic proposed standard has emerged.

S07. Simple time-series Access Protocol

Involved interested parties from the Solar and STP communities to help develop the spec. Monitor upcoming IVOA SIA and SSA protocols definitions that can 'almost' do what the time-series protocol needs to do. Ensure needs of Solar/STP communities met.

S08. IVOA WS Basic Profile

Support to bring it to IVOA recommendation.

---

Prototypes

P01. VOSpace 1.1

Collaborate with the IVOA GridAndWebServices^? working group on ideas and designs for the version 1.1 specification for VOSpace services.

P02. SSO

Astrogrid will make prototypes of a community attribute service that supports community-managed user-groups. This should be made useful both for VObs-level services and grid services. Discussions with DCA WP5 suggest that a minor enhancement of VOMS will be the best way to proceed. Astrogrid will produce a servlet engine that supports TLS with RFC3820 proxies. This should be a version of Jetty enhanced with a special JSSE implementation ("provider") supporting RFC3820. The JSSE provider may be reused in other contexts; it may even be possible to retrofit it to Tomcat.

It will be necessary to standardize the "community services" so that AR no longer dependent on talking to Astrogrid Community component.

ESO will add "community style" interfaces to the current ESO user database, to allow ESO credentials to be used in the VO. In addition ESO will integrate RFC3820 certificate use with the CAS system that is being used for SSO on the ESO portal.

P03. UWS-PA

No plans to produce a production version of UWS-PA before March. A second prototype may be built if it informs the development of the standard.

P04. Cross-match between remote databases

Participate in the IVOA VOQL working group discussion on crossmatching, and where it should reside in the IVO architecture. It seems likely that crossmatching will be supported as a separate service standard rather than as part of either the ADQL language or the Table Access Protocol.

P05. VizieR SkyNode

Work depending on SkyNode^?-ADQL evolution.

P06. VOSpace

Implementation at CDS. Work on topics like data replication... , report and make proposals.

P07. UWS

Implementation at CDS for different use cases (image processing, ...)

---

Production components

C01. DSA/Catalogue (asynchronous ADQL engine with refactored ADQL)

Building upon the major architectural changes to DSA/Catalog in previous stages, undertake a steady stream of incremental improvements and enhancements to both the user interface and the underlying processing engine. Collaborate with the OGSA-DAI project to explore how OGSA-DAI might help the DSA to support user-writeable tables and integration into VOSpace. Integration of the new Table Access Protocol and ADQL/sql standards is likely in the Stage-5/6 timeframe.

C02. DSA/Simple Table Access Protocol

Work on new ADQL parser. Deliverables:

• Parser (merge SQL92 and the old XML based standard in an ADQL/s format)
• Actively navigable BNF syntax diagrams (using a browser)
• Test program to allow the syntax of specific queries to be tried out.

C03. DSA/Simple Time Access Protocol

Develop prototype. Deploy against MSSL data holdings which will then be seen in Helioscope.

C04. Registry with V1.0 interface and v1.0 resource-schemata

Implement V1.0 Interface and V1.0 Resource Schemata. Deploy test registries. Include in AstroGrid 2006.4 or 2007.1 release as appropriate. Upgrade filestore, filemanager, and community to publish 1.0 VOResource metadata. Refactor workbench to use new XQuery. Investigate:

• better validationLevel handling to enable institutes to add there own validationLevel to Resources that they do not manage or own
• harvest services in preparation for adoption of VOSI

C05. (Possibly) vos:// protocol handler

Predicated by VOSpace access becoming available via AR, itself predicated by ratification of VOSpec spec at IVOA. May well slip into Stage-5.

C06. Community (with certificate authority and MyProxy)

Produce an upgrade for the AstroGrid Community component that deals in identity certificates. This lets sites that have already deployed the community component issue certificates to their end-users by means of a local certificate authority and export those certificates by means of a MyProxy service. The upgrade shall work with the established database of users in each AstroGrid community. Externally-issued certificates shall also be useable in this system (i.e. the users may load the MyProxy server with their own certificates) but no special code shall be provided to support this.

C07. (eSTAR) VOEvent: Driving the VO in the time domain

Feature complete parser tracking the evolution of the VOEvent and Transport document standards, collaboration with the Greek EUDOXOS project on a second interoperable parser.

The rapid growth in the event network took up the bulk of the time. Interfaces were built to handle messages from the PLANET/Robonet-1.0, Angstrom and ESSENCE projects for real time notifications of events and injection of messages into the VO.

Experimenting with storage prototypes and outlines for a Simple Event Access Protocol (SEAP).

Experimenting with using incoming VOEvent messages to trigger searches into the VO via the Workbench.

Expanded capabilities of event broker software, and rebuilt the prototype gateway between the RAPTOR/TALONS and eSTAR networks to produce a robust production quality piece of software that also handled the new VOEvent document standard as well as the HTN's own RTML documents.

Deployed a closed beta release of a manual injection system for VOEvent messages, jointly hosted between Exeter and LANL. This service allows users to easily build VOEvent messages from a generic templates, and then inject these messages directly onto the backbone event network.

C08. JLOW evolution and support

Support to VOTech partners.

---

Studies

T01. Workflow - Grid

Use cases, workflow data model, definition of templates
Report the Workflow and Grid working groups results to VOTech.

---

Principal DS3 Partner Contact Persons

AstroGrid	KeithNoddle
CDS	AndreSchaaff
ESO	PaulHarrison

---

-- KeithNoddle - 29 Nov 2006