Re: Microsoft extensions to XSL

[Andrew Bunner <bunner@xxxxxxxxxxxxxxxxxx>]

>> the functionality is needed for a great many applications and if the
>> standard doesn't provide it, then proprietary extensions must.
>
>The standard doesn't provide it because there is no standard.  There
>is a draft, explicitly in progress and not done yet.  This
>functionality is intended, but not this way; investing effort in
>ECMAScript-based solutions will only waste your time.

  What kind of non-script solution would be able to do all the things that
people want -AND- let them do these things without learning a new language or
set of tags?

  I don't like Microsoft's strategy of trying to "de-commoditize" standards,
but look at what they're giving developers. Not only can people do new things,
but there's virtually no learning curve. Microsoft is letting developers apply
their existing Java Script knowledge to the problem.

  If the extension mechanism proposed by the WG isn't AT LEAST AS GOOD as
Microsoft's, my guess is that Microsoft will win. (ie developers will use
propietary extensions and end users will decide to use the client software that
supports those extensions)
  

-- Andrew

   Andrew Bunner
   President, Mass Quantities, Inc.
   bunner@xxxxxxxxxxxxxxxxxx
   Professional Supplements for the Perfect Physique
   http://www.massquantities.com 
   


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list