1. As not all properties are relevant to choice, sequence etc shouldn't they be in the tree?
2. Aren't all occursxxx properties dependent on max/minoccurs > 1?
3. InitiatorSeparator dependent on initiator
4. Separator dependent on Delimited?

[attachment "DFDL Property Precedence (parsing) 001.mm" deleted by Alan Powell/UK/IBM]

Writing:

tbd

Notes:

- Precedence is from top to bottom recursively, so the top priority is dfdl:inputValueCalc, then dfdl:byteOrder, then dfdl:encoding, then it's children top to bottom, then dfdl:occursKind (you get the idea).

Questions arising:

- Does dfdl:escapeScheme apply when dfdl:lengthKind = endOfData ?
- Confirm that only signed logical number can have a signed rep, and only unsigned logical number can have an unsigned rep ? (change from spec 028 to 030)
- Should dfdl:terminator, dfdl:separator and dfdl:occursSeparator be lists (to handle alternative delimiters) ?  (viz dfdl:nullValues)
- Why isn't dfdl:nullIndicatorIndex encompassed by dfdl:nullIndicatorPath ?
- Use of enum 'xpath' for dfdl:nullKind.?  We've used "explicit" elsewhere and decorated syntax to indicate xpath for other properties. For nullKind maybe a better enum would be "external" or "remote" ?
- The advanced text delimiter supplement needs revision - most of its content appears to be in the core. Main question is on prefix v infix v postfix separators and how that capability is to be specified.


Regards, Steve

Steve Hanson
WebSphere Message Brokers
Hursley, UK
Internet: smh@uk.ibm.com
Phone (+44)/(0) 1962-815848

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