How about
 
     lengthKind="fillAvailableSpace"

or

    lengthKind="fitIntoAvailableSpace"

Seems clear. We have to not be squeamish about long enum names when they really make things clearer.

...mikeb

Mike Beckerle
STSM, Architect, Scalable Computing
IBM Software Group
Information Platform and Solutions
Westborough, MA 01581
direct: voice and FAX 508-599-7148
assistant: Pam Riordan  
                 priordan@us.ibm.com
                 508-599-7046




"Simon Parker" <simon.parker@polarlake.com>
Sent by: dfdl-wg-bounces@ogf.org

08/30/2007 07:28 AM

To
<dfdl-wg@ogf.org>
cc
Subject
Re: [DFDL-WG] v4 on length/occurs simplification proposal





My initial reaction is that 'maximum' is too close to 'maxOccurs'.
 
'Fill' is concise and meaningful, but a little to general.
'fillContainer' might be considered, but it's not specific about which container is to be filled.
'fillEncloser' would address that, but sounds forced.
'fillParent' is my favourite at the moment.
 
 Simon
 


From: dfdl-wg-bounces@ogf.org [mailto:dfdl-wg-bounces@ogf.org] On Behalf Of Mike Beckerle
Sent:
29 August 2007 23:10
To:
dfdl-wg@ogf.org
Subject:
[DFDL-WG] v4 on length/occurs simplification proposal



How's lengthKind="maximum" sound for the "endOfData" fitting into a box thing? Other possibilities in this doc:




Mike Beckerle
STSM, Architect, Scalable Computing
IBM Software Group
Information Platform and Solutions
Westborough, MA 01581
direct: voice and FAX 508-599-7148
assistant: Pam Riordan  
                priordan@us.ibm.com
                508-599-7046
--
 dfdl-wg mailing list
 dfdl-wg@ogf.org
 http://www.ogf.org/mailman/listinfo/dfdl-wg