Scott,

Thanks, that is better.

-- 
 
JG



James Gould
Distinguished Engineer
[email protected] 
<applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

Verisign.com <http://verisigninc.com/>

On 1/27/20, 7:39 AM, "Hollenbeck, Scott" <[email protected]> wrote:

    > -----Original Message-----
    > From: regext <[email protected]> On Behalf Of Gould, James
    > Sent: Friday, January 24, 2020 4:25 PM
    > To: Alexey Melnikov <[email protected]>
    > Cc: [email protected]; Joseph Yee 
<[email protected]>;
    > The IESG <[email protected]>; [email protected]; [email protected]
    > Subject: [EXTERNAL] Re: [regext] Alexey Melnikov's Discuss on draft-ietf-
    > regext-login-security-07: (with DISCUSS and COMMENT)
    > 
    > Alexey,
    > 
    > I'll go ahead and add the following description of "whitespace" in 
section 1.1
    > "Conventions Used in This Document":
    > 
    > "whitespace" is based on the definition for the XML schema whiteSpace
    > datatype in [W3C.REC-xmlschema-2-20041028], which only includes the ASCII
    > whitespace characters #x9 (tab), #xA (linefeed), #xD (carriage return), 
and
    > #x20 (space).
    
    I'd recommend stronger language. It's not just "based on" the definition 
for the XML schema whiteSpace datatype, that datatype is normatively 
incorporated by reference. Perhaps something like this:
    
    '"whitespace" is defined by the XML schema whiteSpace datatype in 
[W3C.REC-xmlschema-2-20041028], which only includes the ASCII whitespace 
characters #x9 (tab), #xA (linefeed), #xD (carriage return), and #x20 (space).'
    
    Scott
    

_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext

Reply via email to