Difference: IVOATheorySimDB (1 vs. 15)

Revision 152012-06-26 - root

 
META TOPICPARENT name="IvoaTheory"

SimDB = Simulation Database

SimDB is a specification for a Simulation Database. A SimDB implementation contains a database with (meta-)data describing simulations, their results, their provenance and various characteristics. The simulations are supposed to be those that produce a representation of 3+1D space, sometimes called "cosmological simulations", though they can be of any scale, from large scale structure of the universe down to solar systems. It has been a point of discussion whether we should open the spec up for all, or at least more types of simulations. This is an open issue. A SimDB also contains various types of post-processing products, as well as meta data identifying web services giving access to these simulations. The latter may, but are not restricted to SimDAP services.

The SimDB specification defines a protocol for an online service for querying and some management of this database. It has two components. One is a specialised TAP service, the other is a REST-like GET protocol to retrieve complete descriptions in XML form. Both of these are based on a data model for simulations, which is also part of this specification.

The full specification consists of a number of different documents. The latest versions of these as well as earlier ones, can be found in the specification directory under the theory/snapdm section of Norman Gray's Volute project on GoogleCode.

The theory/snapdmsection contains a lot more material than the specification alone. Most of this is the result of a project to create a demonstrator proto-type for the SimDB project. That project is in the process of being ported to the VO-URP project.

For the purpose of this specification one need only consult the specification sub directory. It contains the following documents:

  • DEPRECATED SimDB-note.doc (in rod, here is pdf): the Note describing SimDB, should be turned into a working draft at some point in the hopefully near future.
  • uml/SimDB_DM.xml: XMI document containing the UML data model on which the spec is based. Created by the 12.1 version of the community edition of MagicDraw UML drawing tool.
  • uml/SimDB_DM_INTERMEDIATE.xml: an XML document containing the so called "intermediate representation" of the data model. This is derived from the XMI model and is (much) easier to read and handle.
  • html/SimDB.html: HTML documentation fo rthe datamodel. Fully crosslinked and documented. Contains also the UTYPEs for the data model elements.
  • tap/SimDB_vodataservice.xml: XML document creating the TAP metadata for the SimDB database as a VODataservice.
  • tap/SimDB_tap_tableset.xml: XMl document containing the TAP metadata for the SimDB database as an "empty" VOTable (i.e. a TABLE for each public table, with FIELDs but no DATA)
  • xsd/: XML Schema files that defines how instances of the data model can be presented in XML.
    • xsd/SimDB_root.xsd: the "element" part of the SimDB schema set. It contains the valid root elements, i.e. the ones with which documents can be made. It depends on "type-schemas" that are all imported by this schema.
    • base.xsd: a schema defining some base types for use by other type definitions in the schema set.
    • The other XSD files in xsd/ and xsd/simdb/ and sub-directories define the (complex and simple)types. There is one type-schema document per XSD namespace, one XSD namespace per UML package.
  • xslt/: contains XSLT scripts that were used to generate the HTML, XSD and TAP documents from the UML model. They are here for informational purposes, and are not part of the specification. The build.xml ANT script in uml/ contains tasks for creating these documents.

Discussion pages

Other pages on the IVOA Wiki pertaining to this specification are

-- GerardLemson - 13 Mar 2009
-- HerveWozniak - 23 Jun 2008


META FILEATTACHMENT attr="" comment="" date="1243073465" name="SimDB_Note.pdf" path="SimDB_Note.pdf" size="575329" user="GerardLemson" version="1.1"

Revision 142009-10-12 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"

SimDB = Simulation Database

SimDB is a specification for a Simulation Database. A SimDB implementation contains a database with (meta-)data describing simulations, their results, their provenance and various characteristics. The simulations are supposed to be those that produce a representation of 3+1D space, sometimes called "cosmological simulations", though they can be of any scale, from large scale structure of the universe down to solar systems. It has been a point of discussion whether we should open the spec up for all, or at least more types of simulations. This is an open issue. A SimDB also contains various types of post-processing products, as well as meta data identifying web services giving access to these simulations. The latter may, but are not restricted to SimDAP services.

The SimDB specification defines a protocol for an online service for querying and some management of this database. It has two components. One is a specialised TAP service, the other is a REST-like GET protocol to retrieve complete descriptions in XML form. Both of these are based on a data model for simulations, which is also part of this specification.

The full specification consists of a number of different documents. The latest versions of these as well as earlier ones, can be found in the specification directory under the theory/snapdm section of Norman Gray's Volute project on GoogleCode.

The theory/snapdmsection contains a lot more material than the specification alone. Most of this is the result of a project to create a demonstrator proto-type for the SimDB project. That project is in the process of being ported to the VO-URP project.

