Altova Mailing List Archives


RE: [xsl] killing xslt

From: "M. David Peterson" <m.david@---------->
To:
Date: 5/13/2004 9:01:00 PM
I don't regret my offer at all and will contact you as soon as I return
back from my trip to Denver today.  Expect a private email from me
within the next 24 hours.

Regarding more the overall development efforts for support of XSLT 2.0
on top of .NET it seems like it would be a very good thing to begin an
all encompassing community web base for all open-source projects that
either have plans to build from the XSLT 2.0 support they expected on
.NET or, with a very recent swift kick in the rear, to give .NET the
support for XSLT 2.0 (and I guess in the same breath XPath 2.0) in the
first place.  Ive got a fairly large database (80+ names at last count)
of domain names I have registered that in one way or another relate to
XML and related technologies.  Let me take a look through them and see
if any of them jump out at me as a logical place to host such a
project...

Anybody else have a domain or an idea for a domain that would be a good
fit for this idea.  I would be more than happy to donate both server
space and bandwidth to this effort if we feel we can garner enough
community support for such a project.

Thoughts?

<M:D/>

> -----Original Message-----
> From: Colin Paul Adams [mailto:colin@xxxxxxxxxxxxxxxxxx]
> Sent: Friday, May 14, 2004 2:42 AM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [xsl] killing xslt
> 
> >>>>> "David" == M David Peterson <m.david@xxxxxxxxxx> writes:
> 
>     David> FanFREAKINtastic!  Do you have a sense for when the port
>     David> will be completed and is there anything I can do to help?
>     David> If nothing else would love to QA this for you as Im sure
>     David> there are many here who would love to do the same :)
> 
> My estimate is about the end of the year. But as I am desperately
> short of money, this may get put well back (provided I can find some
> work - or better still, some sponsorship).
> 
> The current situation is the the XPath stuff is largely complete,
> excepting the functions (I have barely scratched the surface on them,
> but many of them are 15 minute jobs).
> 
> I'm only just starting on the XSLT code. (And I've no plans at all for
> XQuery).
> 
> This is intended to be a Basic XSLT processor, but I am leaving the
> way open for a possible future upgrade (i.e. I have copied the
> item-type changes that Mike made after Saxon 7.8).
> 
> All help is welcome. If you want to start by helping with QA, then
> building up a set of test case XPath strings is the immediate priority
> (I have regression tests in case, but they only tend to cover one
> instance of each type of XPath expression, thus leaving HUGE gaps for
> unknown bugs to sneak through).
> 
> As a starting step, you will need to install the current version of
> Gobo from CVS, plus an Eiffel compiler (there are 3 to choose from -
> all of which have free (in some sense or other) downloadable versions.
> You will want to download ESI's free version for .NET:
> http://www.eiffel.com/downloads/
> 
> Actually, just running the test suite on the .NET platform is a help,
> as I don't have windows myself.
> 
> Contact me by private email if you haven't regretted your offer to
> help (and same for anyone else who wants to join in - .NET or whatever
> - I use Linux myself).
> --
> Colin Paul Adams
> Preston Lancashire

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.