Fwd: Re: Cube/ImageDM - new diagram set.

[Douglas Tody]

On Fri, 2 May 2014, Louys Mireille wrote:
> I would just insure that the Characterisation DM is still in agreement.

The same point should be made about the SpectralDM 2.0.  I just checked,
and the Utypes in the latest draft do not agree with ObsCore or Char.

There was a time once, about 3 years ago, when we were trying to fast
track an update of the SpectrumDM to a generalized SpectralDM and wanted
compatibility with the existing standards and implementations at the
time.  However if are still now finalizing SpectralDM 2.0, and have
decided that ImageDM should extend ObsCore, I suggest that the new
SpectralDM should do so as well.

All of these primary data models - ObsCore/Char/ObsTAP, ImageDM, and
SpectralDM, should at this point share the same core data model based
upon the latest Char2 Utypes.  We already pretty much reached that point
last fall.

 	- Doug



On Fri, 2 May 2014, Louys Mireille wrote:

>
>
>
> -------- Message original --------
> Sujet: 	Re: Cube/ImageDM - new diagram set.
> Date : 	Fri, 02 May 2014 11:27:38 +0200
> De : 	Louys Mireille <mireille.louys at unistra.fr>
> Pour : 	CresitelloDittmar, Mark <mdittmar at cfa.harvard.edu>
>
>
>
> Hi Mark,  Hi DMers,
>
> Thank you Mark for this careful improvement and follow up of Image/DM.
>
> I haven't check your update in details yet .
> I would just insure that the Characterisation DM is still in agreement.
> That should be the case , because syserror and staterror inside Accuracy were 
> based on the STC object you rely on .
> Same for Resolution.
>
> About the term "Uncertainty", which is new , I think we should use Accuracy 
> which already exist instead.
> Same concepts with two different names might lose our standard readers / 
> implementers .
>
> Is it really a new concept?
>
> best wishes , Mireille
>
> Le 30/04/2014 20:31, CresitelloDittmar, Mark a écrit :
>> All,
>> 
>> I have, updated the Volute Cube model repository.
>> Some diagrams (STC/STCMod) plus two new ones (STC SubstitutionGroups, 
>> STCMod ErrorModel)
>> 
>> Changes are:
>>   + discussions with Arnold (off list), pointed out that the error model 
>> used was insufficient, more than 'interval' was needed.
>>      So, I went back into STC and pulled out the substitution groups used 
>> there (CERROR, CRESOLUTION, etc).  I then
>>      based a new datatype suite (Uncertainty), on some of Arnold's newer 
>> work.
>>      STCMod AxisCoordinate objects now use these objects for sysError, 
>> statError, resolution, bin.
>>   + the ivoa:datatypes discussion showed that I should separate Vector from 
>> AtomicValue.  Doing so effected some structure
>>      in the AxisCoordinates.  Also added Matrix type(s) to replace 
>> STC:double4Type and STC:double9Type.
>> 
>> Mark
>> 
>> 
>> 
>> 
>> On Wed, Apr 23, 2014 at 4:49 PM, CresitelloDittmar, Mark 
>> <mdittmar at cfa.harvard.edu <mailto:mdittmar at cfa.harvard.edu>> wrote:
>>
>>     All,
>>
>>     I have updated the Volute repository..
>>     Several diagrams, the modelio save-set, and the XMI files.
>>
>>     Changes are:
>>       + made a sweep of the models, replacing URI types with anyURI. 
>> Removed URI from my ivoaTypes model which was redundant with anyURI.
>>       + corrected some errors I found in my STC interpretation while
>>     reviewing the VO-DML version of the same.
>>       + XMI 2.4.1 - export does not include Modelio annotations.  The
>>     EMF3.0 export does.
>>
>>     Mark
>> 
>> 
>
>
>
>