Forrest
  1. Forrest
  2. FOR-1176

enable plugins to utilise stylesheets from exslt.org

    Details

    • Urgency:
      Blocker

      Description

      Various plugins (e.g. "input.baetle") want to use selected stylesheets from exslt.org

        Activity

        Hide
        David Crossley added a comment -
        This topic has arisen before for Forrest. Here is one discussion:

         EXSLT license and license convention (Was: docv12txt.xsl)
         http://thread.gmane.org/gmane.text.xml.forrest.devel/5598/focus=8217

        See earlier in that thread where Ross asked at the EXSLT mail list:
         http://thread.gmane.org/gmane.text.xml.forrest.devel/5598/focus=8216
        Note that the links that Ross provided are broken. This following is close:
         [exslt-manage] License?
         http://lists.fourthought.com/pipermail/exslt-manage/2004-June/000603.html
         
        I have only done basic searching today. It seems like a recurring issue for them.
        Show
        David Crossley added a comment - This topic has arisen before for Forrest. Here is one discussion:  EXSLT license and license convention (Was: docv12txt.xsl)   http://thread.gmane.org/gmane.text.xml.forrest.devel/5598/focus=8217 See earlier in that thread where Ross asked at the EXSLT mail list:   http://thread.gmane.org/gmane.text.xml.forrest.devel/5598/focus=8216 Note that the links that Ross provided are broken. This following is close:  [exslt-manage] License?   http://lists.fourthought.com/pipermail/exslt-manage/2004-June/000603.html   I have only done basic searching today. It seems like a recurring issue for them.
        Hide
        David Crossley added a comment -
        Here is my suggestion for handling this at Forrest:

        mkdir $FORREST_HOME/main/webapp/resources/stylesheets/exslt

        Add a file README.txt to that directory to explain where they came from, and refer to this issue. Also add a note that these stylesheets should not be edited, rather contribute changes to exslt.org and update.

        Add a file exslt-license.txt ... Note that i have not done full research. I think that they suggested "Creative Commons : Attribution" various times in later years, but i have not found any definite statement.

        Add attribution to $FORREST_HOME/NOTICE.txt as specified in the mail above.

        For each stylesheet that we want to use, add it "as-is" to the abovementioned directory, using a sub-directory structure patterned on the directories from all-exslt.zip
        (Note that adding all exslt stylesheets to Forrest is too large.)

        In the various Forrest plugins, use our "locationmap" techniques to refer to the relevant stylesheet.
        Show
        David Crossley added a comment - Here is my suggestion for handling this at Forrest: mkdir $FORREST_HOME/main/webapp/resources/stylesheets/exslt Add a file README.txt to that directory to explain where they came from, and refer to this issue. Also add a note that these stylesheets should not be edited, rather contribute changes to exslt.org and update. Add a file exslt-license.txt ... Note that i have not done full research. I think that they suggested "Creative Commons : Attribution" various times in later years, but i have not found any definite statement. Add attribution to $FORREST_HOME/NOTICE.txt as specified in the mail above. For each stylesheet that we want to use, add it "as-is" to the abovementioned directory, using a sub-directory structure patterned on the directories from all-exslt.zip (Note that adding all exslt stylesheets to Forrest is too large.) In the various Forrest plugins, use our "locationmap" techniques to refer to the relevant stylesheet.
        Hide
        David Crossley added a comment -
        See ...
         ASF Legal Previously Asked Questions
         http://www.apache.org/legal/resolved.html
        "
        Works under the following licenses may be included within Apache products:
        ...
        Creative Commons Attribution (CC-A)
        ...
        "
        Show
        David Crossley added a comment - See ...  ASF Legal Previously Asked Questions   http://www.apache.org/legal/resolved.html " Works under the following licenses may be included within Apache products: ... Creative Commons Attribution (CC-A) ... "
        Hide
        Sjur N. Moshagen added a comment -
        One question: will the locationmap function in xslt import statements? As in:

        <xsl:stylesheet version="1.0"
                        xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                        xmlns:date="http://exslt.org/dates-and-times"
                        extension-element-prefixes="date">

          <xsl:import href="{lm:exslt-extensions}/date.add.template.xsl" />

        ...
        </xsl:stylesheet>
        Show
        Sjur N. Moshagen added a comment - One question: will the locationmap function in xslt import statements? As in: <xsl:stylesheet version="1.0"                 xmlns:xsl=" http://www.w3.org/1999/XSL/Transform "                 xmlns:date=" http://exslt.org/dates-and-times "                 extension-element-prefixes="date">   <xsl:import href="{lm:exslt-extensions}/date.add.template.xsl" /> ... </xsl:stylesheet>
        Hide
        Sjur N. Moshagen added a comment -
        David, where did you intend that exslt-license.txt should be added? In the exslt directory? To $FORREST_HOME?
        Show
        Sjur N. Moshagen added a comment - David, where did you intend that exslt-license.txt should be added? In the exslt directory? To $FORREST_HOME?
        Hide
        David Crossley added a comment -
        Dunno. Maybe at
        lib/core/
        that is where we have other unusual ones such as
        lib/core/w3c-dtd-license.txt

        Please also note the pathname in $FORREST_HOME/LICENSE.txt and it will be dealt with along with the others in due course.
        Show
        David Crossley added a comment - Dunno. Maybe at lib/core/ that is where we have other unusual ones such as lib/core/w3c-dtd-license.txt Please also note the pathname in $FORREST_HOME/LICENSE.txt and it will be dealt with along with the others in due course.
        Hide
        David Crossley added a comment -
        Added license and notice details for EXSLT stylesheets in r814513
        at main/webapp/resources/stylesheets/exslt/
        Show
        David Crossley added a comment - Added license and notice details for EXSLT stylesheets in r814513 at main/webapp/resources/stylesheets/exslt/
        Hide
        David Crossley added a comment -
        This is all done now. Any project or plugin can use the centralised collection of stylesheets.

        * Added a match to main/webapp/locationmap-transforms.xml to handle any exslt stylesheet

        * The locationmap syntax shown above and on the mail list discussion is incorrect. It is instead, for example:
        <xsl:import href="lm://transform-exslt/date/functions/day-name/date.day-name.template.xsl"/>

        * Yes, ordinary relative paths do function correctly for importing other stylesheets from those ones.

        * See EXSLT example and its related stylesheet at 'forrest seed-sample' site.

        * Cleaned up the Baetle plugin to use this system.
        Show
        David Crossley added a comment - This is all done now. Any project or plugin can use the centralised collection of stylesheets. * Added a match to main/webapp/locationmap-transforms.xml to handle any exslt stylesheet * The locationmap syntax shown above and on the mail list discussion is incorrect. It is instead, for example: <xsl:import href=" lm://transform-exslt/date/functions/day-name/date.day-name.template.xsl "/> * Yes, ordinary relative paths do function correctly for importing other stylesheets from those ones. * See EXSLT example and its related stylesheet at 'forrest seed-sample' site. * Cleaned up the Baetle plugin to use this system.

          People

          • Assignee:
            Unassigned
            Reporter:
            David Crossley
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development