For the purpose of this specification one need only consult the specification sub directory. It contains the following documents:

Changed:
<
<
  • SimDB-note.doc (in rod, here is pdf): the Note describing SimDB, should be turned into a working draft at some point in the hopefully near future.
>
>
  • DEPRECATED SimDB-note.doc (in rod, here is pdf): the Note describing SimDB, should be turned into a working draft at some point in the hopefully near future.
Added:
>
>
 
  • uml/SimDB_DM.xml: XMI document containing the UML data model on which the spec is based. Created by the 12.1 version of the community edition of MagicDraw UML drawing tool.
  • uml/SimDB_DM_INTERMEDIATE.xml: an XML document containing the so called "intermediate representation" of the data model. This is derived from the XMI model and is (much) easier to read and handle.
  • html/SimDB.html: HTML documentation fo rthe datamodel. Fully crosslinked and documented. Contains also the UTYPEs for the data model elements.
  • tap/SimDB_vodataservice.xml: XML document creating the TAP metadata for the SimDB database as a VODataservice.
  • tap/SimDB_tap_tableset.xml: XMl document containing the TAP metadata for the SimDB database as an "empty" VOTable (i.e. a TABLE for each public table, with FIELDs but no DATA)
  • xsd/: XML Schema files that defines how instances of the data model can be presented in XML.
    • xsd/SimDB_root.xsd: the "element" part of the SimDB schema set. It contains the valid root elements, i.e. the ones with which documents can be made. It depends on "type-schemas" that are all imported by this schema.
    • base.xsd: a schema defining some base types for use by other type definitions in the schema set.
    • The other XSD files in xsd/ and xsd/simdb/ and sub-directories define the (complex and simple)types. There is one type-schema document per XSD namespace, one XSD namespace per UML package.
  • xslt/: contains XSLT scripts that were used to generate the HTML, XSD and TAP documents from the UML model. They are here for informational purposes, and are not part of the specification. The build.xml ANT script in uml/ contains tasks for creating these documents.

Discussion pages

Other pages on the IVOA Wiki pertaining to this specification are

-- GerardLemson - 13 Mar 2009
-- HerveWozniak - 23 Jun 2008


<--  
-->

META FILEATTACHMENT attr="" comment="" date="1243073465" name="SimDB_Note.pdf" path="SimDB_Note.pdf" size="575329" user="GerardLemson" version="1.1"

Revision 132009-05-23 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"

SimDB = Simulation Database

SimDB is a specification for a Simulation Database. A SimDB implementation contains a database with (meta-)data describing simulations, their results, their provenance and various characteristics. The simulations are supposed to be those that produce a representation of 3+1D space, sometimes called "cosmological simulations", though they can be of any scale, from large scale structure of the universe down to solar systems. It has been a point of discussion whether we should open the spec up for all, or at least more types of simulations. This is an open issue. A SimDB also contains various types of post-processing products, as well as meta data identifying web services giving access to these simulations. The latter may, but are not restricted to SimDAP services.

The SimDB specification defines a protocol for an online service for querying and some management of this database. It has two components. One is a specialised TAP service, the other is a REST-like GET protocol to retrieve complete descriptions in XML form. Both of these are based on a data model for simulations, which is also part of this specification.

The full specification consists of a number of different documents. The latest versions of these as well as earlier ones, can be found in the specification directory under the theory/snapdm section of Norman Gray's Volute project on GoogleCode.

The theory/snapdmsection contains a lot more material than the specification alone. Most of this is the result of a project to create a demonstrator proto-type for the SimDB project. That project is in the process of being ported to the VO-URP project.

For the purpose of this specification one need only consult the specification sub directory. It contains the following documents:

Changed:
<
<
  • SimDB-note.doc: the Note describing SimDB, should be turned into a working draft at some point in the hopefully near future.
