Difference: IVOATheorySimDB (1 vs. 2)

Revision 22009-03-12 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
Changed:
<
<

From SNAP to SimDB/SimDAP

>
>

SimDB = Simulation Database

Added:
>
>
  • page describing why we think SimDB development needs explicit input from different working groups.
 
Changed:
<
<
This page contains a general introduction on why we decided to move from SNAP to SimDB/SimDAP. Details on SimDB/SimDAP can be found
>
>
We have split up the former SNAP effort of the Theory Interest Group in two separate ones: SimDB(=Simulation Database) and SimDAP(=Simulation Data Access Protocol). Here we describe SimDB.
Deleted:
<
<
here.
 
Changed:
<
<

>
>
SimDB is a specification for a Simulation (meta-)Database (could be called Simulation Registry, -Portal).
Deleted:
<
<

We have split up the former SNAP effort of the Theory Interest Group in two separate ones: SimDB(=Simulation Database) and SimDAP(=Simulation Data Access Protocol). SimDB is a specification for a Simulation (meta-)Database (could be called Simulation Registry, -Portal).
 
Changed:
<
<
SimDB is an online service offering query capabilities to a database containing meta data describing results of simulations and their post-processing as well as about the codes used in these algorithms.
>
>
SimDB is an online service offering query capabilities to a database containing meta data describing results of simulations and their post-processing as well as about the codes used in these algorithms.
 Currently the simulations are still supposed to be those that produce a representation of 3+1D space, (possibly reduced spatial dimension through assumptions of symmetry). This is open for discussion.
Changed:
<
<
A SimDB also contains information about web services giving access to the simulation results themselves. The more detailed specification of such services is the goal of the SimDAP-specification.
>
>
A SimDB also contains information about web services giving access to the simulation results themselves. The more detailed specification of such services is the goal of the SimDAP-specification.
Deleted:
<
<

Interactions with others WGs:

We plan forming a focus group to tackle SimDB and other issues. This group should contain members from several relevant WGs (DM, Registry, Semantics, DAL), together with the current developers of SimDB, members from the TIG. Indeed, some issues have to be solved that require input from a number of working groups, among which are:

  • We need to iron out the wrinkles from the data model and check its relevance. Beside the inputs from theorists to see whether their results fit in the model, we also need input from the DM WG on various aspects of the DM.

  • Should a SimDB be stand alone, or should it be possible to have relations between SimDB/Resource-s in different SimDB-s? The answer to this has repercussions for the XML and RDB representations. It may have repercussions for the functioning of a SimDB in case it is supposed to be stand alone (mirroring through harvesting of external resources may be required). We would like to discuss these issues with the Registry WG who have experience with similar issues.

  • Should a SimDB be read-only, i.e. represent the work of the groups publishing their own results? Or can external parties register their results in a nearby SimDB? I.e., is SimDB S*AP like, or Registry like (an extension registry?), or something in between? We'd like to discuss this with Registry and DAL WGs.

  • We need a common vocabulary for certain attributes in the model that refer to astrophysical concepts and are likely prime targets for queries. We want to use existing vocabularies where possible, but may need to define new ones. We would like to discuss this with the Semantics WG.

  • We need a way to express formally that SimDB services offer a particular ADQL query interface. We think we need to discuss these issues with Registry and DAL(TAP) WGs.

  • SimDB is a service that ADQL queries can be sent to and may(?) be thought of as a TAP service. However we'd rather not wait until TAPs specification is done before continuing. We would like to discuss the issues arising from this within the context of TAP and ADQL, i.e. need discussions with DAL and VOQL.

It is unclear what the formal organization should be, as there is not a single WG that could most obviously be given responsibility for the further development of this standard and the theory INTEREST group can not move a working draft through the recommendation track.

 

-- HerveWozniak - 23 Jun 2008


<--  
-->

Revision 12008-06-23 - HerveWozniak

 
META TOPICPARENT name="IvoaTheory"

From SNAP to SimDB/SimDAP

This page contains a general introduction on why we decided to move from SNAP to SimDB/SimDAP. Details on SimDB/SimDAP can be found here.



We have split up the former SNAP effort of the Theory Interest Group in two separate ones: SimDB(=Simulation Database) and SimDAP(=Simulation Data Access Protocol). SimDB is a specification for a Simulation (meta-)Database (could be called Simulation Registry, -Portal).

SimDB is an online service offering query capabilities to a database containing meta data describing results of simulations and their post-processing as well as about the codes used in these algorithms. Currently the simulations are still supposed to be those that produce a representation of 3+1D space, (possibly reduced spatial dimension through assumptions of symmetry). This is open for discussion.

A SimDB also contains information about web services giving access to the simulation results themselves. The more detailed specification of such services is the goal of the SimDAP-specification.

Interactions with others WGs:

We plan forming a focus group to tackle SimDB and other issues. This group should contain members from several relevant WGs (DM, Registry, Semantics, DAL), together with the current developers of SimDB, members from the TIG. Indeed, some issues have to be solved that require input from a number of working groups, among which are:

  • We need to iron out the wrinkles from the data model and check its relevance. Beside the inputs from theorists to see whether their results fit in the model, we also need input from the DM WG on various aspects of the DM.

  • Should a SimDB be stand alone, or should it be possible to have relations between SimDB/Resource-s in different SimDB-s? The answer to this has repercussions for the XML and RDB representations. It may have repercussions for the functioning of a SimDB in case it is supposed to be stand alone (mirroring through harvesting of external resources may be required). We would like to discuss these issues with the Registry WG who have experience with similar issues.

  • Should a SimDB be read-only, i.e. represent the work of the groups publishing their own results? Or can external parties register their results in a nearby SimDB? I.e., is SimDB S*AP like, or Registry like (an extension registry?), or something in between? We'd like to discuss this with Registry and DAL WGs.

  • We need a common vocabulary for certain attributes in the model that refer to astrophysical concepts and are likely prime targets for queries. We want to use existing vocabularies where possible, but may need to define new ones. We would like to discuss this with the Semantics WG.

  • We need a way to express formally that SimDB services offer a particular ADQL query interface. We think we need to discuss these issues with Registry and DAL(TAP) WGs.

  • SimDB is a service that ADQL queries can be sent to and may(?) be thought of as a TAP service. However we'd rather not wait until TAPs specification is done before continuing. We would like to discuss the issues arising from this within the context of TAP and ADQL, i.e. need discussions with DAL and VOQL.

It is unclear what the formal organization should be, as there is not a single WG that could most obviously be given responsibility for the further development of this standard and the theory INTEREST group can not move a working draft through the recommendation track.

-- IVOA.HerveWozniak - 23 Jun 2008


<-- 
    • Set ALLOWTOPICRENAME = Main.TWikiAdminGroup
-->
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback