Re: [ddlm-group] Characterset of non-delimited stringsinsidecompou nd data items. .. .
- To: Group finalising DDLm and associated dictionaries <ddlm-group@iucr.org>
- Subject: Re: [ddlm-group] Characterset of non-delimited stringsinsidecompou nd data items. .. .
- From: "Bollinger, John C" <John.Bollinger@STJUDE.ORG>
- Date: Tue, 9 Nov 2010 13:08:35 -0600
- Accept-Language: en-US
- acceptlanguage: en-US
- In-Reply-To: <989947.2514.qm@web87012.mail.ird.yahoo.com>
- References: <AANLkTimVXn5ZEEBZx37YtgjP3g8AdZGZEise7fF=C+Ee@mail.gmail.com><alpine.BSF.2.00.1011082115550.70856@epsilon.pair.com><AANLkTikbuR2aCebXKsq_smzUhbijLWN7CrPttBQ0urLV@mail.gmail.com><370271.52057.qm@web87009.mail.ird.yahoo.com><8F77913624F7524AACD2A92EAF3BFA5416659DEE46@SJMEMXMBS11.stjude.sjcrh.local><989947.2514.qm@web87012.mail.ird.yahoo.com>
We are now drifting a bit , but it would indeed solve the problem if list and table delimiters were required to be separated from other tokens by whitespace. Alternatively, it would also be sufficient to specify that "whitespace-delimited" values must in fact be delimited by whitespace, with a special exception
to allow the : in a table key:value to serve as whitespace in that limited context. At this point, however, I would prefer simply restricting ] and }, and perhaps also [ and {, from appearing anywhere in a whitespace-delimited value. Restricting
all of them is equivalent to saying that unquoted [, ], {, and } can serve only in their delimiter roles. That seems to me a smaller change from what was previously agreed, and also a more intuitive outcome, than the other alternatives provide. Regards, John From: ddlm-group-bounces@iucr.org [mailto:ddlm-group-bounces@iucr.org]
On Behalf Of SIMON WESTRIP If the brackets in these constructs are treated as delimiters (though 'nestable' unlike the other delimiters), then perhaps both the opening and closing delimiter From: "Bollinger, John C" <John.Bollinger@STJUDE.ORG> I would be fine with disallowing all of [, ], {, and } from appearing anywhere in a whitespace-delimited data value. The [ and { do not at present cause lexical ambiguity, but there’s something
to be said for consistent treatment of opening and closing delimiters. Do note, however, that the opening [ of a list or { of a table is still required to be separated from any preceding value by whitespace. Thus _t [ depth_1[depth_1_still ] ] would contain an error at the second [. (There is still an error under the current spec or if only ] and } are forbidden in whitespace-delimited data values, but it is at the final ].) This
is still OK, though: _t [[depth_2] depth_1] John Email Disclaimer: www.stjude.org/emaildisclaimer |
_______________________________________________ ddlm-group mailing list ddlm-group@iucr.org http://scripts.iucr.org/mailman/listinfo/ddlm-group
Reply to: [list | sender only]
- Follow-Ups:
- References:
- [ddlm-group] Characterset of non-delimited strings inside compounddata items (James Hester)
- Re: [ddlm-group] Characterset of non-delimited strings insidecompound data items (Herbert J. Bernstein)
- Re: [ddlm-group] Characterset of non-delimited strings insidecompound data items (James Hester)
- Re: [ddlm-group] Characterset of non-delimited strings insidecompound data items (SIMON WESTRIP)
- Re: [ddlm-group] Characterset of non-delimited stringsinsidecompou nd data items. . (Bollinger, John C)
- Re: [ddlm-group] Characterset of non-delimited strings insidecompound data items. . (SIMON WESTRIP)
- Prev by Date: Re: [ddlm-group] Characterset of non-delimited strings insidecompound data items. .
- Next by Date: Re: [ddlm-group] Characterset of non-delimited strings insidecompound data items. .. .
- Prev by thread: Re: [ddlm-group] Characterset of non-delimited strings insidecompound data items. .
- Next by thread: Re: [ddlm-group] Characterset of non-delimited strings insidecompound data items. .. .
- Index(es):