MicrosimulationsS3 (Simple Self-described Service protocol)S3 follows the same dialog philosophy already present in TSAP (see below) but allowing more flexible implementations not only for theoretical spectra but also for other kind of theoretical data.General information
Model services using S3S3 metadata interface to the models: (links point to the first S3 dialog step: the format=metadata one. Subsequent queries can be made using this information)
Applications using S3
TSAP (SSAP theory use case)The first attempt (as an ESAVO-SVO collaboration) to define such a protocol was TSAP (Theory Simple Access Protocol), designed to access theoretical spectra. Now TSAP is part of the SSAP protocol as a Use Case.General information about TSAP
Model services using TSAP
Applications using TSAP
| |||||||||||
Changed: | |||||||||||
< < |
| ||||||||||
> > |
| ||||||||||
|
MicrosimulationsS3 (Simple Self-described Service protocol)S3 follows the same dialog philosophy already present in TSAP (see below) but allowing more flexible implementations not only for theoretical spectra but also for other kind of theoretical data.General information
Model services using S3S3 metadata interface to the models: (links point to the first S3 dialog step: the format=metadata one. Subsequent queries can be made using this information)
Applications using S3
TSAP (SSAP theory use case)The first attempt (as an ESAVO-SVO collaboration) to define such a protocol was TSAP (Theory Simple Access Protocol), designed to access theoretical spectra. Now TSAP is part of the SSAP protocol as a Use Case.General information about TSAP
Model services using TSAP
Applications using TSAP
| |||||||||||
Changed: | |||||||||||
< < | |||||||||||
> > |
| ||||||||||
Added: | |||||||||||
> > |
| ||||||||||
<--
|
MicrosimulationsS3 (Simple Self-described Service protocol)S3 follows the same dialog philosophy already present in TSAP (see below) but allowing more flexible implementations not only for theoretical spectra but also for other kind of theoretical data.General information
Model services using S3 | ||||||||
Added: | ||||||||
> > | S3 metadata interface to the models: (links point to the first S3 dialog step: the format=metadata one. Subsequent queries can be made using this information) | |||||||
Changed: | ||||||||
< < |
| |||||||
> > | ||||||||
Added: | ||||||||
> > |
Applications using S3
| |||||||
TSAP (SSAP theory use case)The first attempt (as an ESAVO-SVO collaboration) to define such a protocol was TSAP (Theory Simple Access Protocol), designed to access theoretical spectra. Now TSAP is part of the SSAP protocol as a Use Case.General information about TSAP
Model services using TSAP
Applications using TSAP
<--
|
MicrosimulationsIt is not so well defined to what we call "Microsimulations". In a way, it is was first used as opposed to "cosmological simulations" (macrosimulations). In fact, we tend to use that word to include any theoretical model that is simple enough so that it does not need a complex schema as that of SimDB/SimDAP to be incorporated in the VO framework. In other words, we want to define a simple protocol so that theoretical models can be included in the VO. Those models that can be implemented with this simple protocol are, in that sense, "microsimulations". | ||||||||
Added: | ||||||||
> > |
S3 (Simple Self-described Service protocol)S3 follows the same dialog philosophy already present in TSAP (see below) but allowing more flexible implementations not only for theoretical spectra but also for other kind of theoretical data.General information
Model services using S3
| |||||||
TSAP (SSAP theory use case)The first attempt (as an ESAVO-SVO collaboration) to define such a protocol was TSAP (Theory Simple Access Protocol), designed to access theoretical spectra. Now TSAP is part of the SSAP protocol as a Use Case.General information about TSAP
Model services using TSAP | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Applications using TSAP
| ||||||||
Deleted: | ||||||||
< < |
S3 (Simple Self-described Service protocol)S3 follows the same dialogue philosophy already present in TSAP but allowing more flexible implementations not only for theoretical spectra but also for other kind of theoretical data. more information:
| |||||||
<--
|
Microsimulations | ||||||||
Added: | ||||||||
> > | ||||||||
It is not so well defined to what we call "Microsimulations".
In a way, it is was first used as opposed to "cosmological simulations" (macrosimulations).
In fact, we tend to use that word to include any theoretical model that is simple enough so that it does not need a complex schema as that of SimDB/SimDAP to be incorporated in the VO framework.
In other words, we want to define a simple protocol so that theoretical models can be included in the VO. Those models that can be implemented with this simple protocol are, in that sense, "microsimulations".
TSAP (SSAP theory use case) | ||||||||
Changed: | ||||||||
< < | The first attempt to define such a protocol was TSAP (Theory Simple Access Protocol), designed to access theoretical spectra. Now TSAP is part of the SSAP protocol as a Use Case. | |||||||
> > | The first attempt (as an ESAVO-SVO collaboration) to define such a protocol was TSAP (Theory Simple Access Protocol), designed to access theoretical spectra. Now TSAP is part of the SSAP protocol as a Use Case. | |||||||
Changed: | ||||||||
< < | General information about TSAP: | |||||||
> > | General information about TSAP | |||||||
| ||||||||
Changed: | ||||||||
< < | Model services using TSAP: | |||||||
> > | Model services using TSAP | |||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > |
Applications using TSAP
| |||||||
S3 (Simple Self-described Service protocol)S3 follows the same dialogue philosophy already present in TSAP but allowing more flexible implementations not only for theoretical spectra but also for other kind of theoretical data. more information:
<--
|
MicrosimulationsIt is not so well defined to what we call "Microsimulations". In a way, it is was first used as opposed to "cosmological simulations" (macrosimulations). In fact, we tend to use that word to include any theoretical model that is simple enough so that it does not need a complex schema as that of SimDB/SimDAP to be incorporated in the VO framework. In other words, we want to define a simple protocol so that theoretical models can be included in the VO. Those models that can be implemented with this simple protocol are, in that sense, "microsimulations".TSAP (SSAP theory use case) | ||||||||
Added: | ||||||||
> > | ||||||||
The first attempt to define such a protocol was TSAP (Theory Simple Access Protocol), designed to access theoretical spectra. Now TSAP is part of the SSAP protocol as a Use Case. | ||||||||
Changed: | ||||||||
< < | more information: | |||||||
> > | General information about TSAP: | |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
Model services using TSAP:
| |||||||
Added: | ||||||||
> > | ||||||||
S3 (Simple Self-described Service protocol)S3 follows the same dialogue philosophy already present in TSAP but allowing more flexible implementations not only for theoretical spectra but also for other kind of theoretical data. more information:
<--
|
| ||||||||
Deleted: | ||||||||
< < | ||||||||
MicrosimulationsIt is not so well defined to what we call "Microsimulations". In a way, it is was first used as opposed to "cosmological simulations" (macrosimulations). In fact, we tend to use that word to include any theoretical model that is simple enough so that it does not need a complex schema as that of SimDB/SimDAP to be incorporated in the VO framework. In other words, we want to define a simple protocol so that theoretical models can be included in the VO. Those models that can be implemented with this simple protocol are, in that sense, "microsimulations".TSAP (SSAP theory use case)The first attempt to define such a protocol was TSAP (Theory Simple Access Protocol), designed to access theoretical spectra. Now TSAP is part of the SSAP protocol as a Use Case. more information:
| ||||||||
Added: | ||||||||
> > |
| |||||||
S3 (Simple Self-described Service protocol)S3 follows the same dialogue philosophy already present in TSAP but allowing more flexible implementations not only for theoretical spectra but also for other kind of theoretical data. more information:
<--
|
MicrosimulationsIt is not so well defined to what we call "Microsimulations". In a way, it is was first used as opposed to "cosmological simulations" (macrosimulations). In fact, we tend to use that word to include any theoretical model that is simple enough so that it does not need a complex schema as that of SimDB/SimDAP to be incorporated in the VO framework. In other words, we want to define a simple protocol so that theoretical models can be included in the VO. Those models that can be implemented with this simple protocol are, in that sense, "microsimulations".TSAP (SSAP theory use case)The first attempt to define such a protocol was TSAP (Theory Simple Access Protocol), designed to access theoretical spectra. Now TSAP is part of the SSAP protocol as a Use Case. more information:
S3 (Simple Self-described Service protocol)S3 follows the same dialogue philosophy already present in TSAP but allowing more flexible implementations not only for theoretical spectra but also for other kind of theoretical data. more information:
<--
|