Re: [ddlm-group] Removing separate "Count" and "Index" types from_type.contents in DDLm

The most you could do safely is to deprecate, not remove Count and Index, since we have no way to know how many, if any, uses have been made of Count and Index, and I cannot see what is gained by removing or deprecating

them.  I would agree that is would make sense to take the small step of checking each use of Count or Index

and seeing how the those uses would look if CIF base types were used.  If we were to end up with no IUCr official uses of Count and Index, then we could explore deprecating one or the other.  Removing them abruptly would

be a mistake. 

Regards,

    Herbert

On Mon, Jul 22, 2019 at 9:32 PM James Hester <jamesrhester@gmail.com> wrote:

Dear DDLm experts,

A suggestion has been made (see https://github.com/COMCIFS/cif_core/issues/140) that we do not need all of "Count", "Index" and "Integer" types in the list of possible values for _type.contents.  "Count" is an unsigned integer, "Index" is a non-zero unsigned integer, and "Integer" is ... an integer. We have _enumeration.range which allows us to specify the lower limit of a value, and so "Integer" in combination with this is sufficient to exactly cover both "Count" and "Index".  Does anybody see a problem with removing "Count" and "Index"?

thanks,

James.
--

T +61 (02) 9717 9907
F +61 (02) 9717 3145
M +61 (04) 0249 4148

_______________________________________________
ddlm-group mailing list
ddlm-group@iucr.org
http://mailman.iucr.org/cgi-bin/mailman/listinfo/ddlm-group