>
>
  • SimDB-note.doc (in rod, here is pdf): the Note describing SimDB, should be turned into a working draft at some point in the hopefully near future.
 
  • uml/SimDB_DM.xml: XMI document containing the UML data model on which the spec is based. Created by the 12.1 version of the community edition of MagicDraw UML drawing tool.
  • uml/SimDB_DM_INTERMEDIATE.xml: an XML document containing the so called "intermediate representation" of the data model. This is derived from the XMI model and is (much) easier to read and handle.
  • html/SimDB.html: HTML documentation fo rthe datamodel. Fully crosslinked and documented. Contains also the UTYPEs for the data model elements.
  • tap/SimDB_vodataservice.xml: XML document creating the TAP metadata for the SimDB database as a VODataservice.
  • tap/SimDB_tap_tableset.xml: XMl document containing the TAP metadata for the SimDB database as an "empty" VOTable (i.e. a TABLE for each public table, with FIELDs but no DATA)
  • xsd/: XML Schema files that defines how instances of the data model can be presented in XML.
    • xsd/SimDB_root.xsd: the "element" part of the SimDB schema set. It contains the valid root elements, i.e. the ones with which documents can be made. It depends on "type-schemas" that are all imported by this schema.
    • base.xsd: a schema defining some base types for use by other type definitions in the schema set.
    • The other XSD files in xsd/ and xsd/simdb/ and sub-directories define the (complex and simple)types. There is one type-schema document per XSD namespace, one XSD namespace per UML package.
  • xslt/: contains XSLT scripts that were used to generate the HTML, XSD and TAP documents from the UML model. They are here for informational purposes, and are not part of the specification. The build.xml ANT script in uml/ contains tasks for creating these documents.

Discussion pages

Other pages on the IVOA Wiki pertaining to this specification are

-- GerardLemson - 13 Mar 2009
-- HerveWozniak - 23 Jun 2008


<--  
-->
Added:
>
>
 
Added:
>
>
META FILEATTACHMENT attr="" comment="" date="1243073465" name="SimDB_Note.pdf" path="SimDB_Note.pdf" size="575329" user="GerardLemson" version="1.1"
 

Revision 122009-05-18 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"

SimDB = Simulation Database

SimDB is a specification for a Simulation Database. A SimDB implementation contains a database with (meta-)data describing simulations, their results, their provenance and various characteristics. The simulations are supposed to be those that produce a representation of 3+1D space, sometimes called "cosmological simulations", though they can be of any scale, from large scale structure of the universe down to solar systems. It has been a point of discussion whether we should open the spec up for all, or at least more types of simulations. This is an open issue. A SimDB also contains various types of post-processing products, as well as meta data identifying web services giving access to these simulations. The latter may, but are not restricted to SimDAP services.

The SimDB specification defines a protocol for an online service for querying and some management of this database. It has two components. One is a specialised TAP service, the other is a REST-like GET protocol to retrieve complete descriptions in XML form. Both of these are based on a data model for simulations, which is also part of this specification.

The full specification consists of a number of different documents. The latest versions of these as well as earlier ones, can be found in the specification directory under the theory/snapdm section of Norman Gray's Volute project on GoogleCode.

The theory/snapdmsection contains a lot more material than the specification alone. Most of this is the result of a project to create a demonstrator proto-type for the SimDB project. That project is in the process of being ported to the VO-URP project.

For the purpose of this specification one need only consult the specification sub directory. It contains the following documents:

  • SimDB-note.doc: the Note describing SimDB, should be turned into a working draft at some point in the hopefully near future.
  • uml/SimDB_DM.xml: XMI document containing the UML data model on which the spec is based. Created by the 12.1 version of the community edition of MagicDraw UML drawing tool.
  • uml/SimDB_DM_INTERMEDIATE.xml: an XML document containing the so called "intermediate representation" of the data model. This is derived from the XMI model and is (much) easier to read and handle.
  • html/SimDB.html: HTML documentation fo rthe datamodel. Fully crosslinked and documented. Contains also the UTYPEs for the data model elements.
  • tap/SimDB_vodataservice.xml: XML document creating the TAP metadata for the SimDB database as a VODataservice.
  • tap/SimDB_tap_tableset.xml: XMl document containing the TAP metadata for the SimDB database as an "empty" VOTable (i.e. a TABLE for each public table, with FIELDs but no DATA)
  • xsd/: XML Schema files that defines how instances of the data model can be presented in XML.
    • xsd/SimDB_root.xsd: the "element" part of the SimDB schema set. It contains the valid root elements, i.e. the ones with which documents can be made. It depends on "type-schemas" that are all imported by this schema.
    • base.xsd: a schema defining some base types for use by other type definitions in the schema set.
    • The other XSD files in xsd/ and xsd/simdb/ and sub-directories define the (complex and simple)types. There is one type-schema document per XSD namespace, one XSD namespace per UML package.
  • xslt/: contains XSLT scripts that were used to generate the HTML, XSD and TAP documents from the UML model. They are here for informational purposes, and are not part of the specification. The build.xml ANT script in uml/ contains tasks for creating these documents.

Discussion pages

Other pages on the IVOA Wiki pertaining to this specification are
Added:
>
>
 

-- GerardLemson - 13 Mar 2009
-- HerveWozniak - 23 Jun 2008


<--  
-->

Revision 112009-05-13 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"

SimDB = Simulation Database

