[vo-dml] Clarification on composition rule..

[Patrick Dowler]

As you may know, I don't let the warning from vo-dml validation about open
ended multiplicity bother me too much. Polynomial is another good example
where it greatly limits/impacts how one might model something... I ran into
it way back at point, circle, polygon (oops! non-fixed size). I don't
expect this can be feasibly made illegal in future... I expect the
warning/admoinishment to be softened, maybe with some good advice about
when such cardinality is warranted and when another pattern may be a better
choice.

my 2c,


--
Patrick Dowler
Canadian Astronomy Data Centre
Victoria, BC, Canada


On Mon, 9 Mar 2020 at 06:05, Gerard Lemson <glemson1 at jhu.edu> wrote:

> HI Mark
>
> Just for now:
>
> From the vo-dml spec:
>
> “Modelers SHOULD NOT use open ended multiplicities, i.e. with
> maxOccurs=-1, but it is not illegal in the current version of this
> specification. "
>
> indicates it is not illegal to use non-fixed size data type instances.
> (not that I like them as you know)
>
>
>
> The fact that you think you need it here may be due to an incompleteness
> in the model as I described in my previous email.
>
> It may well be that the structure of the mapping, including explicitly
> representation of what-is-mapped-to-what, could make the need for an
> explicit indication of forward vs inverse redundant.
>
> So looking forward to seeing more details of the model (and I can comment
> on another thread).
>
>
>
> Cheers
>
> Gerard
>
>
>
>
>
> There are flavors which have open ended list of content
>
>    Lookup table has open ended list of Entries
>
>    Polynomials have open ended list of Coefficients,  to avoid
> individually modeling the different order of polynomial functions.
>
>
>
> DataTypes are supposed to have fixed size.
>
>
>
> Mark
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/dm/attachments/20200309/f1b7e9f8/attachment.html>