RE: Can't use any of the xdt functions! Grrrr

And AFAIK its just this WG that are doing it.
They are not following any W3C procedure.
I'd suggest people shout on the W3C comments list,
  public-qt-comments@xxxxxx 

DaveP 

    -----Original Message-----
    From: Colin Paul Adams [mailto:colin@xxxxxxxxxxxxxxxxxx] 
    Sent: 18 March 2005 23:28
    To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
    Subject: Re:  Can't use any of the xdt functions! Grrrr
    
    >>>>> "Dimitre" == Dimitre Novatchev <dnovatchev@xxxxxxxxx> writes:
    
        Dimitre> The admirable tricks recommended by Michael Kay for
        Dimitre> finding this information in the source code of 
    Saxon 8.x
        Dimitre> clearly show how difficult the W3C groups have made it
        Dimitre> for a programmer to use the reference 
    implementations of
        Dimitre> the drafts.
    
    It's a REAL pain, this switching of namespaces on every 
    working draft!
    What is an implementor meant to do, when a new drat comes out?
    
    I have two choices that I can see:
    
    1) Be honest - I haven't got round to reading the latest draft
       thoropughly enough yet to claim I have implemented it yet - so
       stick to the old namespace - then FXSL won't work for me, as
       Dimitre has had to change to accomodate saxon 8.3.
    
    or 2), change to the latest namespace, thus giving a 
    mis-leading impression.
    
    Perforce, I choose option 2.
    Meanwhile, last call drafts are to come out in a few weeks, 
    so another change will have to come.
    
    I think it's a daft idea myself. Sure, change the namespace 
    when it reaches VCR (or PR or REC - whatever), but these 
    changes every working draft help noone.
    --
    Colin Paul Adams
    Preston Lancashire
    
    

-- 
DISCLAIMER:

NOTICE: The information contained in this email and any attachments is 
confidential and may be privileged.  If you are not the intended 
recipient you should not use, disclose, distribute or copy any of the 
content of it or of any attachment; you are requested to notify the 
sender immediately of your receipt of the email and then to delete it 
and any attachments from your system.

RNIB endeavours to ensure that emails and any attachments generated by
its staff are free from viruses or other contaminants.  However, it 
cannot accept any responsibility for any  such 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