Registry Model for Applications

This page summarizes the models for applications within the "tiger team"

Goals

The v10 registry schema had no specific data model that described applications, so a new model has been proposed. The general goals of this model are to support;

• General metadata about an application - e.g. Source code language. A suggested initial set of metadata were suggested at the October 2005 Interop meeting
• Information about what VOStandards and data formats the application supports;
• Concepts of
  • Desktop application - with URIs to support automatic download and launching where possible
  • Software library.
  • Applications that can be run as services - e.g. CEA.
• Can easily be extended to incorporate the registration of applications with new facilities - e.g. the PLASTIC system for desktop interaction between applications.

Application model

The UML model of how the new Application type fits into the registry schema is presented below

CEA Model in detail

In addition for the UWS specification of a remotely invocable application the CEA model (with some enhancements) will be adopted. The UML for this model is presented below.

• CEA Application:
  

The expression of these models as XML schema is work in progress.

-- PaulHarrison - 10 Mar 2006