[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reply to: [list | sender only]
Re: Draft JSON specification for CIF
- Subject: Re: Draft JSON specification for CIF
- From: Marcin Wojdyr <wojdyr@xxxxxxxxx>
- Date: Thu, 13 Apr 2017 17:14:21 +0100
- 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=Iu9GVLjEcjzhbTXKZjcZMLt7YYKB2lW2/fpmy+hZIsg=;b=SwNS1JJj+WZXRuxAtFU3BZ0HaovAkdyQvhSK3KwS4Kl+OK19tbIsTEy4G5pE7JwpCaAN1lxMO2c/QuHpjAoOJxCnZ+Z9YgTM0YVAL8HZirXM5zrEtUf22jbrt34k1jgYH5tu2qRobnmAcnrp1eISCOOrv9cdf+Jx9Muf62W/ZYrGCeQkxfxhp3UmpSRuqA/BfIXmMkWg4XlRfj2Nxa42VZ7/DjcYX9Si17T1EeaA8vVOWQtQCCdbFOBvPuiMUqkEXws+SZx8e363zy81UBauzCosrc0EKPVsX+L/CfSwXee/4uj1kL7ahST222Ur4Var/QIBxHnIugOjMsUyEjXJwg==
- In-Reply-To: <3a456373-cdf3-229f-f4c8-3a7271575d92@gmail.com>
- References: <CAM+dB2fszww=4A_w6evqg=5O9KKLnujajmg_SPSX=hCRQiBPtg@mail.gmail.com><CAF_YUvWgON8Z3JS1TePu3K=SRErN4TBhNTP1Q3GfdJeoLnymMw@mail.gmail.com><CACaHzQU+25tZQXe1EKUFi4y+UJfa+rA6z7F7Y2EvWhX=Jg6P8g@mail.gmail.com><3a456373-cdf3-229f-f4c8-3a7271575d92@gmail.com>
On 13 April 2017 at 16:42, Andrius Merkys <andrius.merkys@gmail.com> wrote:> Dear Marcin,>> that's why I suggest retaining CIF value types. CIF parser knows the> type of each value read (here is the difference between ? and '?') and I> suggest storing this bit of information inside JSON explicitly. Dear Andrius,Retaining all the information (single quote vs double quote, etc.) hassome uses, but there are trade-offs to consider. Files used for macromolecular structures can be big. If you convert3j3q.cif (250MB) to the JSON you use, you will end up with even biggerfile.Or the chemical components dictionary:ftp://ftp.wwpdb.org/pub/pdb/data/monomers/components.cifwhich has similar size.So being more explicit makes it slower to download and parse resulting file. Another thing is simplicity. I wrote a simple cif->json to checkcorrectness of my parser (for example by comparing the output withJMol).If the JSON format is simple, it's worth to add JSON writer to CIFparser just for the sake of testing. If JSON schema is too elaborate,it may not be worth. Cheers,Marcin_______________________________________________cif-developers mailing listcif-developers@iucr.orghttp://mailman.iucr.org/cgi-bin/mailman/listinfo/cif-developers
Reply to: [list | sender only]
- Follow-Ups:
- Re: Draft JSON specification for CIF (Andrius Merkys)
- References:
- Draft JSON specification for CIF (James Hester)
- Re: Draft JSON specification for CIF (Robert Hanson)
- Re: Draft JSON specification for CIF (Marcin Wojdyr)
- Re: Draft JSON specification for CIF (Andrius Merkys)
- Prev by Date: Re: Draft JSON specification for CIF
- Next by Date: Re: Draft JSON specification for CIF
- Prev by thread: Re: Draft JSON specification for CIF
- Next by thread: Re: Draft JSON specification for CIF
- Index(es):