<div dir="ltr"><div>Gerard,</div><div><br></div><div>I'd very much appreciate feedback on the transform model if you've reviewed it.. probably on a separate thread would be best.</div><div>This model is getting a lot of real-world exercise, being applied to both the AST and gWCS libraries.</div><div><br></div><div>So.. two compositions to the same target is supposed to be invalid?</div><div><br></div><div>Mark</div><div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Mar 7, 2020 at 3:45 AM Gerard Lemson <<a href="mailto:glemson1@jhu.edu">glemson1@jhu.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_4787261721509796850WordSection1">
<p class="MsoNormal">Actually, it seems to me from <a href="https://volute.g-vo.org/svn/trunk/projects/dm/STC/Trans/doc/WD-Trans-1.0.pdf" target="_blank">
https://volute.g-vo.org/svn/trunk/projects/dm/STC/Trans/doc/WD-Trans-1.0.pdf</a> that the model still misses a “prescription how axes or so are represented as variables". To me the essential elements for a transformation model would be representation of the
actual “things” that are being mapped or transformed and how these are represented in the operations. (I have some initial suggestion how that can be modelled if you’re interested).<br></p><p class="MsoNormal"><u></u></p>
<p class="MsoNormal"><u></u><br></p><div style="border-style:none none none solid;border-left-width:1.5pt;border-left-color:blue;padding:0in 0in 0in 4pt"><div><blockquote style="border-style:none none none solid;border-left-width:1pt;border-left-color:rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in"><div><div><div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote></div></div>