Hi Dan:

I see; a changing world; you are shooting at a moving target.
What is your XSL cd? Please can you annotate it with comments.

-- Karl

>From dstrom@ccs.neu.edu Tue Dec 22 11:26:49 1998
>From: "Daniel J. Strom" <dstrom@ccs.neu.edu>
>To: lieber@ccs.neu.edu
>
>Karl Lieberherr <lieber@ccs.neu.edu> writes:
>
>Hi,
>
>> Lot's of interest in your project topic.
>> 
>> What your project does is an implementation of a subset of 
>> XML/XSL. 
>> 
>> Which subset of XML and XSL are you using?
>
>For XML, I will handle almost everything.  With the help of the input
>filter, I should be able to parse everything.  However, I will ignore
>such things as processing instructions and encodings (i.e. input will
>have to be ASCII).  In the web page, I mention that I am not handling
>entities.  However, I have realized that I can handle them directly in
>the input filter.  I am not an expert in XML, but as I understand it,
>I should be able to parse almost anything.
>
>XSL, on the other hand, is a different story.  The spec is much larger
>and involves much more in the way of behavior than XML.  Thus, I will
>only be able to handle a small subset for this project.
>
>In fact, XSL has changed dramatically from what it was originally (as
>described in the documents I had when I decided to start this.
>I had a book published in 1998 which described what seems to be an
>entirely different thing.
>
>All the flow objects are new, for example (as far as I can figure
>out).  I don't think I will be getting to these.
>
>I'm hoping to handle templates along with font attributes similar to
>what I showed in my web page.
>
>> What kind of pattern matching in the construction rules
>> of XSL are you using?  What kind of flow objects do you support?
>> 
>> -- Karl
>
>
>