[vo-dml] Clarification on composition rule..

[CresitelloDittmar, Mark]

I think this part relates to the question at hand:
 * If the operation is a DataType, then I can have Attributes for forward
and inverse, which would be just as good.

I've tried to stick with the spirit of the vo-dml spec, and avoid the
warnings as much as possible.
If people are OK with it in this case, it'd make my life a bit simpler.  I
just don't want it to come back and bite me in the end (double meaning
there :) ).

Mark



On Mon, Mar 9, 2020 at 9:05 AM 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).
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/dm/attachments/20200309/0b2f920e/attachment.html>