[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reply to: [list | sender only]
Re: Global section in CIF headers
- To: "Discussion list of the IUCr Committee for the Maintenance of the CIFStandard (COMCIFS)" <comcifs@iucr.org>
- Subject: Re: Global section in CIF headers
- From: Brian McMahon <bm@iucr.org>
- Date: Wed, 9 Sep 2009 14:28:15 +0100
- In-Reply-To: <279aad2a0909081949o19e8bfd2t81b851c60ad3003e@mail.gmail.com>
- References: <4AA67814.4000007@niehs.nih.gov><F429002A-90A6-4429-A9D7-51016C5180E7@ANL.gov><279aad2a0909081949o19e8bfd2t81b851c60ad3003e@mail.gmail.com>
Note that this is not very different in spirit from the existing AUDIT_LINK category in the Core (see http://www.iucr.org/__data/iucr/cifdic_html/1/cif_core.dic/Caudit_link.html ) The AUDIT_LINK definition does specify "relationships between data blocks in the current CIF", but one could extend it to external data blocks as well. If we were to do that, perhaps a case could be made for an additional data item _audit_link_block_location that specified a URI of an external file (or "." for the current file). We had very long discussions ages back about the dangers of providing such transient locations, but it still seems the only way that you can usefully do it. > Also, the nature of the relationship could be > formalised into an enumerated list to help machine-readability. That's the difficult bit! Brian McMahon > Moving on to Brian's suggestion, I think we are overdue for finding a > way to describe links between data blocks. However, using a global_ > block to do this restricts the description to a single data file. As > an alternative proposal, how about defining a CIF semantic dictionary, > with the following two datanames in it? > > _semantic.block_id > _semantic.block_relationship > > These datanames could be looped inside any datablock order to convey a > series of relationships to other datablocks, including those not in > the same file e.g. > > loop_ > _semantic.block_id > _semantic.block_relationship > > |Sydney|090909|JRH 'wavelength determination' > |Sydney|080808|VKP 'identical batch of sample' > |Sydney|070707|XYZ 'raw powder data' > |Sydney|060606|ABC 'Lebail refined structure' > > > In the example I have used a pd_block.id type construction to uniquely > identify a datablock. Also, the nature of the relationship could be > formalised into an enumerated list to help machine-readability. _________________________________________________________________________ Brian McMahon tel: +44 1244 342878 Research and Development Officer fax: +44 1244 314888 International Union of Crystallography e-mail: bm@iucr.org 5 Abbey Square, Chester CH1 2HU, England
Reply to: [list | sender only]
- Follow-Ups:
- Re: Global section in CIF headers (James Hester)
- References:
- Global section in CIF headers (Joe Krahn)
- Re: Global section in CIF headers (Brian H. Toby)
- Re: Global section in CIF headers (James Hester)
- Prev by Date: Re: Global section in CIF headers
- Next by Date: New chair of pdCIF DMG
- Prev by thread: Re: Global section in CIF headers
- Next by thread: Re: Global section in CIF headers
- Index(es):