Re: History: Question on C14N list of nodes instead of subtrees

>I'm not averse to more transforms; it would be useful to get an idea for
>how much motivation there might be to make changes at this point.  My
>position is that 
>	if the problem is important enough (e.g. good idea but too slow
>in a frequently occuring scenario), and
>	if it is easy for the implementations to be tweaked, 
>	then let's fix it before REC.
>So, before we stop the presses and re-architect anything, it would be
>useful to find out exactly how important the problem is.  By this I mean
>the mundane question of how frequently occuring the scenario is, but
>also the more interesting question of whether the slowness is really an
>inherent limitation we are hitting with XPath or just an implementation

I don't think that we need to change the spec or anything;
we can just throw up a new doc like exclusive c14n, or even
just add to the extra algorithms doc. I may try running
some tests if I have the time.


Baltimore Technologies plc will not be liable for direct,  special,  indirect 
or consequential  damages  arising  from  alteration of  the contents of this
message by a third party or as a result of any virus being passed on.

This footnote confirms that this email message has been swept by
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.

Received on Thursday, 24 January 2002 22:59:38 UTC