Re: removing HTML flow objects?

The MSXSL parser transforms XML into HTML. This I believe will remain
unchanged.

I believe, and I am not privy to any inside information, this is only
gleaned from tid-bits I have picked up on the list, that the WG considers
that using HTML syntax to create flow objects is too confusing to the
average user.

In the following example:-

<xsl>
  <rule>
 <!--here is the pattern part of the rule-->
   <target-element type= "greeting"/>
 <!--here is the action part of the rule-->
  <DIV color= "blue">
  <children/>
  </DIV>
  </rule>
 </xsl>
 <!--This rule uses CSS/HTML flow objects-->

We are creating a DIV type flow object with the CSS propert of "color" and a
value of "blue". It is this that I believe the WG may alter although I for
one believe it will be a HUGE mistake if they do, because it will
immediatley drive away 90% of the potential users of XSL.

Frank
-----Original Message-----
From: Ed Burns <edburns@xxxxxxx>
To: xsl-list@xxxxxxxxxxxxxxxx <xsl-list@xxxxxxxxxxxxxxxx>
Date: Friday, May 22, 1998 10:40 AM
Subject: removing HTML flow objects?


>On Fri, 22 May 02:35:33, The XSL-List Digest wrote:
>> From: "Frank Boumphrey" <bckman@xxxxxxxxxxxxx>
>
>> I only hope that if the XSL WR is changed, as I have heard it rumored, to
>> exclude HTML flow objects, that MS will rapidly come out with a parser to
>> interpret the new set of flow objects!!
>
>What's this about removing HTML flow objects?  The ability to render
>XML/XSL into HTML is a major boon.  Also, the decision to include HTML
>flow objects for ease of adoption was a sound one.  Please give me more
>info on this troubling development.
>
>Thanks,
>
>Ed
>
>
> XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


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