[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reply to: [list | sender only]
Re: Problems with CIF BNF
- To: "Discussion list of the IUCr Committee for the Maintenance of the CIFStandard (COMCIFS)" <comcifs@iucr.org>
- Subject: Re: Problems with CIF BNF
- From: Joe Krahn <krahn@niehs.nih.gov>
- Date: Fri, 16 Mar 2007 12:25:17 -0400
- In-Reply-To: <20070316133946.GB17402@emerald.iucr.org>
- References: <45F5918A.4030602@niehs.nih.gov> <a06230902c21b5216f07d@[192.168.10.211]> <45F5B86D.7090100@niehs.nih.gov> <a06230904c21bb879317d@[192.168.2.101]> <45F69E91.10109@niehs.nih.gov><20070316133946.GB17402@emerald.iucr.org>
Brian McMahon wrote: ... > Much of what is projected in DDLm goes beyond any existing > XML schema-based validation, and it's important for > software developers to concentrate on the potential > of methods-based validation, rather than getting hung up on > the detail of the CIF format. I agree that my recent posts about CIF BNF are a bit verbose. It's not that I think a prefect BNF is needed, but that the basic syntax is really important to get right because so much is built on it. None of the discrepancies are major problems, but I have noticed messages on the the CIF related lists that actual compatibility problems have resulted. With plans to incorporate even more features, like bracketed data items, which are going to require parser updates, it seems that now is a good time to get some of these issues resolved. Joe
Reply to: [list | sender only]
- References:
- Problems with CIF BNF (Joe Krahn)
- Re: Problems with CIF BNF (Herbert J. Bernstein)
- Re: Problems with CIF BNF (Joe Krahn)
- Re: Problems with CIF BNF (Herbert J. Bernstein)
- Re: Problems with CIF BNF (Joe Krahn)
- Re: Problems with CIF BNF (Brian McMahon)
- Prev by Date: Re: Problems with CIF BNF
- Next by Date: Re: New accent modifier types?
- Prev by thread: Re: Problems with CIF BNF
- Next by thread: Escape code issues
- Index(es):