(back to main)


SimDB is based on a data model. Data models are supposed to be represented in UML and be accompanied by an XML schema. In SimDB we propose the following usage for this schema
  • Defines valid SimDB/XML documents.
  • Such documents can be retrieved upon a simple GET request (format to be decided) for single (or multiple?), identified SimDB/Resource(-s).
  • Such documents MAY be used if a SimDB instance allows upload/insertion of SimDB/Resource-s.


Issue to be discussed:
  • Only concrete (i.e. non-abstract) root entity classes mapped to root elements
  • use of predefined base.xsd
  • each package mapped to own XML doc with own targetnamespace
  • identifiers structured
    • database id (a long)
    • ivoIdentifier
    • xml ID (for references internal to doc)
    • ?publisherDID?
  • references mapped to element containing just an identifier
  • ...

Comment: Priorities

In order to keep up the progress on SimDB becoming a recommendation, the ReST interface is secondary to finalizing the data model and mapping it onto a TAP service. I think we should set this topic aside until we have some SimDB services implemented. If users start to query the databases, they may begin asking for a common mechanism to add metadata about their simulations. This would be the point to finalize the ReST interface.

-- RickWagner - 19 May 2009

(back to main)

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