W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2007

[Bug 4595] 1.0.3dev: document(*) with undefined context item

From: <bugzilla@wiggum.w3.org>
Date: Wed, 06 Jun 2007 08:30:25 +0000
To: public-qt-comments@w3.org
Message-Id: <E1HvquP-0003j7-Cm@wiggum.w3.org>


------- Comment #7 from mike@saxonica.com  2007-06-06 08:30 -------
>I don't know whether this is significant, but in the table in C.1, a monospaced font is used for the word "none" for the static type of the context item. 
Other items marked as "none" use a sans-serif font.  This lead me to believe
that it was talking about the FS type "none".

Yes, and the fact that someone added "(raises error on access)" also suggests
that someone was thinking this way. Of course implementations are allowed to
set a different default/initial value and I strongly suspect most systems in
practice have a default of item().

But we do seem to be finding quite a few areas where implementations are
interpreting the spec in radically different ways. 
Received on Wednesday, 6 June 2007 08:30:28 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:33 UTC