Re: Barry Leiba's Yes on draft-ietf-xmpp-6122bis-23: (with COMMENT)
Barry Leiba <[email protected]> Tue, 9 Jun 2015 17:41:46 +0100
| Newsgroups | gmane.ietf.xmpp |
|---|---|
| Message-ID | <CALaySJ+hMRXMjVW76YQK9_5wsc1yK=K07QLsW94s26D3Mvo-XA@mail.gmail.com> |
Hi, Peter; thanks for the response. > OLD > The domainpart of a JID is that portion which remains once any > portion from the first '/' character to the end of the string has > been removed (if there is a '/' character present), and then any > portion from the beginning of the string to the first '@' character > (if there is a '@' character present). > > NEW > The domainpart of a JID is that portion which remains once the > following parsing steps are taken: > > 1. Remove any portion from the first '/' character to the end of the > string (if there is a '/' character present). > > 2. Remove any portion from the beginning of the string to the first > '@' character (if there is a '@' character present). > > This parsing order is important, as illustrated by example 15 in > Section 3.5. Nice; thanks. >> In Section 3.3.1, I find the "i.e."s to be distracting clutter, and >> mildly recommend rendering those lines like this: >> >> U+0022 (QUOTATION MARK): " >> U+0026 (AMPERSAND): & > > This might be confusing... > > U+003A (COLON): : Ah, true. > So I'll change the order to: > > " U+0022 (QUOTATION MARK) > & U+0026 (AMPERSAND) > ' U+0027 (APOSTROPHE) > / U+002F (SOLIDUS) > : U+003A (COLON) > < U+003C (LESS-THAN SIGN) > > U+003E (GREATER-THAN SIGN) > @ U+0040 (COMMERCIAL AT) Yes, that's a good way to handle it. b