I note with dismay that the XInclude CR draft specifies a _different_ algorithm for computing the [references] property of attributes from the Infoset REC itself. The Infoset REC is clear that duplicate IDs are _not_ available as referents, and so an IDREF to such an ID has no [references] property. The XInclude CR draft follows XPath 1.0 (but note _not_ XPath 2.0) and _does_ give such IDREFs a [references] property, pointing to the host of the first of the conflicting IDs. I think this is a _serious_ bug and that XInclude should be brought in to line with the Infoset REC. ht -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh W3C Fellow 1999--2002, part-time member of W3C Team 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail really from me _always_ has this .sig -- mail without it is forged spam]Received on Friday, 19 July 2002 09:33:50 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:09:31 UTC