If you want to collaborate on the PsychoPath/XSLT 2.0 project, I'm
willing to host the code on the Bilrost github site. This would at least
give it a place to reside publicly until it can be determined where it
will eventually reside.
https://github.com/organizations/bilrost
Please let me know if
I'm glad to see that Xalan is starting a reboot. One thing I think the
PMC is going to need to investigate with the Apache Software Foundation
is obtaining access to the W3C XSLT 2.x/3.x test suite. Unfortunately
this is not publicly available like the W3C Test Suite for XQuery is.
Re-crea
The biggest thing you'll need to implement besides the new Parser
language for XPath 2 is the function library.
There are over 100 functions and a handful of operations.
The good thing is that the XSLT workingroup had created a Test suite,
that you can run processors against for XPath2/XQuery
I've been following this list for months, and it amazes me that it has
taken the threat of moving the project to the Attic to realise that
there is a hole in the 3 PMC requirement to keep a project going.
According to Ohloh.net, the existing committers and PMC pretty much
abandonded the Xalan-
I'd be interested in helping you guys out. I already have a future fork
of Xalan code in GitHub.
https://github.com/kingargyle/bilrost
I've got a branch where I've mavenized the build, which makes it a bit
simplier to get started. Not much work has happened. I'm also one of the
committers for the
I just cloned the xalan-j trunk, and there have been no active commits
to Xalan-J in the last 17 months.
So for all intents and purposes, I would suspect that none of the
existing PMC members for Xalan-J are actively involved. The problem
with Xalan and Xalan-J in general was the lack of pro
This has been discussed on and off, and it might be possible to plug,
the PsychoPath XPath 2.0 processor into Xalan or extend Xalan to use it.
I know that the Xerces-J folks are using it for there XML Schema 1.1
implementation.
http://wiki.eclipse.org/PsychoPathXPathProcessor
Dave
On 04/11/2011
You may be interested in the Test Suite for XSLT 1.0 and XPath 1.0
provided by OASIS.
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xslt
I know for XPath 2.x, XSLT 2.x, and XQuery 1.x the W3C has created a
very large test suite for use by implementers.
Dave
On 06/24/2010 03:06
might
> implement the ItemPSVI interface of the Xerces XML Schema API?
and you reponded:
David Carver wrote on 04/11/2010 09:48:22 AM:
> For XML Schema Awarness which PsychoPath supports, it requires
> Xerces-J. For all other DOM's that are given to it, it defaults to
&
for Xalan"
Best regards
Xunlong Gui
2010-04-11
ustbcoder
----
*发件人:* David Carver
*发送时间:* 2010-04-11 21:40:21
*收件人:* ustbcoder
*抄送:* xalan-dev@xml.
Answers in line.
Thanks for your thoughts. I've spent a few minutes looking at some of
the PsychoPath documentation, and I have a few questions and comments:
1. What is the form of the input accepted by PsychoPath? Is it
restricted to taking a DOM (Level 2?) input tree - whose nodes might
Gui
2010-04-11
ustbcoder
*发件人:* Henry Zongaro
*发送时间:* 2010-04-11 20:47:00
*收件人:* xalan-dev@xml.apache.org
*抄送:* David Carver
*主题:* Re: implement XPath 2.0 function for xalan
Hi, Jesper.
Jesper Møller wrote on 04/01/2
You guys may be able to speed some of this up by leveraging the
PsychoPath XPath 2.0 processor that is at Eclipse.
It is already being used by Xerces-J for XSD 1.1 Assertion support. Why
re-invent the wheel if you can leverage something that already exists.
http://wiki.eclipse.org/PsychoPathXPath
Just a suggestion that if you are going to look into XSLT 2, you might
want to look at using the PsychoPath XPath 2.0 processor for the XPath
2.0 support. It is fully schema aware, and is open source under an
Eclipse Public License.
The Xerces-J project is using it for their XPath 2.0 asserti
Can you elaborate on this David? Is this a proprietary processor, or
open source? url? What do the Xalan guys think about this, are they
going to EOL Xalan or are they waiting for resources to catch up to 2.0?
--- On Tue, 10/11/09, David Carver wrote:
> From: David Carver
> Subject: Re:
And unfortunately, IBM which provided the original basis for Xalan has
decided to do their own XSLT 2.0 processor instead of making Xalan XSLT
2.0 capable. Even though there is code in Apache's source code control
system that has the basis for XSLT 2.0 support.
Dave
Mukul Gandhi wrote:
On T
16 matches
Mail list logo