SimDB is a specification for a Simulation Database. A SimDB implementation contains a database with (meta-)data describing simulations, their results, their provenance and various characteristics. The simulations are supposed to be those that produce a representation of 3+1D space, sometimes called "cosmological simulations", though they can be of any scale, from large scale structure of the universe down to solar systems. It has been a point of discussion whether we should open the spec up for all, or at least more types of simulations. This is an open issue. A SimDB also contains various types of post-processing products, as well as meta data identifying web services giving access to these simulations. The latter may, but are not restricted to SimDAP services.

The SimDB specification defines a protocol for an online service for querying and some management of this database. It has two components. One is a specialised TAP service, the other is a REST-like GET protocol to retrieve complete descriptions in XML form. Both of these are based on a data model for simulations, which is also part of this specification.

The full specification consists of a number of different documents. The latest versions of these as well as earlier ones, can be found in the specification directory under the theory/snapdm section of Norman Gray's Volute project on GoogleCode.

The theory/snapdmsection contains a lot more material than the specification alone. Most of this is the result of a project to create a demonstrator proto-type for the SimDB project. That project is in the process of being ported to the VO-URP project.

For the purpose of this specification one need only consult the specification sub directory. It contains the following documents:

  • SimDB-note.doc: the Note describing SimDB, should be turned into a working draft at some point in the hopefully near future.
  • uml/SimDB_DM.xml: XMI document containing the UML data model on which the spec is based. Created by the 12.1 version of the community edition of MagicDraw UML drawing tool.
  • uml/SimDB_DM_INTERMEDIATE.xml: an XML document containing the so called "intermediate representation" of the data model. This is derived from the XMI model and is (much) easier to read and handle.
  • html/SimDB.html: HTML documentation fo rthe datamodel. Fully crosslinked and documented. Contains also the UTYPEs for the data model elements.
  • tap/SimDB_vodataservice.xml: XML document creating the TAP metadata for the SimDB database as a VODataservice.
  • tap/SimDB_tap_tableset.xml: XMl document containing the TAP metadata for the SimDB database as an "empty" VOTable (i.e. a TABLE for each public table, with FIELDs but no DATA)
  • xsd/: XML Schema files that defines how instances of the data model can be presented in XML.
    • xsd/SimDB_root.xsd: the "element" part of the SimDB schema set. It contains the valid root elements, i.e. the ones with which documents can be made. It depends on "type-schemas" that are all imported by this schema.
    • base.xsd: a schema defining some base types for use by other type definitions in the schema set.
    • The other XSD files in xsd/ and xsd/simdb/ and sub-directories define the (complex and simple)types. There is one type-schema document per XSD namespace, one XSD namespace per UML package.
  • xslt/: contains XSLT scripts that were used to generate the HTML, XSD and TAP documents from the UML model. They are here for informational purposes, and are not part of the specification. The build.xml ANT script in uml/ contains tasks for creating these documents.
Changed:
<
<
>
>

Discussion pages

 Other pages on the IVOA Wiki pertaining to this specification are
Added:
>
>
 
  • IVOA.IVOATheorySimDB_WGs describing why we think SimDB development needs explicit input from different working groups.

-- GerardLemson - 13 Mar 2009
-- HerveWozniak - 23 Jun 2008


<--  
-->

Revision 102009-05-13 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"

SimDB = Simulation Database

SimDB is a specification for a Simulation Database. A SimDB implementation contains a database with (meta-)data describing simulations, their results, their provenance and various characteristics. The simulations are supposed to be those that produce a representation of 3+1D space, sometimes called "cosmological simulations", though they can be of any scale, from large scale structure of the universe down to solar systems. It has been a point of discussion whether we should open the spec up for all, or at least more types of simulations. This is an open issue. A SimDB also contains various types of post-processing products, as well as meta data identifying web services giving access to these simulations. The latter may, but are not restricted to SimDAP services.

The SimDB specification defines a protocol for an online service for querying and some management of this database. It has two components. One is a specialised TAP service, the other is a REST-like GET protocol to retrieve complete descriptions in XML form. Both of these are based on a data model for simulations, which is also part of this specification.

The full specification consists of a number of different documents. The latest versions of these as well as earlier ones, can be found in the specification directory under the theory/snapdm section of Norman Gray's Volute project on GoogleCode.

The theory/snapdmsection contains a lot more material than the specification alone. Most of this is the result of a project to create a demonstrator proto-type for the SimDB project. That project is in the process of being ported to the VO-URP project.

