{"action":"created","issue":{"url":"https://api.github.com/repos/genkgo/xsl/issues/3","labels_url":"https://api.github.com/repos/genkgo/xsl/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/genkgo/xsl/issues/3/comments","events_url":"https://api.github.com/repos/genkgo/xsl/issues/3/events","html_url":"https://github.com/genkgo/xsl/issues/3","id":112383140,"number":3,"title":"Any thoughts in supporting XSLT 3.0 in the future?","user":{"login":"bzerangue","id":27163,"avatar_url":"https://avatars.githubusercontent.com/u/27163?v=3","gravatar_id":"","url":"https://api.github.com/users/bzerangue","html_url":"https://github.com/bzerangue","followers_url":"https://api.github.com/users/bzerangue/followers","following_url":"https://api.github.com/users/bzerangue/following{/other_user}","gists_url":"https://api.github.com/users/bzerangue/gists{/gist_id}","starred_url":"https://api.github.com/users/bzerangue/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bzerangue/subscriptions","organizations_url":"https://api.github.com/users/bzerangue/orgs","repos_url":"https://api.github.com/users/bzerangue/repos","events_url":"https://api.github.com/users/bzerangue/events{/privacy}","received_events_url":"https://api.github.com/users/bzerangue/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-10-20T14:36:29Z","updated_at":"2015-10-20T15:55:46Z","closed_at":null,"body":"Any thoughts in supporting XSLT 3.0 in the future?\r\n\r\nhttp://www.w3.org/TR/xslt-30/\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/genkgo/xsl/issues/comments/149613971","html_url":"https://github.com/genkgo/xsl/issues/3#issuecomment-149613971","issue_url":"https://api.github.com/repos/genkgo/xsl/issues/3","id":149613971,"user":{"login":"frederikbosch","id":1552577,"avatar_url":"https://avatars.githubusercontent.com/u/1552577?v=3","gravatar_id":"","url":"https://api.github.com/users/frederikbosch","html_url":"https://github.com/frederikbosch","followers_url":"https://api.github.com/users/frederikbosch/followers","following_url":"https://api.github.com/users/frederikbosch/following{/other_user}","gists_url":"https://api.github.com/users/frederikbosch/gists{/gist_id}","starred_url":"https://api.github.com/users/frederikbosch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/frederikbosch/subscriptions","organizations_url":"https://api.github.com/users/frederikbosch/orgs","repos_url":"https://api.github.com/users/frederikbosch/repos","events_url":"https://api.github.com/users/frederikbosch/events{/privacy}","received_events_url":"https://api.github.com/users/frederikbosch/received_events","type":"User","site_admin":false},"created_at":"2015-10-20T15:55:46Z","updated_at":"2015-10-20T15:55:46Z","body":"@bzerangue Maybe. I would rather see a stable version of [Saxon C](http://www.saxonica.com/html/saxon-c/index.html) together with the corresponding PHP extension. There is also [work in Rust](https://github.com/shepmaster/sxd-xpath) that targets to replace libxslt. Unfortunately, there is no clue when these projects will be usable. That was the exact reason to start a transpiler.\r\n\r\nOf course, I am proud that there is an opportunity for XSLT 2.0 now. But a transpiler should never be the final solution.\r\n\r\nMoreover, let's first complete XSLT 2.0 with all Xpath functions. If you could help with that, awesome. Then, afterwards, we could think of implementing a W3C draft specification.\r\n"}}