<html><head></head><body><div style="color:#000; background-color:#fff; font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_ym19_1_1511190009160_146391"><span>Hi Colleagues</span></div><div id="yui_3_16_0_ym19_1_1511190009160_146481"><span><br></span></div><div id="yui_3_16_0_ym19_1_1511190009160_146484"><span id="yui_3_16_0_ym19_1_1511190009160_146483">A few comments expressed a slight preference for option 2 below, rejecting updates with multiple whitespace. So with my devil's advocate hat on let me make a comment.</span></div><div id="yui_3_16_0_ym19_1_1511190009160_146487"><span><br></span></div><div id="yui_3_16_0_ym19_1_1511190009160_146490" dir="ltr"><span id="yui_3_16_0_ym19_1_1511190009160_146521">Putting multiple whitespaces in any text string in the database input has no meaning or benefit to anyone</span><span id="yui_3_16_0_ym19_1_1511190009160_146489"><span id="yui_3_16_0_ym19_1_1511190009160_146522"> (except in "remarks:" for formatted information blocks)</span>. So when it occurs it is an obvious typo or misunderstanding of how the database works. The fix for it, compressing the multiple whitespaces into a single space, is clearly defined and I can't think of any situation where applying that fix would corrupt the data.</span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1511190009160_146639"><span id="yui_3_16_0_ym19_1_1511190009160_146489"><br></span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1511190009160_146611"><span id="yui_3_16_0_ym19_1_1511190009160_146489">If the database software applies that fix automatically in any situation (except in "remarks:") it makes the database slightly more user friendly. So I don't see the need to reject any update for this mistake, and make users do more work, when it can be so easily fixed. I don't even see the need for any informational message back to the users about applying this fix to their data. Also I would like to see this fix applied to input from Webupdates as well. It is such an obvious and easy fix, why make it an issue.</span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1511190009160_146759"><span id="yui_3_16_0_ym19_1_1511190009160_146489"><br></span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1511190009160_155002"><span id="yui_3_16_0_ym19_1_1511190009160_146489">We do have a precedence for this. If you include multiple spaces in an INETNUM range either side of the '-' they are fixed by the software and reduced to a single space. No info message is included in the ack message.</span></div><div class="qtdSeparateBR" id="yui_3_16_0_ym19_1_1511190009160_146386"><div id="yui_3_16_0_ym19_1_1511190009160_158701"><br></div><div id="yui_3_16_0_ym19_1_1511190009160_158703">cheers</div><div id="yui_3_16_0_ym19_1_1511190009160_158705">denis</div><div dir="ltr" id="yui_3_16_0_ym19_1_1511190009160_158707">co-chair DB WG</div><div dir="ltr" id="yui_3_16_0_ym19_1_1511190009160_158709"><br></div><br></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1511190009160_146381" style="display: block;"> <div style="font-family: Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1511190009160_146380"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1511190009160_146379"> <div dir="ltr" id="yui_3_16_0_ym19_1_1511190009160_146378"> <font id="yui_3_16_0_ym19_1_1511190009160_146384" size="2" face="Arial"> <hr id="yui_3_16_0_ym19_1_1511190009160_146383" size="1"> <b><span style="font-weight:bold;">From:</span></b> Tim Bruijnzeels via db-wg <db-wg@ripe.net><br> <b><span style="font-weight: bold;">To:</span></b> Database WG <db-wg@ripe.net> <br> <b><span style="font-weight: bold;">Sent:</span></b> Sunday, 12 November 2017, 7:35<br> <b><span style="font-weight: bold;">Subject:</span></b> [db-wg] Validation on "org-name:" syntax (double spaces and newlines)<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_ym19_1_1511190009160_146430"><br><div dir="ltr" id="yui_3_16_0_ym19_1_1511190009160_146432">Dear Working Group,<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1511190009160_146434"><br></div><div dir="ltr">Out of 114181 ORGANISATION objects, 112 objects use multiple consecutive whitespace in the “org-name:” attribute and only 1 uses a multi-line value. While this is a tiny fraction these objects are a bit problematic to us when we verify that the “org-name:” matches the name of the organisation that we allocated or assigned resources to in our records. We also believe that this is highly confusing to users and tools parsing these objects.<br></div><div dir="ltr"><br></div><div dir="ltr">Therefore we like to clean these objects up and remove any multi-whitespace or multi-line occurrences. We can of course follow up with these organisation individually, but the reason that I bring it up here is that we also want to have stricter syntax rules in place to prevent this from happening again. We can do either of the following:<br></div><div dir="ltr"><br></div><div dir="ltr">1) replace multi-whitespace or multi-line occurrences on input (warn, but just strip the additional space)<br></div><div dir="ltr">2) reject multi-whitespace or multi-line occurrences on input<br></div><div dir="ltr"><br></div><div dir="ltr">I am leaning towards option 2, but I would value your input.<br></div><div dir="ltr"><br></div><div dir="ltr">Kind regards,<br></div><div dir="ltr"><br></div><div dir="ltr">Tim Bruijnzeels<br></div><div dir="ltr">Assistant Manager Software Engineering and Senior Technology Officer<br></div><div dir="ltr">RIPE NCC</div><br><br></div> </div> </div> </div></div></body></html>