For the purpose of this specification one need only consult the specification sub directory. It contains the following documents:

  • SimDB-note.doc: the Note describing SimDB, should be turned into a working draft at some point in the hopefully near future.
  • uml/SimDB_DM.xml: XMI document containing the UML data model on which the spec is based. Created by the 12.1 version of the community edition of MagicDraw UML drawing tool.
  • uml/SimDB_DM_INTERMEDIATE.xml: an XML document containing the so called "intermediate representation" of the data model. This is derived from the XMI model and is (much) easier to read and handle.
  • html/SimDB.html: HTML documentation fo rthe datamodel. Fully crosslinked and documented. Contains also the UTYPEs for the data model elements.
  • tap/SimDB_vodataservice.xml: XML document creating the TAP metadata for the SimDB database as a VODataservice.
  • tap/SimDB_tap_tableset.xml: XMl document containing the TAP metadata for the SimDB database as an "empty" VOTable (i.e. a TABLE for each public table, with FIELDs but no DATA)
  • xsd/: XML Schema files that defines how instances of the data model can be presented in XML.
    • xsd/SimDB_root.xsd: the "element" part of the SimDB schema set. It contains the valid root elements, i.e. the ones with which documents can be made. It depends on "type-schemas" that are all imported by this schema.
    • base.xsd: a schema defining some base types for use by other type definitions in the schema set.
    • The other XSD files in xsd/ and xsd/simdb/ and sub-directories define the (complex and simple)types. There is one type-schema document per XSD namespace, one XSD namespace per UML package.
  • xslt/: contains XSLT scripts that were used to generate the HTML, XSD and TAP documents from the UML model. They are here for informational purposes, and are not part of the specification. The build.xml ANT script in uml/ contains tasks for creating these documents.

Other pages on the IVOA Wiki pertaining to this specification are

Changed:
<
<
>
>
 
Changed:
<
<
  • page describing why we think SimDB development needs explicit input from different working groups.
>
>
  • IVOA.IVOATheorySimDBSemantics: discussing features of SimDB requiring input from Semantics WG, e.g. how to use SKOS vocabularies in the DM, and how to create (and use) new ones.
Added:
>
>
  • IVOA.IVOATheorySimDBRegistry: relation of SimDB to registry WG (reuse of concepts form Resource DM, registration of SimDB implementations, registration of features of SimDB data model)
  • IVOA.IVOATheorySimDB_WGs describing why we think SimDB development needs explicit input from different working groups.
 

-- GerardLemson - 13 Mar 2009
-- HerveWozniak - 23 Jun 2008


<--  
-->

Revision 92009-05-12 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"

SimDB = Simulation Database

SimDB is a specification for a Simulation Database. A SimDB implementation contains a database with (meta-)data describing simulations, their results, their provenance and various characteristics. The simulations are supposed to be those that produce a representation of 3+1D space, sometimes called "cosmological simulations", though they can be of any scale, from large scale structure of the universe down to solar systems. It has been a point of discussion whether we should open the spec up for all, or at least more types of simulations. This is an open issue. A SimDB also contains various types of post-processing products, as well as meta data identifying web services giving access to these simulations. The latter may, but are not restricted to SimDAP services.

The SimDB specification defines a protocol for an online service for querying and some management of this database. It has two components. One is a specialised TAP service, the other is a REST-like GET protocol to retrieve complete descriptions in XML form. Both of these are based on a data model for simulations, which is also part of this specification.

The full specification consists of a number of different documents. The latest versions of these as well as earlier ones, can be found in the specification directory under the theory/snapdm section of Norman Gray's Volute project on GoogleCode.

The theory/snapdmsection contains a lot more material than the specification alone. Most of this is the result of a project to create a demonstrator proto-type for the SimDB project. That project is in the process of being ported to the VO-URP project.

For the purpose of this specification one need only consult the specification sub directory. It contains the following documents:

  • SimDB-note.doc: the Note describing SimDB, should be turned into a working draft at some point in the hopefully near future.
  • uml/SimDB_DM.xml: XMI document containing the UML data model on which the spec is based. Created by the 12.1 version of the community edition of MagicDraw UML drawing tool.
  • uml/SimDB_DM_INTERMEDIATE.xml: an XML document containing the so called "intermediate representation" of the data model. This is derived from the XMI model and is (much) easier to read and handle.
  • html/SimDB.html: HTML documentation fo rthe datamodel. Fully crosslinked and documented. Contains also the UTYPEs for the data model elements.
  • tap/SimDB_vodataservice.xml: XML document creating the TAP metadata for the SimDB database as a VODataservice.
  • tap/SimDB_tap_tableset.xml: XMl document containing the TAP metadata for the SimDB database as an "empty" VOTable (i.e. a TABLE for each public table, with FIELDs but no DATA)
  • xsd/: XML Schema files that defines how instances of the data model can be presented in XML.
    • xsd/SimDB_root.xsd: the "element" part of the SimDB schema set. It contains the valid root elements, i.e. the ones with which documents can be made. It depends on "type-schemas" that are all imported by this schema.
    • base.xsd: a schema defining some base types for use by other type definitions in the schema set.
    • The other XSD files in xsd/ and xsd/simdb/ and sub-directories define the (complex and simple)types. There is one type-schema document per XSD namespace, one XSD namespace per UML package.
  • xslt/: contains XSLT scripts that were used to generate the HTML, XSD and TAP documents from the UML model. They are here for informational purposes, and are not part of the specification. The build.xml ANT script in uml/ contains tasks for creating these documents.

