[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Unfortunately David there seems to be a (yet confirmed) expectation that the existing CIF1 data names can be used in a new DDLm/dREL world. Hence the dilemma.
On 10/11/09 10:53 PM, "David Brown" <idbrown@mcmaster.ca> wrote:
cheers
Nick
--------------------------------
Associate Professor N. Spadaccini, PhD
School of Computer Science & Software Engineering
The University of Western Australia t: +61 (0)8 6488 3452
35 Stirling Highway f: +61 (0)8 6488 1089
CRAWLEY, Perth, WA 6009 AUSTRALIA w3: www.csse.uwa.edu.au/~nick
MBDP M002
CRICOS Provider Code: 00126G
e: Nick.Spadaccini@uwa.edu.au
Reply to: [list | sender only]
Re: [ddlm-group] CIF-2 changes
- To: Group finalising DDLm and associated dictionaries <ddlm-group@iucr.org>
- Subject: Re: [ddlm-group] CIF-2 changes
- From: Nick Spadaccini <nick@csse.uwa.edu.au>
- Date: Wed, 11 Nov 2009 15:05:29 +0800
- Authentication-Results: postfix;
- In-Reply-To: <4AF97E6B.3090803@mcmaster.ca>
Unfortunately David there seems to be a (yet confirmed) expectation that the existing CIF1 data names can be used in a new DDLm/dREL world. Hence the dilemma.
On 10/11/09 10:53 PM, "David Brown" <idbrown@mcmaster.ca> wrote:
Surely dREL is not compromised by what have been used as datanames in the past. dREL apppears only in CIF2 dictionaries and uses only the standard datanames that appear in the CIF2 dictionaries. The only place where it is necessary to be concerned about [] and / appearing in datanames is when reading in CIF1 data files. All the datanames that appear in the CIF1 dictionaries are aliased in the CIF2 dictionaries. This means that the the abilitiy to read datanames containing [] and / is only required when reading in CIF1 data files, not when reading dictionaries (the old datanames only appear in CIF2 dictionaries as delimited values in the _alias loops). At the point where the CIF value of _sint/lambda is read in, its internal name has in any case to be equivalenced to the CIF2 dictionary name (_sintoverlambda) which is data name used in the dREL stantements. Thus we are still free to place any limitations we choose on the datanames used in dREL (except for _ and . which, being punctuation, may cause problems with the names used in programming languages). However, the CIF2 dictionaries also define a _description.common dataname that contains only letters (and numbers?) and these names could be used just as easily in dREL if that were an advantage.
David
_______________________________________________
ddlm-group mailing list
ddlm-group@iucr.org
http://scripts.iucr.org/mailman/listinfo/ddlm-group
cheers
Nick
--------------------------------
Associate Professor N. Spadaccini, PhD
School of Computer Science & Software Engineering
The University of Western Australia t: +61 (0)8 6488 3452
35 Stirling Highway f: +61 (0)8 6488 1089
CRAWLEY, Perth, WA 6009 AUSTRALIA w3: www.csse.uwa.edu.au/~nick
MBDP M002
CRICOS Provider Code: 00126G
e: Nick.Spadaccini@uwa.edu.au
_______________________________________________ ddlm-group mailing list ddlm-group@iucr.org http://scripts.iucr.org/mailman/listinfo/ddlm-group
Reply to: [list | sender only]
- Follow-Ups:
- Re: [ddlm-group] CIF-2 changes (David Brown)
- References:
- Re: [ddlm-group] CIF-2 changes (David Brown)
- Prev by Date: Re: [ddlm-group] CIF-2 changes
- Next by Date: Re: [ddlm-group] UTF-8 versus extended ASCII
- Prev by thread: Re: [ddlm-group] CIF-2 changes
- Next by thread: Re: [ddlm-group] CIF-2 changes
- Index(es):