[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reply to: [list | sender only]
Re: CIF-JSON draft 2017-05-15
- Subject: Re: CIF-JSON draft 2017-05-15
- From: James Hester <jamesrhester@xxxxxxxxx>
- Date: Tue, 16 May 2017 09:58:59 +1000
- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;h=mime-version:in-reply-to:references:from:date:message-id:subject:to;bh=keUX5JqxqBecC1t5vujbFtaD0uJe1Gl50j8xVYXD32k=;b=nmlGoz4PINWB4i/eHe9kqWvNI1QhqsgpRYte+lcy19vf8jnhO0+ZUY422xJglEEeu52PWf6T5GI5xdAnQc/b1GByRyaCP/g3KM8v6vpKnDXur7u6+7RFmD5WopAFtj+LBWnZUTDjVGUOqdP/sG0GuqDXC2fr+xpsw/QNPouXcYRmSUoI8VpNzQyiFSLKlZNBbdi8gUkj0YEn4OmM6/06coZFEsRfBO5VZwYvj3krVJ8dGIUjQYaNQGGAjQAmx5XYBjOWBo9LGzhZKnJSRjbu09YKIm4V8ilTLqoilWJ/LVkNx1ppiMNgLHWPdLxnYY3SuLIkLSBLabvQz6qlcYHhvw==
- In-Reply-To: <CAF_YUvXPj9g6CEnsKmwZwrp7p550nyykrnQY9iN5wpEnDzrrYQ@mail.gmail.com>
- References: <CAM+dB2cAAY3CjC741WU0GqaWmAi2iGHtwZ82iA1bCwuNoG6nQg@mail.gmail.com><CAF_YUvVa0JXgAN9Bec6fjd6Nmco5W7EHWLN=Ba=daRR9U-2PzQ@mail.gmail.com><CACaHzQVYeOfS9zTe4gDJMVNCTgxtat0zhMAd2EMX=etXj5g2Gw@mail.gmail.com><CAF_YUvWV3huhwoBuCOkKXqCcYH+8kjFCPjoa=j_v61JC4H32Jg@mail.gmail.com><CAF_YUvUMbVz2j5=XXD5WD3G+0XB4tY=r1zwXuADB14qQNZTPvg@mail.gmail.com><CAF_YUvXPj9g6CEnsKmwZwrp7p550nyykrnQY9iN5wpEnDzrrYQ@mail.gmail.com>
Hi again Bob,
--
On 16 May 2017 at 03:53, Robert Hanson <hansonr@stolaf.edu> wrote:
Two questions arising:1) CIF2 mentions byte order. This would be the (optional) first two characters of the data stream?
Byte order marks are a JSON syntax issue and thus not relevant to this specification. https://tools.ietf.org/html/rfc7159#section-8.1 states that JSON implementations must not add BOMs to streams, but parsers may ignore BOMs in the interests of interoperability.
2) list item names need not be lower-case, right? Nothing I see in CIF says that they conform to the requirements of data names. Thus, CIF2 could have upper- and lower-case names in list items.
Currently lower case is only enforced for JSON datablock names. The CIF syntaxes require that datanames appearing in a datablock must have canonical caseless forms that do not match, but the datanames themselves do not have to be presented in canonical caseless form. As case is, in general, significant for datavalues, list item names and any other datavalues may be in upper case, capitalised etc.
_______________________________________________
cif-developers mailing list
cif-developers@iucr.org
http://mailman.iucr.org/cgi-bin/mailman/listinfo/cif- developers
--
T +61 (02) 9717 9907
F +61 (02) 9717 3145
M +61 (04) 0249 4148
F +61 (02) 9717 3145
M +61 (04) 0249 4148
_______________________________________________ cif-developers mailing list cif-developers@iucr.org http://mailman.iucr.org/cgi-bin/mailman/listinfo/cif-developers
Reply to: [list | sender only]
- References:
- CIF-JSON draft 2017-05-15 (James Hester)
- Re: CIF-JSON draft 2017-05-15 (Robert Hanson)
- Re: CIF-JSON draft 2017-05-15 (Marcin Wojdyr)
- Re: CIF-JSON draft 2017-05-15 (Robert Hanson)
- Re: CIF-JSON draft 2017-05-15 (Robert Hanson)
- Re: CIF-JSON draft 2017-05-15 (Robert Hanson)
- Prev by Date: Re: CIF-JSON draft 2017-05-15
- Next by Date: Re: CIF-JSON draft 2017-05-15
- Prev by thread: Re: CIF-JSON draft 2017-05-15
- Next by thread: Re: CIF-JSON draft 2017-05-15
- Index(es):