Other pages on the IVOA Wiki pertaining to this specification are

Added:
>
>
 
  • page describing why we think SimDB development needs explicit input from different working groups.

-- GerardLemson - 13 Mar 2009
-- HerveWozniak - 23 Jun 2008


<--  
-->

Revision 82009-05-04 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"

SimDB = Simulation Database

SimDB is a specification for a Simulation Database. A SimDB implementation contains a database with (meta-)data describing simulations, their results, their provenance and various characteristics. The simulations are supposed to be those that produce a representation of 3+1D space, sometimes called "cosmological simulations", though they can be of any scale, from large scale structure of the universe down to solar systems. It has been a point of discussion whether we should open the spec up for all, or at least more types of simulations. This is an open issue. A SimDB also contains various types of post-processing products, as well as meta data identifying web services giving access to these simulations. The latter may, but are not restricted to SimDAP services.

The SimDB specification defines a protocol for an online service for querying and some management of this database. It has two components. One is a specialised TAP service, the other is a REST-like GET protocol to retrieve complete descriptions in XML form. Both of these are based on a data model for simulations, which is also part of this specification.

The full specification consists of a number of different documents. The latest versions of these as well as earlier ones, can be found in the specification directory under the theory/snapdm section of Norman Gray's Volute project on GoogleCode.

The theory/snapdmsection contains a lot more material than the specification alone. Most of this is the result of a project to create a demonstrator proto-type for the SimDB project. That project is in the process of being ported to the VO-URP project.

For the purpose of this specification one need only consult the specification sub directory. It contains the following documents:

  • SimDB-note.doc: the Note describing SimDB, should be turned into a working draft at some point in the hopefully near future.
  • uml/SimDB_DM.xml: XMI document containing the UML data model on which the spec is based. Created by the 12.1 version of the community edition of MagicDraw UML drawing tool.
  • uml/SimDB_DM_INTERMEDIATE.xml: an XML document containing the so called "intermediate representation" of the data model. This is derived from the XMI model and is (much) easier to read and handle.
  • html/SimDB.html: HTML documentation fo rthe datamodel. Fully crosslinked and documented. Contains also the UTYPEs for the data model elements.
  • tap/SimDB_vodataservice.xml: XML document creating the TAP metadata for the SimDB database as a VODataservice.
  • tap/SimDB_tap_tableset.xml: XMl document containing the TAP metadata for the SimDB database as an "empty" VOTable (i.e. a TABLE for each public table, with FIELDs but no DATA)
  • xsd/: XML Schema files that defines how instances of the data model can be presented in XML.
    • xsd/SimDB_root.xsd: the "element" part of the SimDB schema set. It contains the valid root elements, i.e. the ones with which documents can be made. It depends on "type-schemas" that are all imported by this schema.
    • base.xsd: a schema defining some base types for use by other type definitions in the schema set.
    • The other XSD files in xsd/ and xsd/simdb/ and sub-directories define the (complex and simple)types. There is one type-schema document per XSD namespace, one XSD namespace per UML package.
  • xslt/: contains XSLT scripts that were used to generate the HTML, XSD and TAP documents from the UML model. They are here for informational purposes, and are not part of the specification. The build.xml ANT script in uml/ contains tasks for creating these documents.

Other pages on the IVOA Wiki pertaining to this specification are

Deleted:
<
<
  • page Table with (possible) discussions points and issues.
 

-- GerardLemson - 13 Mar 2009
-- HerveWozniak - 23 Jun 2008


<--  
-->

Revision 72009-04-30 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"

SimDB = Simulation Database

SimDB is a specification for a Simulation Database. A SimDB implementation contains a database with (meta-)data describing simulations, their results, their provenance and various characteristics. The simulations are supposed to be those that produce a representation of 3+1D space, sometimes called "cosmological simulations", though they can be of any scale, from large scale structure of the universe down to solar systems. It has been a point of discussion whether we should open the spec up for all, or at least more types of simulations. This is an open issue. A SimDB also contains various types of post-processing products, as well as meta data identifying web services giving access to these simulations. The latter may, but are not restricted to SimDAP services.

