We aim to construct a specification (SimDB) for a protocol enabling discovering and accessing interesting simulations.

Approach

  • We build this spec around a data model describing simulations, i.e. a meta-data model.
  • We start with an abstract, application independent model (domain momdel or analysis model)
    • Following "standard" modelling apporaches: analysis -> logical -> physical
  • MAYBE we derive from the domain model a separate applicationd dependent, logical model (currently logical and domain model are the same)
  • SimDB/DM is designed in UML
    • UML is stored in XMI
    • Model is drawn using MagicDraw Community Edition 12.1 and stored in its XMI format
    • We follow a predefined UML profile
    • The particular profile can be found here
      • ALso in appendix to the Note
    • Profile is mapped to "intermediate representation", XML schema file intermediateModel.xsd
    • UML aims to be comprehensive, i.e. contains all documentation etc.
  • We use the (intermediate representation of the) (logical) model to derive physical representations that can be used in implementations:
    • A relational schema, basis for a specialised TAP protocol
      • we use object-relational mapping rules (implemented in an XSLT script) to derive the relational schema directly from the UML
      • ISSUES
        • treatment of inheritance hierarchies
    • An XML schema (actually a set of XML schema documents), defining valaid SimDB/XML documents
      • We use mapping rules to derive the XML schema directly from the UML. rules similar to those used in registry/VOTable schemas.
      • ISSUES
        • Mapping references.
    • an [[][HTML document]], for human consumption
    • a list of UTYPEs, to be used for example in VOTable results of ADQL queries to SimDB/TAP
      • we use rules to derive the UTYPEs directly from the UML
      • the UTYPEs are defined in the HTML document

Contents of model.

  • Model in http://volute.googlecode.com/svn/trunk/projects/theory/snapdm/specification/uml/SimDB_DM.xml
  • Use of packages: simdb, protocol, experiment, object, dal
  • Anchored in Resource, base class of Experiment_(_Simulation,_PostProcessing_), Protocol (Simulator,_PostProcessor_), Project, WebService
    • NB to Registry+DM: SimDB/Resource similar to, but not identical with Resource Model's Resource. Some of them (Protocol, Project, WebService, some Experiments) could be Registry/Resources as well. We propose to create particular representations of these in terms of the Resource data model.

Usage of model


Edit | Attach | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2009-05-03 - GerardLemson
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback