[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reply to: [list | sender only]
Re: mmCIF specification
- Subject: Re: mmCIF specification
- From: Marcin Wojdyr via cif-developers <cif-developers@xxxxxxxx>
- Date: Wed, 3 Jun 2020 16:09:59 +0200
- Cc: Marcin Wojdyr <wojdyr@xxxxxxxxx>, James Hester <james.r.hester@xxxxxxxxx>, Forum for CIF software developers <cif-developers@xxxxxxxx>
- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;h=mime-version:references:in-reply-to:from:date:message-id:subject:to:cc; bh=h7lQLf55yNMjQ3rninuaTxApEm3mIT6tLeDtt7brt5w=;b=JxinyG9xDDpLJX2QAniVUkHYQsFVB2ut+hSaF0FaEjCCV6sH+CGx5+Hw/+F4SvtqSdeLL9qRpi5hvAd2J/w6bhx+qJDl6ei5c7rC8n7EYMImqen51cnIyf/3jt30psuilRkZghxJBE7h1HdLurZ7bCYScwYX5rfwzTQPsZH6LHlUyYb6eQGlQdrO3MK/xjqRMze1e7Iu6QQKHFuLj939VLGzgsk4fpliFSQfIxdxeHn9cfBrlx8JSOk4qOhVYapcRz/s4kKxFIlFpSPeFLr/IQxstS7Id3iKFl6MPxtcpBLp0qSs9zMaoGYBT0OuU/Wo0iRgdbcYqCiCOk66H9pj7g==
- In-Reply-To: <CABcsX277-WzoNNnMtDkjRL0WNsorQ7hXh=gB4rqdHZHNLZCcxQ@mail.gmail.com>
- References: <CACaHzQVtQe=BgdBZAfGwVikBQFNNmmxXUat6rVxd2r=EJCRX1Q@mail.gmail.com><CAM+dB2eoTp6qrJbfeMOEpRX1XEsSEDiMzUsY81xfOnCU1vkPOg@mail.gmail.com><CACaHzQWattMotoX5fv+fe30g1_J+Lz3LXUgbHX46rYX0KVzKzg@mail.gmail.com><CAM+dB2f3W+uBzH27-7kK9PG4naoKJQuhvzaGfkYu7j2Qsvb4RA@mail.gmail.com><CABcsX277-WzoNNnMtDkjRL0WNsorQ7hXh=gB4rqdHZHNLZCcxQ@mail.gmail.com>
Thanks for letting me know about imgCIF, now I see how it's going to work. > "But what is the procedure to make a mandatory, but never needed mmCIF item> non-mandatory?">> However, if you are the maintainer of a large, complex evolving body of data, and want some> reasonable chance of maintaining the ability to search for and retrieve various subsets of> columns and rows at the same time as other subsets of columns and rows are being updated> without it getting garbled, then I would urge you to a strictly follow a relational model and be sure> to keep careful track of the keys needed for the relevant schema, and to be very careful to> include information for the columns that are mandatory for the schema holding it all together. To repeat: the examples I gave are never used for anything. They arenot holding together anything._diffrn_refln.standard_code is always '1'. It could link to_diffrn_standard_refln.code, but the diffrn_standard_refln category isnever present.Similarly with _diffrn_refln.scale_group_code. But this discussion should have been started in a wwPDB forum, so I'mmoving there. Best wishes,Marcin_______________________________________________cif-developers mailing listcif-developers@iucr.orghttp://mailman.iucr.org/cgi-bin/mailman/listinfo/cif-developers
Reply to: [list | sender only]
- References:
- mmCIF specification (Marcin Wojdyr via cif-developers)
- Re: mmCIF specification (James Hester via cif-developers)
- Re: mmCIF specification (Marcin Wojdyr via cif-developers)
- Re: mmCIF specification (James Hester via cif-developers)
- Re: mmCIF specification (Herbert J. Bernstein via cif-developers)
- Prev by Date: Re: mmCIF specification
- Next by Date: Dictionary style guide
- Prev by thread: Re: mmCIF specification
- Next by thread: Expanding category key for publ_author.name
- Index(es):