<html><head>
<meta name="Generator" content="Novell Groupwise Client (Version 14.2.2 Build: 126868)">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head>
<body style="font: 10pt/normal Segoe UI; font-size-adjust: none; font-stretch: normal;"><div class="GroupWiseMessageBody" id="GroupWiseSection_1580742439000_elpenhof@astron.nl_28E1F8D0171500008001DA0021002D00_"><div>Dear Madam/Sir,</div><div><br></div><div>Please remove our email address from the mailing list.</div><div><br></div><div>With kind regards,</div><div>Liesbet Elpenhof</div><div><br></div><div><br></div><div><br></div><span id="GWSignatureSent" style="padding-right: 0px; padding-left: 0px; margin-bottom: 5px; display: block;"><span style="display: block;"><br><span style="font-size: 10pt; display: inline-block; -ms-word-wrap: normal;"><font face="Tahoma">
<div>
<div><em>Marjan Tibbe<br>Office Manager</em></div>
<div><em>Liesbet Elpenhof</em></div>
<div><em>Secretary <br>Astronomy Group Division</em></div>
<div><em></em> </div>
<div><em>ASTRON<br>Oude Hoogeveensedijk 4<br>7991 PD Dwingeloo<br>The Netherlands</em></div>
<div><em><a href="http://www.astron.nl">www.astron.nl</a></em></div>
<div><em></em> </div>
<div><em>Tel: +31 (0)521 - 595776 (Marjan)</em></div>
<div><em>Tel: +31 (0)521 - 595790 (Liesbet)<br>e-mail: </em><a href="mailto:secretaryastronomy@astron.nl"><em>secretaryastronomy@astron.nl</em></a></div>
<div> </div>
<div> </div></div></font></span></span></span><span style="margin-bottom: 5px; display: block;"><br></span><div class="GroupWiseMessageBody" id="GroupWiseSection_1580742438000_elpenhof@astron.nl_28E1F8D0171500008001DA0021002D00_"><span class="GroupwiseReplyHeader">>>> Tom Donaldson <tdonaldson@stsci.edu> 3-2-2020 15:24 >>><br></span><div><div>Dear IVOA,</div><div><br></div><div>I'm still looking for one (or more) volunteer(s) to do a code review of this astropy.io.votable pull request:</div><a href="https://github.com/astropy/astropy/pull/9505">https://github.com/astropy/astropy/pull/9505</a><div><br></div><div><br></div><div>I definitely thank Markus for the comments, indeed this PR made it clear that we have some work to do on specifying how strings are serialized in VOTable. If he or anyone else can spare a few cycles to look through the code and enter a review on github, I'd be most grateful.</div><div><br></div><div>The VOTable code does take a little learning curve at first, but anyone with both Python and VOTable familiarity should be fine. Please feel free to ask any questions here or on the github PR.</div><div><br></div><div>The set of people who know both Python and one or more VO standards is a limited resource, but one that will be very important moving forward to keep astropy and pyvo features robust and current with VO standards, and to bring in new features and reference implementations to pyvo. If you or your institution can spare some cycles for this effort, that would be terrific!</div><div><br></div><div>Best Regards,</div><div>Tom</div><div><br></div><div><br></div><div>On 1/8/20, 3:41 PM, "apps-bounces@ivoa.net on behalf of Markus Demleitner" <apps-bounces@ivoa.net on behalf of msdemlei@ari.uni-heidelberg.de> wrote:</div><div><br></div><div> External Email - Use Caution</div><div> </div><div> Dear Apps,</div><div> </div><div> On Wed, Dec 18, 2019 at 04:08:50PM +0000, Tom Donaldson wrote:</div><div> > Astropy and I would greatly appreciate if someone could have a look</div><div> > at this code, and enter a review here:</div> > <a href="https://github.com/astropy/astropy/pull/9505">https://github.com/astropy/astropy/pull/9505</a><div><br></div><div> </div><div> I've put in an informal comment for now, in particular pointing to</div><div> our previous discussion on allowing utf-8 in votable char (which I</div><div> still think is a good idea):</div> <a href="http://mail.ivoa.net/pipermail/apps/2014-October/001010.html">http://mail.ivoa.net/pipermail/apps/2014-October/001010.html</a><div><br></div><div> </div><div> In sum: I'm convinced exposing char[] as strings rather than bytes is</div><div> absolutely the right thing to do, and they'd even have my vote for</div><div> decoding from utf-8 rather than (VOTable-correct) ASCII.</div><div> </div><div> > - Lack of direction on encoding</div><div> > - Inconsistency on sizing between TABLEDATA and BINARY serializations</div><div> </div><div> ...which, incidentally, is something we don't get around, and that we</div><div> already have with unicodeChar (no XML document I've ever seen uses</div><div> UCS-2, but it's what we require in BINARY2; I'll mention in passing</div><div> that UCS-2 these days isn't part of unicode any more and then pretend</div><div> I hadn't said that).</div><div> </div><div> </div><div> There is, however, a more sinister question here (related, but it</div><div> shouldn't block the astropy PR): What do you serialise python3</div><div> strings *into*? Since you can't be sure that there's just ASCII in</div><div> these, it can't blindly be char[]. On the other hand,</div><div> unicodeChar[] as a VOTable type isn't pretty either, starting with</div><div> wasting one byte per char in >>99% of the strings in use in</div><div> astronomy.</div><div> </div><div> Since I don't have an idea for how to solve this that I like: Does</div><div> anyone here know of an elegant solution to this (i.e., have nice,</div><div> compact chars by default but let users say "I want non-ASCII here,</div><div> really" where necessary) somewhere?</div><div> </div><div> -- Markus</div><div> </div><div><br></div></div></div></div></body></html>