<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Small correction: consistency comes with matching the model, so I meant to support option 1, not 2...</div><div>Brian</div><br><div><div>On 2015-06-18, at 9:59 AM, Brian Major wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi grid,<div><br></div><div>In support of a more scalable VOSI /tables interface, we will start a 1.1 WD of the IVOA Support Interface document.</div><div><br></div><div>There is, however, one issue that remains: whether or not to include the $dbSchema segment in the rest interface to the new /table endpoint. An initial email thread of a discussion of this point can be seen here:<br><div><br></div><div><a href="http://mail.ivoa.net/pipermail/grid/2015-May/002728.html">http://mail.ivoa.net/pipermail/grid/2015-May/002728.html</a><br></div><div><br></div>Should the REST endpoint match the, potentially flawed, XML model which includes the dbSchema (option 1), or should we try to correct the new /table REST endpoint now and fix the XML model later? (option 2). (If I've misunderstood the arguments please correct me.)</div><div><br></div><div>My preference is for consistency so vote option 2, but I'd like to hear opinions from the wider grid community so please state your opinions.</div><div><br></div><div>Regards,</div><div>Brian<br clear="all"><div><br></div></div></div>
</blockquote></div><br></body></html>