W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > January to March 2004

LC-40

From: <jrlee@charter.net>
Date: 24 Mar 2004 07:23:02 -0700
Message-Id: <200403181428.i2IESCDt067513@mxsf03.cluster1.charter.net>
To: <www-xml-schema-comments@w3.org>




Sorry for the inconvienence, but I'm having trouble tracking down the proposed resolution for this issue.  From scanning newsgroups it does'nt seem to uncommon, although I'm not seeing any viable answers.  The link below under "Actual Resolution" seems to point at a different topic.
	Is there a solution proposed for this in 1.1?
Thanks in advance,
Johnathon Lee
	

LC-40. null-and-keyref: xsi:null and keyref
Issue Class: C Locus: both Cluster: 20 keys Status: silent
Assigned to: editor Originator: Henry Thompson 
Description
Should key references with fields whose elements are xsi:null='true' be treated as if the node were not found? (Or, alternatively, as if it contained an empty string?) 
Interactions and Input
Input from  <http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000AprJun/0024.html>Henry Thompson:
ht@cogsci.ed.ac.uk (Henry S. Thompson) to XML Schema Comments list, 12 Apr 2000 15:56:40 +0100
Not key, but keyref, for a change. 
Seems to me we missed a case: if the node picked out by a keyref's field is xsi:null='true', then this should be treated as if the node had not been found. As the PWD reads, it will just use an empty string as that field's contribution to the key sequence to be looked up. 
Ditto for unique fields. 
Input from  <http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000AprJun/0202.html>Ashok Malhotra:
Your note of 4/12 confuses me. keyref fields can only refer to key fields and these are, by definition, non-nullable. 
Actual Resolution
Formal response to commentator <http://lists.w3.org/Archives/Public/www-xml-schema-comments/2000OctDec/0072.html>.
Received on Wednesday, 24 March 2004 09:22:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:02 UTC