 |
 |
 |
"Michael Kay" <mhk@m...> writes:
> I was looking again at the sentence in 4.2.1:
>
> During schema construction, implementations must retain .QName. values for
> such references, in case an appropriately-named component becomes available
> to discharge the reference by the time it is actually needed
>
> It seems implementations have to retain much more than QName values to do
> late binding of schema components. For example, until you know the type of
> an element or attribute declaration you don't know whether its
> default/fixed/enumeration values are namespace-sensitive (QNames or
> notations), so you have to keep not only their lexical representation but
> also their entire namespace context! This part of the spec seems to leave an
> awful lot unsaid...
Yup. Speaking only for myself, the true extent to which the
architecture of the REC requires lazy construction/late binding
emerged very late in the process, and its pervasive impact is not
well-documented in the spec.
ht
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
Half-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@i...
URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
From k.buchcik@4... Wed Oct 06 09:04:11 2004
Received: fro
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |