Registry Model for Applications

Contents

Latest Standards and Schema

Goals

• 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

Registry Model for Applications

Contents

Latest Standards and Schema

Goals

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

-- PaulHarrison - 10 Mar 2006

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Registry Model for Applications

Contents

Latest Standards and Schema

• VOApplicationDM Draft Standard

Goals

• 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

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Registry Model for Applications

Contents

Latest Standards and Schema

• VOApplicationDM Draft Standard

Goals

• 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

-- PaulHarrison - 10 Mar 2006

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Registry Model for Applications

Contents

Goals

• 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

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Registry Model for Applications

Contents

Goals

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

Schema

A set of schema that implement the models presented above are attached to this page

• General application model - The application model schema is defined in
  • VOApplication.xsd - contains the following important type defintions (amongst others)
    • basic Application type and metadata as a subtype of vr:Resource.
    • DesktopApplication -- the resource definition of an application that can be downloaded and run.
    • SoftwareLibrary -- software that does not execute, but can be used to build other software.

• CEA schema - define applications that are typically called remotely as web services - though the model is suitable for use by applications running in other containers. The schema have been split over serveral namespaces for historical reasons, and some consolidation is possible still especially combination of CeaBase.xsd and CEAParameterDefintion.xsd. Note that CEATypes.xsd contains types used exclusively in the CEA web service WSDL definition and as such is not strictly part of the registry schema set.
• Core Registry schema - core schema that are defined in RegDMServices are also included in this file for easy download into a single directory.
• example instances -- note that these files each contain several registry records that validate against RegistryInterface-v1.0.xsd.
  • application.xml - definitions of various types of desktop applications and libraries
  • cea.xml - definition of SExtractor wrapped as a CEA application.
  • sia.xml - defining the SIAP in CEA terms.

XMLSpy Schema documentation

• VOApplication.xsd
• VOCEA.xsd

-- PaulHarrison - 10 Mar 2006

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Registry Model for Applications

Contents

Goals

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

Schema

A set of schema that implement the models presented above are attached to this page

• app_v1b1_schema.zip: application model schema v1.0b1

The details of the attached files

• General application model - The application model schema is defined in
  • VOApplication.xsd - contains the following important type defintions (amongst others)
    • basic Application type and metadata as a subtype of vr:Resource.
    • DesktopApplication -- the resource definition of an application that can be downloaded and run.
    • SoftwareLibrary -- software that does not execute, but can be used to build other software.

• CEA schema - define applications that are typically called remotely as web services - though the model is suitable for use by applications running in other containers. The schema have been split over serveral namespaces for historical reasons, and some consolidation is possible still especially combination of CeaBase.xsd and CEAParameterDefintion.xsd. Note that CEATypes.xsd contains types used exclusively in the CEA web service WSDL definition and as such is not strictly part of the registry schema set.
• Core Registry schema - core schema that are defined in RegDMServices are also included in this file for easy download into a single directory.
• example instances -- note that these files each contain several registry records that validate against RegistryInterface-v1.0.xsd.
  • application.xml - definitions of various types of desktop applications and libraries
  • cea.xml - definition of SExtractor wrapped as a CEA application.
  • sia.xml - defining the SIAP in CEA terms.

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Registry Model for Applications

Contents

Goals

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

Schema

A set of schema that implement the models presented above are attached to this page

• app_v1b1_schema.zip: application model schema v1.0b1

The details of the attached files

• General application model - The application model schema is defined in
  • VOApplication.xsd - contains the following important type defintions (amongst others)
    • basic Application type and metadata as a subtype of vr:Resource.
    • DesktopApplication -- the resource definition of an application that can be downloaded and run.
    • SoftwareLibrary -- software that does not execute, but can be used to build other software.

• CEA schema - define applications that are typically called remotely as web services - though the model is suitable for use by applications running in other containers. The schema have been split over serveral namespaces for historical reasons, and some consolidation is possible still especially combination of CeaBase.xsd and CEAParameterDefintion.xsd. Note that CEATypes.xsd contains types used exclusively in the CEA web service WSDL definition and as such is not strictly part of the registry schema set.
• Core Registry schema - core schema that are defined in RegDMServices are also included in this file for easy download into a single directory.
• example instances -- note that these files each contain several registry records that validate against RegistryInterface-v1.0.xsd.
  • application.xml - definitions of various types of desktop applications and libraries
  • cea.xml - definition of SExtractor wrapped as a CEA application.
  • sia.xml - defining the SIAP in CEA terms.

-- PaulHarrison - 10 Mar 2006

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Registry Model for Applications

Contents

Goals

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

Schema

A set of schema that implement the models presented above are attached to this page

• app_v1b1_schema.zip: application model schema v1.0b1

The details of the attached files

-- PaulHarrison - 10 Mar 2006

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Registry Model for Applications

Goals

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

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Registry Model for Applications

Goals

• 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

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Registry Model for Applications

Goals

• 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

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Registry Model for Applications

Goals

• 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

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->