[meas] RFC comment - MD #2,3

[CresitelloDittmar, Mark]

This may be an error in the multiplicity.
Currently Measure.error:Error[0..*]  (not 1..*) , and I was going to
respond that this was to cover the dimensionality of measure, but the text
is pretty clear that the Error content MUST be compatible (dimension,
domain, units, etc) with the Measure value.

So.. I think that is just an artifact from the previous representation and
there is a change here:
   Measure.error:Error[0..1]



On Tue, Sep 24, 2019 at 9:05 AM Markus Demleitner <
msdemlei at ari.uni-heidelberg.de> wrote:

> But if that's the requirement, I can't understand why Measure:Error
> is 1:* any more.  would clients interpret the additional error
> objects?  [on my first reading, I had thought these might correspond
> to different estimates or so, and so I'm actually happy that I was
> wrong].
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/dm/attachments/20190925/06d93c50/attachment.html>