Difference: IVOATheorySimDBREST (1 vs. 5)

Revision 52012-06-26 - root

 
META TOPICPARENT name="IVOATheorySimDB"
(back to main)

SimDB/REST

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.

TODO

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)

Revision 42009-05-19 - RickWagner

 
META TOPICPARENT name="IVOATheorySimDB"
(back to main)

SimDB/REST

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.

TODO

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
  • ...
Added:
>
>

Comment: Priorities

 
Added:
>
>
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.
 
Changed:
<
<
>
>
-- RickWagner - 19 May 2009
 
(back to main)
<--  
-->

Revision 32009-05-19 - GerardLemson

 
META TOPICPARENT name="IVOATheorySimDB"
Added:
>
>
(back to main)
 

SimDB/REST

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.

TODO

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
  • ...


Added:
>
>
(back to main)
 
<--  
-->

Revision 22009-05-12 - GerardLemson

 
META TOPICPARENT name="IVOATheorySimDB"
Deleted:
<
<
 

SimDB/REST

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.
Changed:
<
<
>
>

TODO

Added:
>
>
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
  • ...
 


<--  
-->

Revision 12009-05-12 - GerardLemson

 
META TOPICPARENT name="IVOATheorySimDB"

SimDB/REST

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.


<--  
-->
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback