[
https://jira.duraspace.org/browse/DS-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24718#comment-24718
]
Robin Taylor commented on DS-995:
---------------------------------
From the developers meeting of 25/4/12...
[21:05] <richardrodgers> my question here is would a simple upgrade buy us
anything, without a rewrite of XMLUI?
[21:05] <mdiggory> While I'm really for using XSLT 2.0, its destablized some
folks customizations in XMLUI when switching.
[21:05] <helix84> richardrodgers: most definitely yes
[21:05] <richardrodgers> OK do tell helix84
[21:06] <mdiggory> yes I agree, XSLT 2.0 far better than 1.1
[21:06] <mdiggory> more tools, more standard functions, more string
comparission, date comparission, localization, etc
[21:07] <helix84> richardrodgers: can't tell you off the top of my head, but
when I write XSLT, doing things in 1.0 is much more complicated than in 2.0
[21:07] <mdiggory> everything that was is EXSLT addons went into the XSLT 2.0
standard
[21:07] <helix84> richardrodgers: e.g. date-time functions
[21:08] <richardrodgers> which would simplify current logic in stylesheets?
[21:08] <helix84> richardrodgers: exactly
[21:08] <robint> What would be required to make the change ?
[21:09] <mdiggory> Xalan loosing developer resources is part of the reason you
do not see 2.0 as more ubiquitous. There was no one in Apache to port Xalan, so
the XSLT community fragmented into two camps... Saxon/XSLT 2.0 vs Xalan/XSLT1.1
[21:09] <richardrodgers> mdiggory: is there an open source Saxon available for
us?
[21:10] <richardrodgers> as in FOSS
[21:11] <mdiggory> http://mvnrepository.com/artifact/net.sf.saxon/Saxon-HE/9.4
[21:12] <mhwood> That one is MPL, I think.
[21:12] <richardrodgers> reason I ask, is historically the 2.0 Saxon was not
freely licensable....
[21:12] <mhwood> http://saxon.sourceforge.net/
[21:14] <richardrodgers> cool, so that may no longer be a concern, if I'm
reading this correctly
[21:14] <mdiggory> no one really needs schema aware processing...
[21:15] <helix84> mdiggory: does the sentence starting "Saxon-HE does not offer
all the capabilities..." have any adverse effect in DSpace compared to current
Saxon in DSpace?
[21:15] == kompewter [[email protected]] has joined
#duraspace
[21:16] <mdiggory> yes, I think the real challenge is that Michael Kay didn't
like seeing saxon distributed through maven in the past. I think he caved and
realized thats a standard for distributing java libs today
[21:16] <helix84> helix84: the sentence is inyour sourceforge link
[21:17] <mdiggory> helix84: we are not neccessarily using XQuery or Shema Aware
Processing...
[21:17] <helix84> IIRC, Michael Kay had a problem with ensuring license terms -
that license text files must be downloaded every time the JAR is downloaded.
Since he put it in Maven, that must have been resolved now.
[21:17] <mdiggory> The feature set of Saxon HE still outpaces Xalan
[21:18] <mdiggory> Package the license in the jar ;-)
[21:19] <helix84> mdiggory: no, it was for 3rd party libs
[21:19] <richardrodgers> So if there are no licensing issues, and no
backward-compatibility issues, I'm for it
[21:20] <mdiggory> the dependencies are already jars in the maven central
repo....
[21:20] <robint> So it is as simple as changing our dependencies ?
[21:20] <mdiggory> theres some changes in cocoon to enable saxon
[21:22] <helix84> i can volunteer with regression testing if someone (wink wink
@ mdiggory) makes a branch
[21:22] <mdiggory> I love it, basically the java community sets the standard
for how LGPL will be tolerated/treated... not Richard Stallman
[21:24] <PeterDietz> my sidenote, is that I was thinking to myself if theres
any merit to considering a DSpace Google Web Toolkit UI, i.e. gwtUI... as I was
banging my head against the wall as how to create html in DSpace-Xmlui-api
[21:24] <PeterDietz> from my limited experience gwt is better / more robust
than wing
[21:25] <helix84> PeterDietz: does that have any relation to
http://publishinggeekly.com/wp-content/uploads/2011/06/sxedit/sxedit.html ?
[21:25] <kompewter> [ Saxon CE / Aloha Editor ] -
http://publishinggeekly.com/wp-content/uploads/2011/06/sxedit/sxedit.html
[21:27] <mdiggory> peter, what did you want to generate for html?
[21:28] <mdiggory> if I could go back and start over again, Wing would have
produced xhtml with "DRI attributes" flagging the merge points
[21:29] <mdiggory> borrowing from html5 to support "navigation", "footer" and
"content" sections
[21:30] <PeterDietz> I just reconsidered, and I think its just a lack of clear
Model-View-Controller, so I've had to pollute my controller with too much view
logic
[21:30] <robint> Sounds like there is general consensus about moving to XSLT
2.0 being a good thing
[21:30] <mdiggory> it would have been open ended allowing nesting of any types
of elements, without factory methods.
[21:31] <hpottinger> if someone writes the patch, I'll offer to test
> support XSLT 2.0 in XMLUI
> -------------------------
>
> Key: DS-995
> URL: https://jira.duraspace.org/browse/DS-995
> Project: DSpace
> Issue Type: Improvement
> Components: XMLUI
> Affects Versions: 1.8.0, 3.0
> Reporter: Ivan Masár
> Labels: cocoon, xslt
>
> This issue is to track work needed to make XMLUI support XSL 2.0 (using
> Saxon).
> Details why it was created are here:
> http://dspace.2283337.n4.nabble.com/Why-does-DSpace-use-XSLT-1-0-td3750179.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