The SimDB specification defines a protocol for an online service for querying and some management of this database. It has two components. One is a specialised TAP service, the other is a REST-like GET protocol to retrieve complete descriptions in XML form. Both of these are based on a data model for simulations, which is also part of this specification.

The full specification consists of a number of different documents. The latest versions of these as well as earlier ones, can be found in the specification directory under the theory/snapdm section of Norman Gray's Volute project on GoogleCode.

The theory/snapdmsection contains a lot more material than the specification alone. Most of this is the result of a project to create a demonstrator proto-type for the SimDB project. That project is in the process of being ported to the VO-URP project.

For the purpose of this specification one need only consult the specification sub directory. It contains the following documents:

  • SimDB-note.doc: the Note describing SimDB, should be turned into a working draft at some point in the hopefully near future.
  • uml/SimDB_DM.xml: XMI document containing the UML data model on which the spec is based. Created by the 12.1 version of the community edition of MagicDraw UML drawing tool.
  • uml/SimDB_DM_INTERMEDIATE.xml: an XML document containing the so called "intermediate representation" of the data model. This is derived from the XMI model and is (much) easier to read and handle.
  • html/SimDB.html: HTML documentation fo rthe datamodel. Fully crosslinked and documented. Contains also the UTYPEs for the data model elements.
  • tap/SimDB_vodataservice.xml: XML document creating the TAP metadata for the SimDB database as a VODataservice.
  • tap/SimDB_tap_tableset.xml: XMl document containing the TAP metadata for the SimDB database as an "empty" VOTable (i.e. a TABLE for each public table, with FIELDs but no DATA)
  • xsd/: XML Schema files that defines how instances of the data model can be presented in XML.
    • xsd/SimDB_root.xsd: the "element" part of the SimDB schema set. It contains the valid root elements, i.e. the ones with which documents can be made. It depends on "type-schemas" that are all imported by this schema.
    • base.xsd: a schema defining some base types for use by other type definitions in the schema set.
    • The other XSD files in xsd/ and xsd/simdb/ and sub-directories define the (complex and simple)types. There is one type-schema document per XSD namespace, one XSD namespace per UML package.
  • xslt/: contains XSLT scripts that were used to generate the HTML, XSD and TAP documents from the UML model. They are here for informational purposes, and are not part of the specification. The build.xml ANT script in uml/ contains tasks for creating these documents.

Other pages on the IVOA Wiki pertaining to this specification are

Added:
>
>
  • page Table with (possible) discussions points and issues.
 

-- GerardLemson - 13 Mar 2009
-- HerveWozniak - 23 Jun 2008


<--  
-->

Revision 62009-04-08 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"

SimDB = Simulation Database

Deleted:
<
<
 
Added:
>
>
SimDB is a specification for a Simulation Database. A SimDB implementation contains a database with (meta-)data describing simulations, their results, their provenance and various characteristics. The simulations are supposed to be those that produce a representation of 3+1D space, sometimes called "cosmological simulations", though they can be of any scale, from large scale structure of the universe down to solar systems. It has been a point of discussion whether we should open the spec up for all, or at least more types of simulations. This is an open issue. A SimDB also contains various types of post-processing products, as well as meta data identifying web services giving access to these simulations. The latter may, but are not restricted to SimDAP services.
 
Added:
>
>
The SimDB specification defines a protocol for an online service for querying and some management of this database. It has two components. One is a specialised TAP service, the other is a REST-like GET protocol to retrieve complete descriptions in XML form. Both of these are based on a data model for simulations, which is also part of this specification.
 
Added:
>
>
The full specification consists of a number of different documents. The latest versions of these as well as earlier ones, can be found in the specification directory under the theory/snapdm section of Norman Gray's Volute project on GoogleCode.
 
Changed:
<
<

abstract

>
>
The theory/snapdmsection contains a lot more material than the specification alone. Most of this is the result of a project to create a demonstrator proto-type for the SimDB project. That project is in the process of being ported to the VO-URP project.
Deleted:
<
<
We have (since Jan 2008) 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.
 
Changed:
<
<
SimDB is a specification for a Simulation (meta-)Database (could be called Simulation Registry, -Portal).
>
>
For the purpose of this specification one need only consult the specification sub directory. It contains the following documents:
 
Deleted:
<
<
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.

To be continued ...

SimDB on Volute

Most developments of SimDB have been performed on the GoogleCode subversion repository of Norman Gray's Volute project.

