[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Reply to: [list | sender only]
Re: [ddlm-group] Elide close quotes by doubling?
- To: Group finalising DDLm and associated dictionaries <firstname.lastname@example.org>
- Subject: Re: [ddlm-group] Elide close quotes by doubling?
- From: "Herbert J. Bernstein" <email@example.com>
- Date: Fri, 4 Dec 2009 18:40:04 -0500 (EST)
- In-Reply-To: <firstname.lastname@example.org>
- References: <4B194ED7.email@example.com><firstname.lastname@example.org><alpine.BSF.email@example.com><firstname.lastname@example.org>
Dear Simon, That will depend on the mechanism chosen. From a user point of view it does not matter at what level it is implemented. What matters to the user is how to write and read such constructs and what they mean. Contrary to John's position, I view this entirely as a software engineering problem, and for that, you focus first and foremost on the user externals and then let the implementation details flow from that. Regards, Herbert ===================================================== Herbert J. Bernstein, Professor of Computer Science Dowling College, Kramer Science Center, KSC 121 Idle Hour Blvd, Oakdale, NY, 11769 +1-631-244-3035 email@example.com ===================================================== On Fri, 4 Dec 2009, SIMON WESTRIP wrote: > Sorry, once again I did not choose my words wisely :-). > > When you say that we will eventually need some mechanisms > to deal with long lines etc..., do you see these as being part of > the CIF2 syntax or handled at e.g. the dictionary level? > > Cheers > > Simon > > ____________________________________________________________________________ > From: Herbert J. Bernstein <firstname.lastname@example.org> > To: Group finalising DDLm and associated dictionaries <email@example.com> > Sent: Friday, 4 December, 2009 21:31:58 > Subject: Re: [ddlm-group] Elide close quotes by doubling? > > Just for the record, we did _not_ agree " that there were enough > alternative data value delimiters to avoid the use of any eliding > mechanism,". What we agrees to was to stop arguing about how to > use a reverse solidus and to take all strings as is. I am certain we > will eventually need some mechanisms to: > > deal with long lines > deal with quoting of arbitrary text > > But neither issue is worth holding up the use of methods as quickly > as possible. We need to get something out that will allow dictionaries > to get written using methods and out into use. The current CIF 2 > specification is adequate to allow dictionaries to get written, and > to deal with a large subset of what is needed in data files. I hope > we will continue this discussion _after_ getting CIF 2 with DDLm > out and in use to see what is appropriate to extend the useful range > of data files. > > ===================================================== > Herbert J. Bernstein, Professor of Computer Science > Dowling College, Kramer Science Center, KSC 121 > Idle Hour Blvd, Oakdale, NY, 11769 > > +1-631-244-3035 > firstname.lastname@example.org > ===================================================== > > On Fri, 4 Dec 2009, SIMON WESTRIP wrote: > > > Judging by the difficulties we had that eventually led to agreeing > > that there were enough alternative data value delimiters to avoid > > the use of any eliding mechanism (and thus returning all values as raw), > > I suspect that arguing for a different eliding mechanism will also be > > fruitless? > > > > I understand your view (Joe) about CSV, but we have to respect the > > legacy that is CIF, which is why we have a variety of delimiters. > > Otherwise, it could probably be argued that only one type of delimiter is > > necessary > > (say """")... > > > > Cheers > > > > Simon > > > > > >___________________________________________________________________________ > _ > > From: Joe Krahn <email@example.com> > > To: Group finalising DDLm and associated dictionaries > <firstname.lastname@example.org> > > Sent: Friday, 4 December, 2009 18:03:03 > > Subject: [ddlm-group] Elide close quotes by doubling? > > > > The reverse solidus (aka backslash) elide was dropped because it really > > does not work well to elide only the close quote. Now that close quotes > > are invalid when not followed by white space, it provides the > > opportunity to elide close quotes by a repeated close-quote sequence, > > similar to Fortran and CSV format. It is free of most of the > > repercussions of defining reverse-solidus as an escape character, and is > > only making use of a character sequence that would otherwise just be a > > syntax error. > > > > The caveat is that it could misinterpret valid CIF1 values. However, at > > least RCSB has done a good job of avoiding embedded quotes by picking > > alternate quoting types. > > > > There are workarounds for embedded quotes, even for CIF-within-CIF, so > > elides are not essential. However, I think this should be easy to > > implement, and free of the hassles generated by backslash escapes. > > > > Thanks, > > Joe Krahn > > _______________________________________________ > > ddlm-group mailing list > > email@example.com > > http://scripts.iucr.org/mailman/listinfo/ddlm-group > > > > > _______________________________________________ > ddlm-group mailing list > firstname.lastname@example.org > http://scripts.iucr.org/mailman/listinfo/ddlm-group > >
_______________________________________________ ddlm-group mailing list email@example.com http://scripts.iucr.org/mailman/listinfo/ddlm-group
Reply to: [list | sender only]
- Prev by Date: Re: [ddlm-group] Elide close quotes by doubling?
- Next by Date: Re: [ddlm-group] Summary of proposed CIF syntax changes
- Prev by thread: Re: [ddlm-group] Elide close quotes by doubling?
- Next by thread: [ddlm-group] Summary of proposed CIF syntax changes