Difference: IVOATheorySimDBDM (1 vs. 27)

Revision 272012-06-26 - root

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, whilst older versions are under the input/ directory, such as version r902. I will try to keep track of the different versions and change logs below. At the bottom of the page the generated GraphViz image representing the last (checked in) version of the model. (NB need to ensure it is in synch with the actual model).

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation, provenance etc (see separate page)
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


Version history (link on heading):

Sometimes versions do not change in content, but nevrtheless produce different MagicDraw XMI documents. Sometimes this is due to different drawing, redrawing links or something like that. Here I only indicate the content that was changed. This I do by generating the SimDB_INTERMEDIATE.xml file and diffing those. Note, at the end there is a diff between the current specification model and amodel on VO-URP/input/simdb.

specification/

under construction
  • Updated descriptions.
  • Rename the enumeration CharacterisationType to Statistic. Rename the 'type' attribute on Characterisation to 'statistic'.

1139

1089

  • Changed cardinality of snapshot collection on Experiment. now 0..*
  • a datatype StringLiteral was added. not really useful remnant of some experimenting. can be removed.
  • Changed cardinality of representationObject collection on experiment. now 0..*
  • Changed cardinality of objectCollecitoncollection on Snapshot. now 0..*
  • Changed cardianlity of label attribute on ValidValue, from 1 to 0..1
1059
  • Added option to refer to an external utype for each <>. Added one on Resource: otherutype="Reg:VOResource"
