- From: <David.Pawson@rnib.org.uk>
- Date: Tue, 20 May 2003 15:18:27 +0100
- To: public-qt-comments@w3.org
> -----Original Message----- > From: Kay, Michael [mailto:Michael.Kay@softwareag.com] > Sent: 20 May 2003 14:59 > To: Michael Rys; David.Pawson@rnib.org.uk; public-qt-comments@w3.org > Subject: RE: TR/xquery-operators/#func-doc > > > > You could see this to be the first stage of a deprecation of > > fn:document() in XPath. First, we provide a simpler function. > > In a later version, fn:document() may be removed. > > > > At least that's how I personally see the reason for keeping > > both in XPath. > > > > Best regards > > Michael [Rys] > > Actually, fn:document() was not in XPath 1.0, and is not in > XPath 2.0 now. MK, please pass on to the WG a 'customer' position. As an XSLT+XPATH *user* I don't care which spec they are in. Saxon and all other implementations implement them together. W3C chose to split them, quite possibly for good reason, but please don't expect users to support/understnad the refined separation. > > We have no plans to deprecate fn:document() in XSLT. It does > no harm, it is > merely redundant, and redundancy is not good enough reason > for deprecation. I'd appreciate a re-affirmation of that as a WG position please, noting the *we* in this mail? > > We have considered deprecating features that are harmful, such as > disable-output-escaping, but decided for the time being that we had no > formal definition of "deprecation" and it was too much > trouble to create > one. <grin/> I'd go for that deprecation. ?More trouble than its worth? regards DaveP - NOTICE: The information contained in this email and any attachments is confidential and may be legally privileged. If you are not the intended recipient you are hereby notified that you must not use, disclose, distribute, copy, print or rely on this email's content. If you are not the intended recipient, please notify the sender immediately and then delete the email and any attachments from your system. RNIB has made strenuous efforts to ensure that emails and any attachments generated by its staff are free from viruses. However, it cannot accept any responsibility for any viruses which are transmitted. We therefore recommend you scan all attachments. Please note that the statements and views expressed in this email and any attachments are those of the author and do not necessarily represent those of RNIB. RNIB Registered Charity Number: 226227 Website: http://www.rnib.org.uk
Received on Tuesday, 20 May 2003 10:18:54 UTC