[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
For example, the _enumeration_set.xref_code and _enumeration_set.xref_dictionary attributes do not specify the particular foreign data name(s) in that foreign dictionary that the value equivalence applies to, perhaps assuming that only one data name can be equivalent to the defined data name in any given foreign dictionary. This is not strictly true in cases where the other ontology splits a category into parts, for example the 'axis' category in imgCIF might be split into 'goniometer axis' and 'detector axis' in some other ontology. _definition.xref_code allows a single foreign data name to be specified for the whole definition, but there is no reference to which dictionary this comes from, as multiple foreign dictionaries can be referenced using _dictionary_xref. Given that these attributes have clearly never been implemented, let alone tested, and are not essential to DDLm functionality (they do not appear in any of our draft or approved DDLm dictionaries) I was wondering if anybody here would like to defend their inclusion in DDLm, rather than e.g. in some future DDLm extension dictionary dedicated to interoperability. I note also that specification of foreign equivalents in a canonical dictionary would clutter definitions and those definitions might need to be kept up to date with changes in that foreign ontology (although a date is attached to each foreign dictionary).
James.
--
Reply to: [list | sender only]
[ddlm-group] Removing dictionary_xref,_definition.xref and _enumeration_xref attributes from DDLm
- To: ddlm-group <ddlm-group@iucr.org>
- Subject: [ddlm-group] Removing dictionary_xref,_definition.xref and _enumeration_xref attributes from DDLm
- From: James Hester <jamesrhester@gmail.com>
- Date: Mon, 28 May 2018 17:16:15 +1000
- DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;h=mime-version:from:date:message-id:subject:to;bh=0zVMCkSAoiPVn3JqeHbIqJMnwwYeZgxvRgx0COGGV6o=;b=ucCpd2P+gGWsIiL897KWaanDwLR+a0FzhJEn2qCr8Q20eda9chcDrVVssZcWs/L7bvOrsepCij1SZlTYlYOGvFobTvTfyNlQT62LDLiyo2nBzeBpKVyYjmf64EndmlplzUDj5CazBGGoXPnSe8cfpRqQJhyvzEO3LyUVmLfQSx/RAmNqllGxSqR3Ebkf+LoME8Q+rnDxi1hUt5nsrOBuSyyizwNC+2D3qyQ8TLuw65ANDct1omW6Mwl+Y/WZN5MlrFRUoja9wPp89QIOQ+JL308oe6tcXQ/Nhf+ciSIVKRNB+BspIqxA974wbhiGF5cHWHcRSB3mt1cy3PDu/qFB2w==
Dear DDLm group,
In preparing the Volume G chapter on DDLm I have noticed that the attributes related to cross-referencing data names with data names in other dictionaries are poorly documented. The intention of these attributes appears to be to allow data names from multiple arbitrary ontologies to be specified as equivalent to the defined data name, and provision is even made for matching enumerated values. As far as I can tell, these definitions are incomplete, and they are not mentioned in the original DDLm paper.For example, the _enumeration_set.xref_code and _enumeration_set.xref_dictionary attributes do not specify the particular foreign data name(s) in that foreign dictionary that the value equivalence applies to, perhaps assuming that only one data name can be equivalent to the defined data name in any given foreign dictionary. This is not strictly true in cases where the other ontology splits a category into parts, for example the 'axis' category in imgCIF might be split into 'goniometer axis' and 'detector axis' in some other ontology. _definition.xref_code allows a single foreign data name to be specified for the whole definition, but there is no reference to which dictionary this comes from, as multiple foreign dictionaries can be referenced using _dictionary_xref. Given that these attributes have clearly never been implemented, let alone tested, and are not essential to DDLm functionality (they do not appear in any of our draft or approved DDLm dictionaries) I was wondering if anybody here would like to defend their inclusion in DDLm, rather than e.g. in some future DDLm extension dictionary dedicated to interoperability. I note also that specification of foreign equivalents in a canonical dictionary would clutter definitions and those definitions might need to be kept up to date with changes in that foreign ontology (although a date is attached to each foreign dictionary).
Alternatively, we should be able to come up with a complete scheme that covers all of the possible interrelationships in a way that is useful (i.e. facilitates automatic interoperability with non-CIF data files).
Thoughts?--
T +61 (02) 9717 9907
F +61 (02) 9717 3145
M +61 (04) 0249 4148
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
Reply to: [list | sender only]
- Follow-Ups:
- Prev by Date: Re: [ddlm-group] Removing Octal,Hexadecimal and Binary as DDLm types
- Next by Date: Re: [ddlm-group] Proposal to allow SU corresponding to a givenMeasurand data name to be linked using _name.linked_item_id
- Prev by thread: Re: [ddlm-group] Proposal to allow SU corresponding to a givenMeasurand data name to be linked using _name.linked_item_id
- Next by thread: Re: [ddlm-group] Removing dictionary_xref,_definition.xref and _enumeration_xref attributes from DDLm
- Index(es):