The documents that will form part of the specification will whilst under development be put in the specification sub directory. Here we describe its contents.

 
  • SimDB-note.doc: the Note describing SimDB, should be turned into a working draft at some point in the hopefully near future.
  • uml/SimDB_DM.xml: XMI document containing the UML data model on which the spec is based. Created by the 12.1 version of the community edition of MagicDraw UML drawing tool.
  • uml/SimDB_DM_INTERMEDIATE.xml: an XML document containing the so called "intermediate representation" of the data model. This is derived from the XMI model and is (much) easier to read and handle.
  • html/SimDB.html: HTML documentation fo rthe datamodel. Fully crosslinked and documented. Contains also the UTYPEs for the data model elements.
  • tap/SimDB_vodataservice.xml: XML document creating the TAP metadata for the SimDB database as a VODataservice.
  • tap/SimDB_tap_tableset.xml: XMl document containing the TAP metadata for the SimDB database as an "empty" VOTable (i.e. a TABLE for each public table, with FIELDs but no DATA)
  • xsd/: XML Schema files that defines how instances of the data model can be presented in XML.
Changed:
<
<
    • base.xsd: a schema defining some base types for use by other type definitions in the schema set.
    • xsd/SimDB_root.xsd: the "element" part of the SimDB schema set. It contains the valid root elements, i.e. the ones with which documents can be made.
    • The other XSD files in xsd/ and xsd/simdb/ define the types.
>
>
    • xsd/SimDB_root.xsd: the "element" part of the SimDB schema set. It contains the valid root elements, i.e. the ones with which documents can be made. It depends on "type-schemas" that are all imported by this schema.
    • base.xsd: a schema defining some base types for use by other type definitions in the schema set.
    • The other XSD files in xsd/ and xsd/simdb/ and sub-directories define the (complex and simple)types. There is one type-schema document per XSD namespace, one XSD namespace per UML package.
Added:
>
>
  • xslt/: contains XSLT scripts that were used to generate the HTML, XSD and TAP documents from the UML model. They are here for informational purposes, and are not part of the specification. The build.xml ANT script in uml/ contains tasks for creating these documents.

Other pages on the IVOA Wiki pertaining to this specification are

  -- GerardLemson - 13 Mar 2009
-- HerveWozniak - 23 Jun 2008


<--  
-->

Revision 52009-03-13 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"

SimDB = Simulation Database

Added:
>
>

abstract

 We have (since Jan 2008) 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.

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.

To be continued ...

Added:
>
>

SimDB on Volute

Most developments of SimDB have been performed on the GoogleCode subversion repository of Norman Gray's Volute project.

The documents that will form part of the specification will whilst under development be put in the specification sub directory. Here we describe its contents.

  • SimDB-note.doc: the Note describing SimDB, should be turned into a working draft at some point in the hopefully near future.
  • uml/SimDB_DM.xml: XMI document containing the UML data model on which the spec is based. Created by the 12.1 version of the community edition of MagicDraw UML drawing tool.
  • uml/SimDB_DM_INTERMEDIATE.xml: an XML document containing the so called "intermediate representation" of the data model. This is derived from the XMI model and is (much) easier to read and handle.
  • html/SimDB.html: HTML documentation fo rthe datamodel. Fully crosslinked and documented. Contains also the UTYPEs for the data model elements.
  • tap/SimDB_vodataservice.xml: XML document creating the TAP metadata for the SimDB database as a VODataservice.
  • tap/SimDB_tap_tableset.xml: XMl document containing the TAP metadata for the SimDB database as an "empty" VOTable (i.e. a TABLE for each public table, with FIELDs but no DATA)
  • xsd/: XML Schema files that defines how instances of the data model can be presented in XML.
    • base.xsd: a schema defining some base types for use by other type definitions in the schema set.
    • xsd/SimDB_root.xsd: the "element" part of the SimDB schema set. It contains the valid root elements, i.e. the ones with which documents can be made.
    • The other XSD files in xsd/ and xsd/simdb/ define the types.

-- GerardLemson - 13 Mar 2009

 -- HerveWozniak - 23 Jun 2008


<--  
-->

Revision 42009-03-13 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"

SimDB = Simulation Database

Added:
>
>
 
  • page describing why we think SimDB development needs explicit input from different working groups.
Changed:
<
<
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.
>
>
We have (since Jan 2008) 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.
  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.

To be continued ...

-- HerveWozniak - 23 Jun 2008


<--  
-->

Revision 32009-03-12 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"

SimDB = Simulation Database

  • page describing why we think SimDB development needs explicit input from different working groups.

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.

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.

Changed:
<
<
>
>
To be continued ...
 

-- HerveWozniak - 23 Jun 2008


<--  
-->

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-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback