IVOA, Trieste, DM 2008-05-22Gerard Lemson SimDB Data Model IVOA interop, DM WG session Trieste,...
-
Upload
gilbert-hutchinson -
Category
Documents
-
view
216 -
download
0
Transcript of IVOA, Trieste, DM 2008-05-22Gerard Lemson SimDB Data Model IVOA interop, DM WG session Trieste,...
IVOA, Trieste, DM 2008-05-22 Gerard Lemson
SimDB Data Model
IVOA interop, DM WG session Trieste, 2008-05-22
IVOA, Trieste, DM 2008-05-22 Gerard Lemson
“tiger team” Laurent Bourges Gerard Lemson Rick Wagner
Claudio Gheller Mireille Louys Patrizia Manzato Herve Wozniak
Ackn: Ugo Becciani, Jeremy Blaizot, Francois Bonnarel, Igor
Chillingarian, Norman Gray, Jaiwon Kim, Franck LePetit, Alex Szalay
IVOA, Trieste, DM 2008-05-22 Gerard Lemson
What is SimDB ? = “Simulation Database”
- registry ? - portal ?
Online service for discovering and accessing numerical simulations
Exposes a relational database containing metadata describing simulations
Focused on “3+1D simulations” Provides for XML representation Defines access protocols for online access to
the database: put/get/query
IVOA, Trieste, DM 2008-05-22 Gerard Lemson
SimDBADQL
VOTable query
putSimDB/XML
1
2
getsimdbId(=ivoID?)
SimDB/XML
3
SimDB architecture (schematic)
IVOA, Trieste, DM 2008-05-22 Gerard Lemson
SimDB use cases Management of institute’s simulation
resources San Diego (legacy) Trieste (legacy) Catania Horizon (Lyon (reference), Paris) MPA (reference)
Publication of resources local/remote (ala registry) generate metadata in simulation pipe line
Link resources to (SimDAP) services theory session 11AM
IVOA, Trieste, DM 2008-05-22 Gerard Lemson
SimDB/RDB
Why Relational Database? because we have a complex, normalised
model for which we need an expressive query
language and the IVOA has such a language
(ADQL) which is relational
(ref Will O’Mullane, 2003)
IVOA, Trieste, DM 2008-05-22 Gerard Lemson
SimDB/XML
Why custom XML (and not VOTable) ? because we have a complex, highly
hierarchical model and because it is the (IVOA)
mandated language for expressing such complex resources
IVOA, Trieste, DM 2008-05-22 Gerard Lemson
SimDB/DM = UML2 Why UML?
because it is the de facto standard for data models,
with free tool support and a standard XML representation (XMI) with standardised extension and specialisation
mechanisms (Profiles) because it is highly expressive and
implementation neutral and because it is the adopted IVOA DM WG
standard for expressing data models (Cambridge 2003)
IVOA, Trieste, DM 2008-05-22 Gerard Lemson
And because we can generate all the other representations from it!
RDB schema XML schema UTYPE-s TAP metadata
tap_schema tableset VODataService
Java/JPA+JAXB HTML .........
See tomorrow’s DM session (GL + Laurent Bourges)
IVOA, Trieste, DM 2008-05-22 Gerard Lemson
SimDB links Development completely open:
http://volute.googlecode.com/svn/trunk/projects/theory/snapdm/
UML: XMI: input/SimDB_DM.xml images : input/images/
representations, “physical models” (auto-generated): “intermediate representation” output/SimDB_DM_INTERMEDIATE.xml RDB: output/ddl/ XML schema: output/schema/ HTML: output/html/ (with UTYPEs) TAP: output/tap/ Java: output/java/
Documentation Note (HTML): doc/note/SimDB-note.html
first draft, in need of updates after this week
IVOA, Trieste, DM 2008-05-22 Gerard Lemson
SimDB/DM elements Packages
simdb (root) object protocol experiment project
Resource Protocol Experiment Project
IVOA, Trieste, DM 2008-05-22 Gerard Lemson
SimDB/DM elements ObjectType
TargetObjectType, TargetProcess, RepresentationObjectType
Property property group
Snapshot ObjectCollection Characterisation
Webservice (link to SimDAP)
IVOA, Trieste, DM 2008-05-22 Gerard Lemson
SimDB/DM issues Profile Normalisation level, e.g.
Experiment —> Protocol ParameterSetting —> InputParameter
Semantic vocabularies Quantity (i.e. units)
value/unit conversion factor to standard (per physical
quantity) ? Representing references others ??
IVOA, Trieste, DM 2008-05-22 Gerard Lemson
SimDB future Move to recommendation track cross-WG Focus Group
Members from current tiger team + DM, Registry, Semantics, DAL/TAP
Formal details in discussion in exec (I hope).
More via email.