<div dir="ltr">HI Mark<br><div class="gmail_extra"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div class="gmail_extra"><div class="gmail_quote"><div>...</div></div></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div class="gmail_extra"><div class="gmail_quote"><div>The question is where does this get defined:<br></div><div> 1) as ivoa:anyType base type.. which you've explained would require restructuring the vo-dml types, so is sub-optimal<br></div><div> 2) as ivoa:DateQuantity base type </div></div></div></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div class="gmail_extra"><div class="gmail_quote"><div> 3) as coords:DateQuantity type.. local extension to ivoa:Quantity which doesn't feel like playing nice with the base types<br></div><div> 4) do you have another proposal?<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888"><div><br></div></font></span></div></div></div></div></blockquote><div>Without being able to take the time to understand your model in all detail, I guess your option 2) might be ok. How would you want that to be modeled?</div><div>Gerard</div><div><div dir="ltr"><div><div class="gmail_extra"><div class="gmail_quote"><span class="HOEnZb"><font color="#888888"><div><br></div><div><br></div></font></span></div></div></div></div>
</div></div><br></div></div>