[DFDL-WG] clarification: textBooleanTrue/FalseRep cannot be empty string? textStandardNaNRep and friends cannot be empty string.

Steve Hanson smh at uk.ibm.com
Tue May 24 11:04:23 EDT 2016


Mike

I came to write up the issue tracker for this and had a thought.  Property 
textStandardZeroRep says:

The empty string means that there is no special literal string for zero. 

I wondered if the equivalent is a better interpretation of empty string 
for textStandardNanRep and textStandardInfinityRep ? 

Regards
 
Steve Hanson
IBM Integration Bus, Hursley, UK
Architect, IBM DFDL
Co-Chair, OGF DFDL Working Group
smh at uk.ibm.com
tel:+44-1962-815848
mob:+44-7717-378890



From:   Steve Hanson/UK/IBM
To:     Mike Beckerle <mbeckerle.dfdl at gmail.com>
Cc:     "dfdl-wg at ogf.org" <dfdl-wg at ogf.org>
Date:   19/05/2016 21:53
Subject:        Re: [DFDL-WG] clarification: textBooleanTrue/FalseRep 
cannot be empty string? textStandardNaNRep and friends cannot be empty 
string.


Agree that textBooleanxxxRep properties should state empty string not 
allowed.

The textStandardNanRep and textStandardInfinityRep properties should state 
empty string not allowed. The others you list already mention empty 
string.

Regards
 
Steve Hanson
IBM Integration Bus, Hursley, UK
Architect, IBM DFDL
Co-Chair, OGF DFDL Working Group
smh at uk.ibm.com
tel:+44-1962-815848
mob:+44-7717-378890




From:   Mike Beckerle <mbeckerle.dfdl at gmail.com>
To:     "dfdl-wg at ogf.org" <dfdl-wg at ogf.org>
Date:   19/05/2016 17:38
Subject:        [DFDL-WG] clarification: textBooleanTrue/FalseRep cannot 
be empty string? textStandardNaNRep and friends cannot be empty string.
Sent by:        "dfdl-wg" <dfdl-wg-bounces at ogf.org>




We don't stipulate that textBooleanTrueRep nor textBooleanFalseRep cannot 
be empty string.

We do stipulate that entity ES is not allowed. So I expect these 
properties cannot be "" meaning the same thing that "%ES;" would mean. 
Since we disallow the latter, we should disallow just "".

Similarly, for textStandardGroupingSeparator, textStandardExponentRep, 
textStandardNaNRep, and textStandardInfinityRep we specify that the string 
literal value behaves as specified in textStandardDecimalSeparator, but we 
don't specify that these cannot be empty string (which is specified in 
textStandardDecimalSeparator, but not in the "Text Number Character 
Restrictions" part of that property description that is referenced from 
these other properties.)

ES and WSP* are not allowed, so almost certainly empty string should not 
be allowed. 




Mike Beckerle | OGF DFDL Workgroup Co-Chair | Tresys Technology | 
www.tresys.com
Please note: Contributions to the DFDL Workgroup's email discussions are 
subject to the OGF Intellectual Property Policy
--
  dfdl-wg mailing list
  dfdl-wg at ogf.org
  https://www.ogf.org/mailman/listinfo/dfdl-wg


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/dfdl-wg/attachments/20160524/5e2d35d7/attachment.html>


More information about the dfdl-wg mailing list