/[volute]/trunk/projects/theory/snapdm/doc/note/SimDB-note.html
ViewVC logotype

Diff of /trunk/projects/theory/snapdm/doc/note/SimDB-note.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 263 by gerard.lemson, Wed Apr 23 05:36:27 2008 UTC revision 264 by gerard.lemson, Thu Apr 24 06:34:40 2008 UTC
# Line 333  Line 333 
333  </ul>  </ul>
334  <br/>  <br/>
335    
336  <h2><a name="sec3">3. Data modelling</a></h2>  <h2><a name="sec3">3. Approach</a></h2>
337  <p>We describe our modelling approach here. The actual models and their physical representations are provided using links  <p>We describe our approach to developing the various products of the SimDB specification.
338  to their location in an SVN repository under Google Code.</p>  </p>
339    
340  <h3><a name="sec3.1">3.1 The <i>universe of discourse</i></a></h3>  <h3><a name="sec3.1">3.1 The <i>universe of discourse</i></a></h3>
341  <p>  <p>
# Line 374  Line 374 
374  <li>How were initial conditions created, what parameters?</li>  <li>How were initial conditions created, what parameters?</li>
375  </ul>  </ul>
376  </p>  </p>
377    <h3><a name="profile"/>3.2 UML</h3>
378    @@TODO Gerard@@
379    
380    <h4>3.2.1 IVOA UML Profile</h4>
381    <h4>3.2.2 XMI</h4>
382    
383    
384    <h3>3.3 Serialisations</h3>
385    @@ TODO Gerard @@
386    <h4>3.3.1 Relational mapping</h4>
387    <h4>3.3.2 XML schema</h4>
388    
389    <h3>3.4 XSLT pipeline</h3>
390    @@ TODO Laurent @@
391    
392    
393  <h2>4. Architecture of the SimDB</h2>  <br /><h2>4. Results</h2>
394  <h3><a name="profile"/>4.0 IVOA UML profile</h3>  <p>
395  @@TODO ...@@  The actual models and their physical representations are provided using links
396  <h3><a name="analysis"/>4.1 analysis model</h3>  to their location in an SVN repository under Google Code.
397    </p>
398    <h3><a name="analysis"/>4.1 Analysis model</h3>
399  The analysis model is an abstract representation of the <a href="#sec3.1">universe of discourse</a> (UoD).  The analysis model is an abstract representation of the <a href="#sec3.1">universe of discourse</a> (UoD).
400  It is a UML model, with emphasis on the concepts and their relationships in the UoD, less on details  It is a UML model, with emphasis on the concepts and their relationships in the UoD, less on details
401  such as attributes. @@TODO create a version and add it to volute@@.  such as attributes. @@TODO create a version and add it to volute@@.
402  <h3><a name="logical"/>4.2 logical data model</h3>  <h3><a name="logical"/>4.2 SimDB logical data model</h3>
403    <p>
404  The logical data model is a fully detailed model of the application domain.  The logical data model is a fully detailed model of the application domain.
405  It is represented as a set of UML diagrams, which we created using MagicDraw Community Edition 12.1 and stored as an  It is represented as a set of UML diagrams, which we created using MagicDraw Community Edition 12.1 and stored as an
406  XMI file in the GoogleCode  XMI file in the GoogleCode
# Line 390  Line 408 
408  SNAP_Simulation_DM.xml</a> @@TODO should change all occurrences of names with SNAP to using SimDB?@@  SNAP_Simulation_DM.xml</a> @@TODO should change all occurrences of names with SNAP to using SimDB?@@
409  JPG representations of the model can be found in <a href="http://volute.googlecode.com/svn/trunk/projects/theory/snapdm/input/images/">this</a>  JPG representations of the model can be found in <a href="http://volute.googlecode.com/svn/trunk/projects/theory/snapdm/input/images/">this</a>
410  directory. @@TODO find proper representation image of the complete model. Possibly color packages differently.@@  directory. @@TODO find proper representation image of the complete model. Possibly color packages differently.@@
411    </p>
412  <h3><a name="intermediate"/>4.3 intermediate representation</h3>@@TODO find a different name@@  <h3><a name="intermediate"/>4.3 Intermediate representation</h3>@@TODO find a different name@@
413  <br />  <br />
414  We introduce our own XML format, defined by the XML schema in  We introduce our own XML format, defined by the XML schema in
415  <a href="http://volute.googlecode.com/svn/trunk/projects/theory/snapdm/res/intermediateModel.xsd">intermediateModel.xsd</a>,  <a href="http://volute.googlecode.com/svn/trunk/projects/theory/snapdm/res/intermediateModel.xsd">intermediateModel.xsd</a>,
# Line 408  Line 426 
426  dialects of XMI. Another reason for this representation is that XMI is a rather complex representation of a UML  dialects of XMI. Another reason for this representation is that XMI is a rather complex representation of a UML
427  model. Since we are using a rather restricted <a href="#profile">profile</a> we do not need this generality, and  model. Since we are using a rather restricted <a href="#profile">profile</a> we do not need this generality, and
428  this allows us to represent the model using XML documents that are much easier to handle with XSLT.  this allows us to represent the model using XML documents that are much easier to handle with XSLT.
429  <h3><a name="relationalschema"/>Relational schema</h3>  <h3><a name="relationalschema"/>4.4 Relational schema</h3>
430  <h3><a name="xmlschema"/>XML schema</h3>  <h3><a name="xmlschema"/>4.5 XML schema</h3>
431  <h3><a name="xhtml"/>XHTML</h3>  <h3><a name="xhtml"/>4.6 XHTML</h3>
432  <h3>Java: JPA+JAXB</h3>  <h3>4.7 Java: JPA+JAXB</h3>
   
433    
434    
435    <h2>5. Reference implementations</h2>
436    <h3>5.1 France</h3>
437    @@ TODO Laurent @@
438    <h3>5.2 Germany</h3>
439    @@ TODO Gerard @@
440    <h3>5.3 Italy</h3>
441    @@ TODO Patrizia @@
442    <h3>5.4 USA</h3>\
443    @@ TODO Rick @@
444  <br/>  <br/>
445  <h2><a name="references">References</a></h2>  <h2><a name="references">References</a></h2>
446    

Legend:
Removed from v.263  
changed lines
  Added in v.264

msdemlei@ari.uni-heidelberg.de
ViewVC Help
Powered by ViewVC 1.1.26