Jumps: IvoaResReg :: reg-dm mail archive :: ResourceMetadata
Meetings: InterOpMay2004ResReg :: InterOpMay2005ResReg :: InterOpOct2005ResReg :: InterOpMay2006ResReg

Registry Model for Applications

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

Contents

---

Latest Standards and Schema

The latest versions of the standard, schema and examples are store in the Volute Googlecode SVN repository http://code.google.com/p/volute/source/browse/#svn/trunk/projects/registry/application

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 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

Note that the Common Execution Architecture (CEA) has its own page. However, of direct relevance to the registration of CEA are;

• VOCEA-v1.0.xsd schema for CEA application and CEA server registration
• cea.xml An example registration of a CEA server and CEA application.

-- PaulHarrison - 10 Mar 2006