1034
  • removed explicit dependency between simdb and IVOAValueTYpes packages again [this is all mainly caused by changes in how to represent explicitly how a model depends on the profile. Is an explict dependency required or not.
  • PostProcessing no longer abstract.

1029

  • no change in content.

1020

  • Added Identity datatype to the IVOAValueTypes. [check whether this is necessray in the model or only for code generation?]
  • Recreated the explicit dependency relation between the "simdb" and IVOAValueTypes" packages.
  • Fixed the errors on Contact introduced in 898.

1012

  • Removed the "model" package. This was used for code generation purposes only.

989

978

  • No change in content

952

  • Exact copy of, i.e. no change wrt prop-952

prop-951 (Mar 12, 2009 ,derived from input/902 !)

input/

1025

902

887

VO-URP

<VO-URP>/input/simdb/SimDB_DM.xml 458 (diff with volute v1089
  • Add "basic" package, holding on to basic datatypes such as Quantity, Value, Cardinality, DataType.
  • All other packages depend on it. [this is somewhat ugly and required by a problem of the current generation framework (i.e. VO-URP), which does not yet allow "inheriting" dependencies from parent to child packages. Only simdb needs otherwise have this relation. Currently it is required so that appropriate import statements will be generated on XML schemas.]
  • Renamed Characterisation -> Statistics ["innocent name change" ?]
  • Renamed CharacterisationType -> Statistic [possibility for confusion with Statistics].
  • Renamed "characterisation" collection on ObjectCollection to "statistics".
  • Introduced Value datatype, representing values of either numeric or unknown datatype. Both represented by an attribute of type Quantity, reps string. [NB this is still far from ideal! But more useful model seems impossible for now as we simply can not know the datatype of parameter values in the model! S3 might present a method to design protocols that can work around this feature of the model, at the cost of only allowing access to experiments of single SimDB:Protocol-s. See the Note.]
  • removed genericparametersetting and numericparametersetting. SSingle, concrete ParameterSetting class has "value" attribute of type Value.
  • Statistics has attribute "value" of type Value. This also allows one to have statistics on string and other non-numeric attributes. For example min/max dates [TODO should Value contain a datetime attribute?], or nominal value, or (in the future) histograms.
  • Added a literal "constant" to Statistic (formerly CharacterisaitonType) to indicate a value that is held constant during an experiment. Example: mass of particles in an N-body simulation.
  • Cleaned up some bad characters.
  • Added "unit" attribute to Field.
  • Changed ValidValue's "value" attribute from string to Value datatype. *

(back to main)


Revision 262009-11-03 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, whilst older versions are under the input/ directory, such as version r902. I will try to keep track of the different versions and change logs below. At the bottom of the page the generated GraphViz image representing the last (checked in) version of the model. (NB need to ensure it is in synch with the actual model).

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation, provenance etc (see separate page)
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


Version history (link on heading):

Sometimes versions do not change in content, but nevrtheless produce different MagicDraw XMI documents. Sometimes this is due to different drawing, redrawing links or something like that. Here I only indicate the content that was changed. This I do by generating the SimDB_INTERMEDIATE.xml file and diffing those. Note, at the end there is a diff between the current specification model and amodel on VO-URP/input/simdb.

specification/

under construction
Added:
>
>
  • Updated descriptions.
  • Rename the enumeration CharacterisationType to Statistic. Rename the 'type' attribute on Characterisation to 'statistic'.
 1139

1089

  • Changed cardinality of snapshot collection on Experiment. now 0..*
  • a datatype StringLiteral was added. not really useful remnant of some experimenting. can be removed.
  • Changed cardinality of representationObject collection on experiment. now 0..*
  • Changed cardinality of objectCollecitoncollection on Snapshot. now 0..*
  • Changed cardianlity of label attribute on ValidValue, from 1 to 0..1
1059
  • Added option to refer to an external utype for each <>. Added one on Resource: otherutype="Reg:VOResource"
1034
  • removed explicit dependency between simdb and IVOAValueTYpes packages again [this is all mainly caused by changes in how to represent explicitly how a model depends on the profile. Is an explict dependency required or not.
  • PostProcessing no longer abstract.

1029

  • no change in content.

1020

  • Added Identity datatype to the IVOAValueTypes. [check whether this is necessray in the model or only for code generation?]
  • Recreated the explicit dependency relation between the "simdb" and IVOAValueTypes" packages.
  • Fixed the errors on Contact introduced in 898.

1012

  • Removed the "model" package. This was used for code generation purposes only.

989

978

  • No change in content

952

  • Exact copy of, i.e. no change wrt prop-952

prop-951 (Mar 12, 2009 ,derived from input/902 !)

input/

1025

902

887

VO-URP

<VO-URP>/input/simdb/SimDB_DM.xml 458 (diff with volute v1089
  • Add "basic" package, holding on to basic datatypes such as Quantity, Value, Cardinality, DataType.
  • All other packages depend on it. [this is somewhat ugly and required by a problem of the current generation framework (i.e. VO-URP), which does not yet allow "inheriting" dependencies from parent to child packages. Only simdb needs otherwise have this relation. Currently it is required so that appropriate import statements will be generated on XML schemas.]
  • Renamed Characterisation -> Statistics ["innocent name change" ?]
  • Renamed CharacterisationType -> Statistic [possibility for confusion with Statistics].
  • Renamed "characterisation" collection on ObjectCollection to "statistics".
  • Introduced Value datatype, representing values of either numeric or unknown datatype. Both represented by an attribute of type Quantity, reps string. [NB this is still far from ideal! But more useful model seems impossible for now as we simply can not know the datatype of parameter values in the model! S3 might present a method to design protocols that can work around this feature of the model, at the cost of only allowing access to experiments of single SimDB:Protocol-s. See the Note.]
  • removed genericparametersetting and numericparametersetting. SSingle, concrete ParameterSetting class has "value" attribute of type Value.
  • Statistics has attribute "value" of type Value. This also allows one to have statistics on string and other non-numeric attributes. For example min/max dates [TODO should Value contain a datetime attribute?], or nominal value, or (in the future) histograms.
  • Added a literal "constant" to Statistic (formerly CharacterisaitonType) to indicate a value that is held constant during an experiment. Example: mass of particles in an N-body simulation.
  • Cleaned up some bad characters.
  • Added "unit" attribute to Field.
  • Changed ValidValue's "value" attribute from string to Value datatype. *

(back to main)


<--  
-->

Revision 252009-10-16 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, whilst older versions are under the input/ directory, such as version r902. I will try to keep track of the different versions and change logs below. At the bottom of the page the generated GraphViz image representing the last (checked in) version of the model. (NB need to ensure it is in synch with the actual model).

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation, provenance etc (see separate page)
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


Version history (link on heading):

Sometimes versions do not change in content, but nevrtheless produce different MagicDraw XMI documents. Sometimes this is due to different drawing, redrawing links or something like that. Here I only indicate the content that was changed. This I do by generating the SimDB_INTERMEDIATE.xml file and diffing those. Note, at the end there is a diff between the current specification model and amodel on VO-URP/input/simdb.

specification/

Changed:
<
<
under construction
>
>
under construction
Added:
>
>
1139
 
Added:
>
>
  • Updated description of various classes (in progress).
 1089
  • Changed cardinality of snapshot collection on Experiment. now 0..*
  • a datatype StringLiteral was added. not really useful remnant of some experimenting. can be removed.
  • Changed cardinality of representationObject collection on experiment. now 0..*
  • Changed cardinality of objectCollecitoncollection on Snapshot. now 0..*
  • Changed cardianlity of label attribute on ValidValue, from 1 to 0..1
1059
  • Added option to refer to an external utype for each <>. Added one on Resource: otherutype="Reg:VOResource"
1034
  • removed explicit dependency between simdb and IVOAValueTYpes packages again [this is all mainly caused by changes in how to represent explicitly how a model depends on the profile. Is an explict dependency required or not.
  • PostProcessing no longer abstract.

1029

  • no change in content.

1020

  • Added Identity datatype to the IVOAValueTypes. [check whether this is necessray in the model or only for code generation?]
  • Recreated the explicit dependency relation between the "simdb" and IVOAValueTypes" packages.
  • Fixed the errors on Contact introduced in 898.

1012

  • Removed the "model" package. This was used for code generation purposes only.

989

978

  • No change in content

952

  • Exact copy of, i.e. no change wrt prop-952

prop-951 (Mar 12, 2009 ,derived from input/902 !)

input/

1025

902

887

VO-URP

<VO-URP>/input/simdb/SimDB_DM.xml 458 (diff with volute v1089
  • Add "basic" package, holding on to basic datatypes such as Quantity, Value, Cardinality, DataType.
  • All other packages depend on it. [this is somewhat ugly and required by a problem of the current generation framework (i.e. VO-URP), which does not yet allow "inheriting" dependencies from parent to child packages. Only simdb needs otherwise have this relation. Currently it is required so that appropriate import statements will be generated on XML schemas.]
  • Renamed Characterisation -> Statistics ["innocent name change" ?]
  • Renamed CharacterisationType -> Statistic [possibility for confusion with Statistics].
  • Renamed "characterisation" collection on ObjectCollection to "statistics".
  • Introduced Value datatype, representing values of either numeric or unknown datatype. Both represented by an attribute of type Quantity, reps string. [NB this is still far from ideal! But more useful model seems impossible for now as we simply can not know the datatype of parameter values in the model! S3 might present a method to design protocols that can work around this feature of the model, at the cost of only allowing access to experiments of single SimDB:Protocol-s. See the Note.]
  • removed genericparametersetting and numericparametersetting. SSingle, concrete ParameterSetting class has "value" attribute of type Value.
  • Statistics has attribute "value" of type Value. This also allows one to have statistics on string and other non-numeric attributes. For example min/max dates [TODO should Value contain a datetime attribute?], or nominal value, or (in the future) histograms.
  • Added a literal "constant" to Statistic (formerly CharacterisaitonType) to indicate a value that is held constant during an experiment. Example: mass of particles in an N-body simulation.
  • Cleaned up some bad characters.
  • Added "unit" attribute to Field.
  • Changed ValidValue's "value" attribute from string to Value datatype. *

(back to main)


<--  
-->

Revision 242009-10-15 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, whilst older versions are under the input/ directory, such as version r902. I will try to keep track of the different versions and change logs below. At the bottom of the page the generated GraphViz image representing the last (checked in) version of the model. (NB need to ensure it is in synch with the actual model).

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation, provenance etc (see separate page)
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


Version history (link on heading):

Sometimes versions do not change in content, but nevrtheless produce different MagicDraw XMI documents. Sometimes this is due to different drawing, redrawing links or something like that. Here I only indicate the content that was changed. This I do by generating the SimDB_INTERMEDIATE.xml file and diffing those. Note, at the end there is a diff between the current specification model and amodel on VO-URP/input/simdb.

specification/

Changed:
<
<
>
>
under construction
Added:
>
>
 1089
  • Changed cardinality of snapshot collection on Experiment. now 0..*
  • a datatype StringLiteral was added. not really useful remnant of some experimenting. can be removed.
  • Changed cardinality of representationObject collection on experiment. now 0..*
  • Changed cardinality of objectCollecitoncollection on Snapshot. now 0..*
  • Changed cardianlity of label attribute on ValidValue, from 1 to 0..1
1059
  • Added option to refer to an external utype for each <>. Added one on Resource: otherutype="Reg:VOResource"
1034
  • removed explicit dependency between simdb and IVOAValueTYpes packages again [this is all mainly caused by changes in how to represent explicitly how a model depends on the profile. Is an explict dependency required or not.
  • PostProcessing no longer abstract.

1029

  • no change in content.

1020

  • Added Identity datatype to the IVOAValueTypes. [check whether this is necessray in the model or only for code generation?]
  • Recreated the explicit dependency relation between the "simdb" and IVOAValueTypes" packages.
  • Fixed the errors on Contact introduced in 898.

1012

  • Removed the "model" package. This was used for code generation purposes only.

989

978

  • No change in content

952

  • Exact copy of, i.e. no change wrt prop-952

prop-951 (Mar 12, 2009 ,derived from input/902 !)

input/

1025

902

887

VO-URP

<VO-URP>/input/simdb/SimDB_DM.xml 458 (diff with volute v1089
  • Add "basic" package, holding on to basic datatypes such as Quantity, Value, Cardinality, DataType.
  • All other packages depend on it. [this is somewhat ugly and required by a problem of the current generation framework (i.e. VO-URP), which does not yet allow "inheriting" dependencies from parent to child packages. Only simdb needs otherwise have this relation. Currently it is required so that appropriate import statements will be generated on XML schemas.]
  • Renamed Characterisation -> Statistics ["innocent name change" ?]
  • Renamed CharacterisationType -> Statistic [possibility for confusion with Statistics].
  • Renamed "characterisation" collection on ObjectCollection to "statistics".
  • Introduced Value datatype, representing values of either numeric or unknown datatype. Both represented by an attribute of type Quantity, reps string. [NB this is still far from ideal! But more useful model seems impossible for now as we simply can not know the datatype of parameter values in the model! S3 might present a method to design protocols that can work around this feature of the model, at the cost of only allowing access to experiments of single SimDB:Protocol-s. See the Note.]
  • removed genericparametersetting and numericparametersetting. SSingle, concrete ParameterSetting class has "value" attribute of type Value.
  • Statistics has attribute "value" of type Value. This also allows one to have statistics on string and other non-numeric attributes. For example min/max dates [TODO should Value contain a datetime attribute?], or nominal value, or (in the future) histograms.
  • Added a literal "constant" to Statistic (formerly CharacterisaitonType) to indicate a value that is held constant during an experiment. Example: mass of particles in an N-body simulation.
  • Cleaned up some bad characters.
  • Added "unit" attribute to Field.
  • Changed ValidValue's "value" attribute from string to Value datatype. *

(back to main)


<--  
-->

Revision 232009-10-06 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, whilst older versions are under the input/ directory, such as version r902. I will try to keep track of the different versions and change logs below. At the bottom of the page the generated GraphViz image representing the last (checked in) version of the model. (NB need to ensure it is in synch with the actual model).

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation, provenance etc (see separate page)
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


Version history (link on heading):

Sometimes versions do not change in content, but nevrtheless produce different MagicDraw XMI documents. Sometimes this is due to different drawing, redrawing links or something like that. Here I only indicate the content that was changed. This I do by generating the SimDB_INTERMEDIATE.xml file and diffing those. Note, at the end there is a diff between the current specification model and amodel on VO-URP/input/simdb.

specification/

1089

  • Changed cardinality of snapshot collection on Experiment. now 0..*
  • a datatype StringLiteral was added. not really useful remnant of some experimenting. can be removed.
  • Changed cardinality of representationObject collection on experiment. now 0..*
  • Changed cardinality of objectCollecitoncollection on Snapshot. now 0..*
  • Changed cardianlity of label attribute on ValidValue, from 1 to 0..1
1059
  • Added option to refer to an external utype for each <>. Added one on Resource: otherutype="Reg:VOResource"
1034
  • removed explicit dependency between simdb and IVOAValueTYpes packages again [this is all mainly caused by changes in how to represent explicitly how a model depends on the profile. Is an explict dependency required or not.
  • PostProcessing no longer abstract.

1029

  • no change in content.

1020

  • Added Identity datatype to the IVOAValueTypes. [check whether this is necessray in the model or only for code generation?]
  • Recreated the explicit dependency relation between the "simdb" and IVOAValueTypes" packages.
  • Fixed the errors on Contact introduced in 898.

1012

  • Removed the "model" package. This was used for code generation purposes only.

989

978

  • No change in content

952

  • Exact copy of, i.e. no change wrt prop-952

prop-951 (Mar 12, 2009 ,derived from input/902 !)

input/

1025

902

887

VO-URP

Changed:
<
<
<VO-URP>/input/SimDB_DM.xml 458 (diff with volute v1089
>
>
<VO-URP>/input/simdb/SimDB_DM.xml 458 (diff with volute v1089
 
  • Add "basic" package, holding on to basic datatypes such as Quantity, Value, Cardinality, DataType.
  • All other packages depend on it. [this is somewhat ugly and required by a problem of the current generation framework (i.e. VO-URP), which does not yet allow "inheriting" dependencies from parent to child packages. Only simdb needs otherwise have this relation. Currently it is required so that appropriate import statements will be generated on XML schemas.]
  • Renamed Characterisation -> Statistics ["innocent name change" ?]
  • Renamed CharacterisationType -> Statistic [possibility for confusion with Statistics].
  • Renamed "characterisation" collection on ObjectCollection to "statistics".
  • Introduced Value datatype, representing values of either numeric or unknown datatype. Both represented by an attribute of type Quantity, reps string. [NB this is still far from ideal! But more useful model seems impossible for now as we simply can not know the datatype of parameter values in the model! S3 might present a method to design protocols that can work around this feature of the model, at the cost of only allowing access to experiments of single SimDB:Protocol-s. See the Note.]
  • removed genericparametersetting and numericparametersetting. SSingle, concrete ParameterSetting class has "value" attribute of type Value.
  • Statistics has attribute "value" of type Value. This also allows one to have statistics on string and other non-numeric attributes. For example min/max dates [TODO should Value contain a datetime attribute?], or nominal value, or (in the future) histograms.
  • Added a literal "constant" to Statistic (formerly CharacterisaitonType) to indicate a value that is held constant during an experiment. Example: mass of particles in an N-body simulation.
  • Cleaned up some bad characters.
  • Added "unit" attribute to Field.
  • Changed ValidValue's "value" attribute from string to Value datatype. *

(back to main)


<--  
-->

Revision 222009-10-05 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, whilst older versions are under the input/ directory, such as version r902. I will try to keep track of the different versions and change logs below. At the bottom of the page the generated GraphViz image representing the last (checked in) version of the model. (NB need to ensure it is in synch with the actual model).

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation, provenance etc (see separate page)
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


Version history (link on heading):

Sometimes versions do not change in content, but nevrtheless produce different MagicDraw XMI documents. Sometimes this is due to different drawing, redrawing links or something like that. Here I only indicate the content that was changed. This I do by generating the SimDB_INTERMEDIATE.xml file and diffing those. Note, at the end there is a diff between the current specification model and amodel on VO-URP/input/simdb.

specification/

1089

  • Changed cardinality of snapshot collection on Experiment. now 0..*
  • a datatype StringLiteral was added. not really useful remnant of some experimenting. can be removed.
  • Changed cardinality of representationObject collection on experiment. now 0..*
  • Changed cardinality of objectCollecitoncollection on Snapshot. now 0..*
  • Changed cardianlity of label attribute on ValidValue, from 1 to 0..1
1059
  • Added option to refer to an external utype for each <>. Added one on Resource: otherutype="Reg:VOResource"
1034
  • removed explicit dependency between simdb and IVOAValueTYpes packages again [this is all mainly caused by changes in how to represent explicitly how a model depends on the profile. Is an explict dependency required or not.
  • PostProcessing no longer abstract.

1029

  • no change in content.

1020

  • Added Identity datatype to the IVOAValueTypes. [check whether this is necessray in the model or only for code generation?]
  • Recreated the explicit dependency relation between the "simdb" and IVOAValueTypes" packages.
  • Fixed the errors on Contact introduced in 898.

1012

  • Removed the "model" package. This was used for code generation purposes only.

989

978

  • No change in content

952

  • Exact copy of, i.e. no change wrt prop-952

prop-951 (Mar 12, 2009 ,derived from input/902 !)

input/

1025

902

887

VO-URP

<VO-URP>/input/SimDB_DM.xml 458 (diff with volute v1089
  • Add "basic" package, holding on to basic datatypes such as Quantity, Value, Cardinality, DataType.
  • All other packages depend on it. [this is somewhat ugly and required by a problem of the current generation framework (i.e. VO-URP), which does not yet allow "inheriting" dependencies from parent to child packages. Only simdb needs otherwise have this relation. Currently it is required so that appropriate import statements will be generated on XML schemas.]
  • Renamed Characterisation -> Statistics ["innocent name change" ?]
  • Renamed CharacterisationType -> Statistic [possibility for confusion with Statistics].
  • Renamed "characterisation" collection on ObjectCollection to "statistics".
  • Introduced Value datatype, representing values of either numeric or unknown datatype. Both represented by an attribute of type Quantity, reps string. [NB this is still far from ideal! But more useful model seems impossible for now as we simply can not know the datatype of parameter values in the model! S3 might present a method to design protocols that can work around this feature of the model, at the cost of only allowing access to experiments of single SimDB:Protocol-s. See the Note.]
Changed:
<
<
  • removed genericparametersetting and numericparametersetting. Single, concrete ParameterSetting class has value of type Value.
  • Statistics has attribute value of type Value. This also allows one to have string
>
>
  • removed genericparametersetting and numericparametersetting. SSingle, concrete ParameterSetting class has "value" attribute of type Value.
  • Statistics has attribute "value" of type Value. This also allows one to have statistics on string and other non-numeric attributes. For example min/max dates [TODO should Value contain a datetime attribute?], or nominal value, or (in the future) histograms.
Added:
>
>
  • Added a literal "constant" to Statistic (formerly CharacterisaitonType) to indicate a value that is held constant during an experiment. Example: mass of particles in an N-body simulation.
  • Cleaned up some bad characters.
  • Added "unit" attribute to Field.
  • Changed ValidValue's "value" attribute from string to Value datatype. *
 

(back to main)


<--  
-->

Revision 212009-10-05 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, whilst older versions are under the input/ directory, such as version r902. I will try to keep track of the different versions and change logs below. At the bottom of the page the generated GraphViz image representing the last (checked in) version of the model. (NB need to ensure it is in synch with the actual model).

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation, provenance etc (see separate page)
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


Version history (link on heading):

Sometimes versions do not change in content, but nevrtheless produce different MagicDraw XMI documents. Sometimes this is due to different drawing, redrawing links or something like that.
Changed:
<
<
Here I only indicate the content changed. This I do by generating the SimDB_INTERMEDIATE.xml file and diffing those.
>
>
Here I only indicate the content that was changed. This I do by generating the SimDB_INTERMEDIATE.xml file and diffing those.
Added:
>
>
Note, at the end there is a diff between the current specification model and amodel on VO-URP/input/simdb.
 
Added:
>
>
 

specification/

1089

  • Changed cardinality of snapshot collection on Experiment. now 0..*
  • a datatype StringLiteral was added. not really useful remnant of some experimenting. can be removed.
  • Changed cardinality of representationObject collection on experiment. now 0..*
  • Changed cardinality of objectCollecitoncollection on Snapshot. now 0..*
  • Changed cardianlity of label attribute on ValidValue, from 1 to 0..1
1059
  • Added option to refer to an external utype for each <>. Added one on Resource: otherutype="Reg:VOResource"
1034
  • removed explicit dependency between simdb and IVOAValueTYpes packages again [this is all mainly caused by changes in how to represent explicitly how a model depends on the profile. Is an explict dependency required or not.
  • PostProcessing no longer abstract.

1029

  • no change in content.

1020

  • Added Identity datatype to the IVOAValueTypes. [check whether this is necessray in the model or only for code generation?]
  • Recreated the explicit dependency relation between the "simdb" and IVOAValueTypes" packages.
  • Fixed the errors on Contact introduced in 898.

1012

  • Removed the "model" package. This was used for code generation purposes only.

989

978

  • No change in content

952

  • Exact copy of, i.e. no change wrt prop-952

prop-951 (Mar 12, 2009 ,derived from input/902 !)

input/

1025
Deleted:
<
<
 902

887

Added:
>
>

VO-URP

<VO-URP>/input/SimDB_DM.xml 458 (diff with volute v1089
  • Add "basic" package, holding on to basic datatypes such as Quantity, Value, Cardinality, DataType.
  • All other packages depend on it. [this is somewhat ugly and required by a problem of the current generation framework (i.e. VO-URP), which does not yet allow "inheriting" dependencies from parent to child packages. Only simdb needs otherwise have this relation. Currently it is required so that appropriate import statements will be generated on XML schemas.]
  • Renamed Characterisation -> Statistics ["innocent name change" ?]
  • Renamed CharacterisationType -> Statistic [possibility for confusion with Statistics].
  • Renamed "characterisation" collection on ObjectCollection to "statistics".
  • Introduced Value datatype, representing values of either numeric or unknown datatype. Both represented by an attribute of type Quantity, reps string. [NB this is still far from ideal! But more useful model seems impossible for now as we simply can not know the datatype of parameter values in the model! S3 might present a method to design protocols that can work around this feature of the model, at the cost of only allowing access to experiments of single SimDB:Protocol-s. See the Note.]
  • removed genericparametersetting and numericparametersetting. Single, concrete ParameterSetting class has value of type Value.
  • Statistics has attribute value of type Value. This also allows one to have string
 

(back to main)


<--  
-->

Revision 202009-10-05 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, whilst older versions are under the input/ directory, such as version r902. I will try to keep track of the different versions and change logs below. At the bottom of the page the generated GraphViz image representing the last (checked in) version of the model. (NB need to ensure it is in synch with the actual model).

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation, provenance etc (see separate page)
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


Version history (link on heading):

Sometimes versions do not change in content, but nevrtheless produce different MagicDraw XMI documents. Sometimes this is due to different drawing, redrawing links or something like that. Here I only indicate the content changed. This I do by generating the SimDB_INTERMEDIATE.xml file and diffing those.

specification/

1089

Changed:
<
<
>
>
  • Changed cardinality of snapshot collection on Experiment. now 0..*
Added:
>
>
  • a datatype StringLiteral was added. not really useful remnant of some experimenting. can be removed.
  • Changed cardinality of representationObject collection on experiment. now 0..*
  • Changed cardinality of objectCollecitoncollection on Snapshot. now 0..*
  • Changed cardianlity of label attribute on ValidValue, from 1 to 0..1
 1059
  • Added option to refer to an external utype for each <>. Added one on Resource: otherutype="Reg:VOResource"
1034
  • removed explicit dependency between simdb and IVOAValueTYpes packages again [this is all mainly caused by changes in how to represent explicitly how a model depends on the profile. Is an explict dependency required or not.
  • PostProcessing no longer abstract.

1029

  • no change in content.

1020

  • Added Identity datatype to the IVOAValueTypes. [check whether this is necessray in the model or only for code generation?]
  • Recreated the explicit dependency relation between the "simdb" and IVOAValueTypes" packages.
  • Fixed the errors on Contact introduced in 898.

1012

  • Removed the "model" package. This was used for code generation purposes only.

989

978

  • No change in content

952

  • Exact copy of, i.e. no change wrt prop-952

prop-951 (Mar 12, 2009 ,derived from input/902 !)

input/

1025

902

887

(back to main)


<--  
-->

Revision 192009-10-05 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, whilst older versions are under the input/ directory, such as version r902. I will try to keep track of the different versions and change logs below. At the bottom of the page the generated GraphViz image representing the last (checked in) version of the model. (NB need to ensure it is in synch with the actual model).

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation, provenance etc (see separate page)
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


Version history (link on heading):

Sometimes versions do not change in content, but nevrtheless produce different MagicDraw XMI documents. Sometimes this is due to different drawing, redrawing links or something like that. Here I only indicate the content changed. This I do by generating the SimDB_INTERMEDIATE.xml file and diffing those.

specification/

1089

1059

Changed:
<
<
>
>
  • Added option to refer to an external utype for each <>. Added one on Resource: otherutype="Reg:VOResource"
 1034
Added:
>
>
  • removed explicit dependency between simdb and IVOAValueTYpes packages again [this is all mainly caused by changes in how to represent explicitly how a model depends on the profile. Is an explict dependency required or not.
  • PostProcessing no longer abstract.
  1029
Deleted:
<
<
 
  • no change in content.
Added:
>
>
 1020
  • Added Identity datatype to the IVOAValueTypes. [check whether this is necessray in the model or only for code generation?]
  • Recreated the explicit dependency relation between the "simdb" and IVOAValueTypes" packages.
  • Fixed the errors on Contact introduced in 898.

1012

  • Removed the "model" package. This was used for code generation purposes only.

989

978

  • No change in content

952

  • Exact copy of, i.e. no change wrt prop-952

prop-951 (Mar 12, 2009 ,derived from input/902 !)

input/

1025

902

887

(back to main)


<--  
-->

Revision 182009-10-05 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, whilst older versions are under the input/ directory, such as version r902. I will try to keep track of the different versions and change logs below. At the bottom of the page the generated GraphViz image representing the last (checked in) version of the model. (NB need to ensure it is in synch with the actual model).

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation, provenance etc (see separate page)
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


Version history (link on heading):

Sometimes versions do not change in content, but nevrtheless produce different MagicDraw XMI documents. Sometimes this is due to different drawing, redrawing links or something like that. Here I only indicate the content changed. This I do by generating the SimDB_INTERMEDIATE.xml file and diffing those.

specification/

1089

1059

1034

1029

Added:
>
>
  • no change in content.
 1020
Added:
>
>
  • Added Identity datatype to the IVOAValueTypes. [check whether this is necessray in the model or only for code generation?]
  • Recreated the explicit dependency relation between the "simdb" and IVOAValueTypes" packages.
  • Fixed the errors on Contact introduced in 898.
  1012
Added:
>
>
  • Removed the "model" package. This was used for code generation purposes only.
  989
Changed:
<
<
  • In Contact, INTRODUCED ERROR, changed dattaype of telephone from string to Resource
>
>
  • In Contact, INTRODUCED 2 ERRORSD
Added:
>
>
 978
  • No change in content

952

  • Exact copy of, i.e. no change wrt prop-952

prop-951 (Mar 12, 2009 ,derived from input/902 !)

input/

1025

902

887

(back to main)


<--  
-->

Revision 172009-10-05 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, whilst older versions are under the input/ directory, such as version r902. I will try to keep track of the different versions and change logs below. At the bottom of the page the generated GraphViz image representing the last (checked in) version of the model. (NB need to ensure it is in synch with the actual model).

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation, provenance etc (see separate page)
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


Changed:
<
<
Version history (link on heading):
>
>

Version history (link on heading):

Added:
>
>
Sometimes versions do not change in content, but nevrtheless produce different MagicDraw XMI documents. Sometimes this is due to different drawing, redrawing links or something like that. Here I only indicate the content changed. This I do by generating the SimDB_INTERMEDIATE.xml file and diffing those.
 
Added:
>
>

specification/

 1089

1059

1034

1029

1020

1012

989

Changed:
<
<
>
>
  • removed explicit dependency from simdb package on IVOAValueTypes package
Added:
>
>
  • Rename AccessibleExperiment to AccessibleResource and change its "experiment" reference to point to Resource iso Experiment and rename it to "resource".
  • In Contact, INTRODUCED ERROR, changed dattaype of telephone from string to Resource
 978
Added:
>
>
  • No change in content
  952
Added:
>
>
  • Exact copy of, i.e. no change wrt prop-952
 
Changed:
<
<
951
>
>
prop-951 (Mar 12, 2009 ,derived from input/902 !)
Added:
>
>
 
Changed:
<
<
input/
>
>

input/

Added:
>
>
1025

 902
Added:
>
>

887

 

(back to main)


<--  
-->

Revision 162009-10-05 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml.
Changed:
<
<
The previous versions as well as later working versions can be found in the history of this file, as well as its direct predecessor version r902. An image of the latest version of the model is reproduced at the bottom of this page.
>
>
The previous versions as well as later working versions can be found in the history of this file, whilst older versions are under the input/ directory, such as version r902. I will try to keep track of the different versions and change logs below. At the bottom of the page the generated GraphViz image representing the last (checked in) version of the model. (NB need to ensure it is in synch with the actual model).
 

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation, provenance etc (see separate page)
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...
Added:
>
>
 
Added:
>
>
Version history (link on heading):

1089

1059

1034

1029

1020

1012

989

978

952

951

input/
902

 (back to main)


Changed:
<
<
>
>
 
<--  
-->

Revision 152009-10-05 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml.
Changed:
<
<
The previous versions as well as later working versions can be found in the history of this file, as well as its direct predecessor version r902.
>
>
The previous versions as well as later working versions can be found in the history of this file, as well as its direct predecessor version r902.
 An image of the latest version of the model is reproduced at the bottom of this page.

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation, provenance etc (see separate page)
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


(back to main)


<--  
-->

Revision 142009-06-03 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, as well as its direct predecessor version r902. An image of the latest version of the model is reproduced at the bottom of this page.

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
Changed:
<
<
    • characterisation
>
>
 
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


(back to main)


<--  
-->

Revision 132009-05-19 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
(back to main)
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, as well as its direct predecessor version r902.
Added:
>
>
An image of the latest version of the model is reproduced at the bottom of this page.
 

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


Changed:
<
<
(back to main)
>
>
(back to main)

Added:
>
>

 
<--  
-->

Revision 122009-05-19 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
Added:
>
>
(back to main)
 This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, as well as its direct predecessor version r902.

To be discussed

  • OK on approach?
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


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

Revision 112009-05-19 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
This page is devoted to describing the SimDB data model (SimDB/DM from now on).

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, as well as its direct predecessor version r902.
Changed:
<
<

TODO

>
>

To be discussed

 
  • OK on approach?
Changed:
<
<
    • analysis(conceptual)->logical->physical
    • TAP+XML
>
>
    • modelling: analysis(conceptual)->logical->physical
    • TAP+XML+UTYPE serialisations derived from logical model
 
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to UTYPEs
  • finalise the serialisation to TAP (see IVOA.IVOATheorySimDBTAP)
  • finalise the serialisation to XML schema ((see IVOA.IVOATheorySimDBREST)
  • reuse by other specs
    • SimDAP
    • S3
  • ...


<--  
-->

Revision 102009-05-12 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
This page is devoted to describing the SimDB data model (SimDB/DM from now on).
Added:
>
>

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, as well as its direct predecessor version r902.
 

TODO

  • OK on approach?
    • analysis(conceptual)->logical->physical
    • TAP+XML
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
Changed:
<
<
  • finalise the serialisation to TAP
    • which OR mapping approaches
  • finalise the serialisation to XML schema
    • multiple packages
    • identifiers
>
>
Deleted:
<
<
 
    • S3
Deleted:
<
<

Some scattered notes and remarks

for historical purposes

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, as well as its direct predecessor version r902.

see also It is meant to reflect the proposal and incorporate conclusions from the discussions page.

Examples of Protocols

For discussion purposes it will be good to have a list of real protocols, i.e. simulation and post-processing codes and algorithms.

Examples of protocols:

Simulators:

  • Gadget (http://www.mpa-garching.mpg.de/gadget/)
  • Enzo ...
  • Flash ...
  • Nemo ...
  • Ramses ...
  • L-Galaxies (MPA semi-analytical (SAM) galaxy formation code)
  • GalForm (Durham SAM code)
  • GalICS (Horizon SAM)
 
  • ...
Deleted:
<
<
Pure post-processors: cluster finders
  • FOF cluster finders (various implementations)
  • SUBFIND cluster finder (Springel etal 2001, ADS)
  • ...
others
 
<--  
-->

Revision 92009-05-12 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
This page is devoted to describing the SimDB data model (SimDB/DM from now on).
Deleted:
<
<
It is meant to reflect the proposal and incorporate conclusions from the discussions page.
 
Added:
>
>

TODO

  • OK on approach?
    • analysis(conceptual)->logical->physical
    • TAP+XML
  • Identify main issues of model
    • sufficiently detailed resources?
    • characterisation
    • normalisation (problem for XML, little for TAP)
    • "queriability" (problem for TAP)
    • missing semantic vocabularies
    • quantities/units
  • Clean up
    • documentation in the UML
    • Description of model in Note
  • finalise the serialisation to TAP
    • which OR mapping approaches
  • finalise the serialisation to XML schema
    • multiple packages
    • identifiers
  • reuseby other specs

Some scattered notes and remarks

for historical purposes
 

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, as well as its direct predecessor version r902.
Changed:
<
<
I propose that for the rest of the discussion we limit ourselves to the model in the
>
>
see also It is meant to reflect the proposal and incorporate conclusions from the discussions page.
Deleted:
<
<
specification subdirectory.

In this page we gather material to support the model.

 

Examples of Protocols

For discussion purposes it will be good to have a list of real protocols, i.e. simulation and post-processing codes and algorithms.

Examples of protocols:

Simulators:

  • Gadget (http://www.mpa-garching.mpg.de/gadget/)
  • Enzo ...
  • Flash ...
  • Nemo ...
  • Ramses ...
  • L-Galaxies (MPA semi-analytical (SAM) galaxy formation code)
  • GalForm (Durham SAM code)
  • GalICS (Horizon SAM)
  • ...

Pure post-processors: cluster finders

  • FOF cluster finders (various implementations)
  • SUBFIND cluster finder (Springel etal 2001, ADS)
  • ...
others


<--  
-->

Revision 82009-04-28 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
This page is devoted to describing the SimDB data model (SimDB/DM from now on). It is meant to reflect the proposal and incorporate conclusions from the discussions page.

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, as well as its direct predecessor version r902.

I propose that for the rest of the discussion we limit ourselves to the model in the specification subdirectory.

In this page we gather material to support the model.

Changed:
<
<

Protocols

>
>
Added:
>
>

Examples of Protocols

 For discussion purposes it will be good to have a list of real protocols, i.e. simulation and post-processing codes and algorithms.

Examples of protocols:

Simulators:

  • Gadget (http://www.mpa-garching.mpg.de/gadget/)
  • Enzo ...
  • Flash ...
  • Nemo ...
  • Ramses ...
  • L-Galaxies (MPA semi-analytical (SAM) galaxy formation code)
  • GalForm (Durham SAM code)
  • GalICS (Horizon SAM)
  • ...

Pure post-processors: cluster finders

  • FOF cluster finders (various implementations)
Changed:
<
<
  • SUBFIND cluster finder (Springel etal 2001,
>
>
  • SUBFIND cluster finder (Springel etal 2001, ADS)
Deleted:
<
<
ADS
 
  • ...
others


<--  
-->

Revision 72009-03-13 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
Changed:
<
<
This page is devoted to describing the SimDB data model.
>
>
This page is devoted to describing the SimDB data model (SimDB/DM from now on).
 It is meant to reflect the proposal and incorporate conclusions from the discussions page.

Current model

Changed:
<
<
The history of all development can be followed in a subversion repository in Norman Gray's Volute project on GoogleCode.
>
>
As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml.
Added:
>
>
The previous versions as well as later working versions can be found in the history of this file, as well as its direct predecessor version r902.
 
Changed:
<
<
The previous version of the model is r902 from the
>
>
I propose that for the rest of the discussion we limit ourselves to the model in the
Deleted:
<
<
input directory.

I propose that for the rest of the discussion we limit ourselves to the documents in the

 specification subdirectory.
Changed:
<
<
That subdirectory contains
>
>
In this page we gather material to support the model.
Deleted:
<
<
 
Changed:
<
<

Protocol

>
>
Added:
>
>

Protocols

For discussion purposes it will be good to have a list of real protocols, i.e. simulation and post-processing codes and algorithms.
 Examples of protocols:

Simulators:

  • Gadget (http://www.mpa-garching.mpg.de/gadget/)
  • Enzo ...
  • Flash ...
  • Nemo ...
  • Ramses ...
  • L-Galaxies (MPA semi-analytical (SAM) galaxy formation code)
  • GalForm (Durham SAM code)
  • GalICS (Horizon SAM)
  • ...

Pure post-processors: cluster finders

  • FOF cluster finders (various implementations)
  • SUBFIND cluster finder (Springel etal 2001,
ADS
  • ...
others


<--  
-->

Revision 62009-03-13 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
Changed:
<
<
This page is devoted to describing the SimDB data model.
>
>
This page is devoted to describing the SimDB data model.
 It is meant to reflect the proposal and incorporate conclusions from the discussions page.

Current model

Changed:
<
<
The latest version of the model is r902 from the input directory in the
>
>
The history of all development can be followed in a subversion repository in Norman Gray's Volute project on GoogleCode.
Deleted:
<
<
volute repository.
 
Added:
>
>
The previous version of the model is r902 from the input directory.
 
Added:
>
>
I propose that for the rest of the discussion we limit ourselves to the documents in the specification subdirectory.

That subdirectory contains

 

Protocol

Examples of protocols:

Simulators:

  • Gadget (http://www.mpa-garching.mpg.de/gadget/)
  • Enzo ...
  • Flash ...
  • Nemo ...
  • Ramses ...
  • L-Galaxies (MPA semi-analytical (SAM) galaxy formation code)
  • GalForm (Durham SAM code)
  • GalICS (Horizon SAM)
  • ...

Pure post-processors: cluster finders

  • FOF cluster finders (various implementations)
  • SUBFIND cluster finder (Springel etal 2001,
ADS
  • ...
others


<--  
-->

Revision 52009-03-13 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
This page is devoted to describing the SimDB data model. It is meant to reflect the proposal and incorporate conclusions from the discussions page.

Current model

Changed:
<
<
The latest version of the model is r902 from the
>
>
The latest version of the model is r902 from the
 input directory in the volute repository.

Protocol

Examples of protocols:

Simulators:

Changed:
<
<
>
>
  • GalForm (Durham SAM code)
  • GalICS (Horizon SAM)
 
  • ...

Pure post-processors: cluster finders

  • FOF cluster finders (various implementations)
Changed:
<
<
>
>
  • SUBFIND cluster finder (Springel etal 2001,
Added:
>
>
ADS
 
  • ...
others


<--  
-->

Revision 42009-03-13 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
This page is devoted to describing the SimDB data model. It is meant to reflect the proposal and incorporate conclusions from the discussions page.

Current model

The latest version of the model is r902 from the input directory in the volute repository.

Protocol

Examples of protocols:

Simulators:

Changed:
<
<
  • Enzo
  • Flash
  • Nemo
  • Ramses
>
>
  • Enzo ...
  • Flash ...
  • Nemo ...
  • Ramses ...
 
  • L-Galaxies (MPA semi-analytical (SAM) galaxy formation code)
  • GalForm (Durham SAM code)
  • GalICS (Horizon SAM)
  • ...

Pure post-processors: cluster finders

Changed:
<
<
  • FOF cluster finders (Davis etal 1986)
  • SubFind cluster finder (Springel etal 2001(
>
>
 
  • ...
others


<--  
-->

Revision 32009-03-13 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
This page is devoted to describing the SimDB data model. It is meant to reflect the proposal and incorporate conclusions from the discussions page.

Current model

The latest version of the model is r902 from the input directory in the volute repository.

Added:
>
>

Protocol

Examples of protocols:
 
Added:
>
>
Simulators:
 
Changed:
<
<
>
>
Pure post-processors: cluster finders
Added:
>
>
  • FOF cluster finders (Davis etal 1986)
  • SubFind cluster finder (Springel etal 2001(
  • ...
others
 
<--  
-->

Revision 22009-03-12 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
Changed:
<
<
This page is devoted to discussions regarding the SimDB data model (SimDB/DM).
>
>
This page is devoted to describing the SimDB data model.
Added:
>
>
It is meant to reflect the proposal and incorporate conclusions from the discussions page.
 

Current model

Added:
>
>
The latest version of the model is r902 from the input directory in the volute repository.
 
Deleted:
<
<

Issues

 


<--  
-->

Revision 12009-01-21 - GerardLemson

 
META TOPICPARENT name="IvoaTheory"
This page is devoted to discussions regarding the SimDB data model (SimDB/DM).

Current model

Issues


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