[jira] Created: (FOR-1176) enable plugins to utilise stylesheets from exslt.org

enable plugins to utilise stylesheets from exslt.org
----------------------------------------------------

                 Key: FOR-1176
                 URL: https://issues.apache.org/jira/browse/FOR-1176
             Project: Forrest
          Issue Type: New Feature
          Components: Core operations, Plugin: input.baetle, Plugins (general issues)
    Affects Versions: 0.9-dev
            Reporter: David Crossley
            Priority: Blocker
             Fix For: 0.9-dev


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

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/FOR-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736444#action_12736444 ]

David Crossley commented on FOR-1176:
-------------------------------------

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.

> enable plugins to utilise stylesheets from exslt.org
> ----------------------------------------------------
>
>                 Key: FOR-1176
>                 URL: https://issues.apache.org/jira/browse/FOR-1176
>             Project: Forrest
>          Issue Type: New Feature
>          Components: Core operations, Plugin: input.baetle, Plugins (general issues)
>    Affects Versions: 0.9-dev
>            Reporter: David Crossley
>            Priority: Blocker
>             Fix For: 0.9-dev
>
>
> Various plugins (e.g. "input.baetle") want to use selected stylesheets from exslt.org

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/FOR-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736451#action_12736451 ]

David Crossley commented on FOR-1176:
-------------------------------------

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.

> enable plugins to utilise stylesheets from exslt.org
> ----------------------------------------------------
>
>                 Key: FOR-1176
>                 URL: https://issues.apache.org/jira/browse/FOR-1176
>             Project: Forrest
>          Issue Type: New Feature
>          Components: Core operations, Plugin: input.baetle, Plugins (general issues)
>    Affects Versions: 0.9-dev
>            Reporter: David Crossley
>            Priority: Blocker
>             Fix For: 0.9-dev
>
>
> Various plugins (e.g. "input.baetle") want to use selected stylesheets from exslt.org

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/FOR-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736453#action_12736453 ]

David Crossley commented on FOR-1176:
-------------------------------------

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)
...
"

> enable plugins to utilise stylesheets from exslt.org
> ----------------------------------------------------
>
>                 Key: FOR-1176
>                 URL: https://issues.apache.org/jira/browse/FOR-1176
>             Project: Forrest
>          Issue Type: New Feature
>          Components: Core operations, Plugin: input.baetle, Plugins (general issues)
>    Affects Versions: 0.9-dev
>            Reporter: David Crossley
>            Priority: Blocker
>             Fix For: 0.9-dev
>
>
> Various plugins (e.g. "input.baetle") want to use selected stylesheets from exslt.org

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/FOR-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744451#action_12744451 ]

Sjur N. Moshagen commented on FOR-1176:
---------------------------------------

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>

> enable plugins to utilise stylesheets from exslt.org
> ----------------------------------------------------
>
>                 Key: FOR-1176
>                 URL: https://issues.apache.org/jira/browse/FOR-1176
>             Project: Forrest
>          Issue Type: New Feature
>          Components: Core operations, Plugin: input.baetle, Plugins (general issues)
>    Affects Versions: 0.9-dev
>            Reporter: David Crossley
>            Priority: Blocker
>             Fix For: 0.9-dev
>
>
> Various plugins (e.g. "input.baetle") want to use selected stylesheets from exslt.org

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Thorsten Scherler]

On Tue, 2009-08-18 at 03:42 -0700, Sjur N. Moshagen (JIRA) wrote:

> [ https://issues.apache.org/jira/browse/FOR-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744451#action_12744451 ]
>
> Sjur N. Moshagen commented on FOR-1176:
> ---------------------------------------
>
> 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" />

the way you call it is not correct. the above should read <xsl:import
href="lm:/exslt-extensions/date.add.template.xsl" />

Since input modules are not available in xsl.

salu2

>
> ...
> </xsl:stylesheet>
>
> > enable plugins to utilise stylesheets from exslt.org
> > ----------------------------------------------------
> >
> >                 Key: FOR-1176
> >                 URL: https://issues.apache.org/jira/browse/FOR-1176
> >             Project: Forrest
> >          Issue Type: New Feature
> >          Components: Core operations, Plugin: input.baetle, Plugins (general issues)
> >    Affects Versions: 0.9-dev
> >            Reporter: David Crossley
> >            Priority: Blocker
> >             Fix For: 0.9-dev
> >
> >
> > Various plugins (e.g. "input.baetle") want to use selected stylesheets from exslt.org
>

--
Thorsten Scherler <thorsten.at.apache.org>
Open Source <consulting, training and solutions>

[Sjur Moshagen]

Den 18. aug. 2009 kl. 16.24 skrev Thorsten Scherler:

> On Tue, 2009-08-18 at 03:42 -0700, Sjur N. Moshagen (JIRA) wrote:
>>  <xsl:import href="{lm:exslt-extensions}/date.add.template.xsl" />
>
> the way you call it is not correct. the above should read <xsl:import
> href="lm:/exslt-extensions/date.add.template.xsl" />
>
> Since input modules are not available in xsl.

Thanks for the clarification. That answers my question.

Best regards,
Sjur

[Sjur Moshagen]

Den 18. aug. 2009 kl. 17.07 skrev Sjur Moshagen:

> Den 18. aug. 2009 kl. 16.24 skrev Thorsten Scherler:
>
>> On Tue, 2009-08-18 at 03:42 -0700, Sjur N. Moshagen (JIRA) wrote:
>>> <xsl:import href="{lm:exslt-extensions}/date.add.template.xsl" />
>>
>> the way you call it is not correct. the above should read <xsl:import
>> href="lm:/exslt-extensions/date.add.template.xsl" />
>>
>> Since input modules are not available in xsl.
>
> Thanks for the clarification. That answers my question.

Not fully, now that I have tested it. Here is what I get as response  
from Forrest with the lm:/... style import:

Internal Server Error
Message: null
...
cause
unknown protocol: lm

Any idea on how to make the protocol 'known' to the xsl processor in  
Cocoon?

Best regards,
Sjur

[Sina K. Heshmati]

"Sjur Moshagen" <sjurnm@...> said:

> Den 18. aug. 2009 kl. 17.07 skrev Sjur Moshagen:
>
>> Den 18. aug. 2009 kl. 16.24 skrev Thorsten Scherler:
>>
>>> On Tue, 2009-08-18 at 03:42 -0700, Sjur N. Moshagen (JIRA) wrote:
>>>> <xsl:import href="{lm:exslt-extensions}/date.add.template.xsl" />
>>>
>>> the way you call it is not correct. the above should read <xsl:import
>>> href="lm:/exslt-extensions/date.add.template.xsl" />
>>>
>>> Since input modules are not available in xsl.
>>
>> Thanks for the clarification. That answers my question.
>
> Not fully, now that I have tested it. Here is what I get as response
> from Forrest with the lm:/... style import:
>
> Internal Server Error
> Message: null
> ...
> cause
> unknown protocol: lm
>
> Any idea on how to make the protocol 'known' to the xsl processor in
> Cocoon?

As far as such references are concerned in XSLT stylesheets, how about using fully qualified URLs and resolve those URLs using XML Catalogs. *At least* two reasons why this is worth considering:

(1) Results in more natural XSLT stylesheets for those reading --debugging-- the stylesheet. No-one knows what the lm: is but almost everyone knows HTTP.

(2) Most XSLT stylesheets are likely to be used in alternate environments where locationmap is not necessarily present.

Sina

[Brian M Dube-2]

On Wed, Aug 19, 2009 at 08:45:36AM +0300, Sjur Moshagen wrote:

> Den 18. aug. 2009 kl. 17.07 skrev Sjur Moshagen:
>
> >Den 18. aug. 2009 kl. 16.24 skrev Thorsten Scherler:
> >
> >>On Tue, 2009-08-18 at 03:42 -0700, Sjur N. Moshagen (JIRA) wrote:
> >>><xsl:import href="{lm:exslt-extensions}/date.add.template.xsl" />
> >>
> >>the way you call it is not correct. the above should read <xsl:import
> >>href="lm:/exslt-extensions/date.add.template.xsl" />
> >>
> >>Since input modules are not available in xsl.
> >
> >Thanks for the clarification. That answers my question.
>
> Not fully, now that I have tested it. Here is what I get as response
> from Forrest with the lm:/... style import:
>
> Internal Server Error
> Message: null
> ...
> cause
> unknown protocol: lm
>
> Any idea on how to make the protocol 'known' to the xsl processor in
> Cocoon?

I've been down this path once before. There is a Jira issue
(somewhere; sorry, I'm just on the way to sleep) about rewriting the
imports. I never had success with it. I'll look for that issue and any
notes I may have.

Brian

> Best regards,
> Sjur
>

[Sjur Moshagen]

Den 19. aug. 2009 kl. 09.00 skrev Sina Khakbaz Heshmati:

> "Sjur Moshagen" <sjurnm@...> said:
>
>> Den 18. aug. 2009 kl. 17.07 skrev Sjur Moshagen:
>>
>>> Den 18. aug. 2009 kl. 16.24 skrev Thorsten Scherler:
>>>
>>>> the way you call it is not correct. the above should read  
>>>> <xsl:import
>>>> href="lm:/exslt-extensions/date.add.template.xsl" />
>>
>> Internal Server Error
>> Message: null
>> ...
>> cause
>> unknown protocol: lm
>>
>> Any idea on how to make the protocol 'known' to the xsl processor in
>> Cocoon?
>
> As far as such references are concerned in XSLT stylesheets, how  
> about using fully qualified URLs and resolve those URLs using XML  
> Catalogs. *At least* two reasons why this is worth considering:
>
> (1) Results in more natural XSLT stylesheets for those reading --
> debugging-- the stylesheet. No-one knows what the lm: is but almost  
> everyone knows HTTP.
>
> (2) Most XSLT stylesheets are likely to be used in alternate  
> environments where locationmap is not necessarily present.

This is not about using stylesheets, only about finding a way to look  
up a file that both is understandable by the xslt processor (from  
Cocoon, on which Forrest is built) and fits reasonably well within the  
existing forrest infrastructure.

Best regards,
Sjur

[Sjur Moshagen]

Den 19. aug. 2009 kl. 09.23 skrev Brian M Dube:

>> Any idea on how to make the protocol 'known' to the xsl processor in
>> Cocoon?
>
> I've been down this path once before. There is a Jira issue
> (somewhere; sorry, I'm just on the way to sleep) about rewriting the
> imports. I never had success with it. I'll look for that issue and any
> notes I may have.

It is in:

https://issues.apache.org/jira/browse/FOR-1000

But according to:

http://www.mail-archive.com/user@.../msg02743.html 
(Thorsten Scherler)

it should work. I'll continue the investigation.

Best regards,
Sjur

[Sjur Moshagen]

Den 19. aug. 2009 kl. 10.50 skrev Sjur Moshagen:

> Den 19. aug. 2009 kl. 09.23 skrev Brian M Dube:
>
>>> Any idea on how to make the protocol 'known' to the xsl processor in
>>> Cocoon?
>>
>> I've been down this path once before. There is a Jira issue
>> (somewhere; sorry, I'm just on the way to sleep) about rewriting the
>> imports. I never had success with it. I'll look for that issue and  
>> any
>> notes I may have.
>
> It is in:
>
> https://issues.apache.org/jira/browse/FOR-1000
>
> But according to:
>
> http://www.mail-archive.com/user@.../msg02743.html 
> (Thorsten Scherler)
>
> it should work. I'll continue the investigation.

It seems to be used in dispatcher, in at least the following file:

whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/
resources/stylesheets/helper/variable.helper.xsl:

<xsl:stylesheet version="1.0"
   xmlns:forrest="http://apache.org/forrest/properties/1.0"
   xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
   <xsl:import href="lm://transform.xml.dotdots"/>
   <xsl:import href="lm://transform.xml.pathutils"/>
...

The dotdots LM string matches in one of the main locationmaps, and  
should resolve just fine. That is, when using dispatcher, using an lm:  
protocol in an xsl import seems to work just fine.

The question is then: why doesn't it work in all other cases?

Best regards,
Sjur

[Thorsten Scherler]

On Wed, 2009-08-19 at 14:32 +0300, Sjur Moshagen wrote:

> Den 19. aug. 2009 kl. 10.50 skrev Sjur Moshagen:
>
> > Den 19. aug. 2009 kl. 09.23 skrev Brian M Dube:
> >
> >>> Any idea on how to make the protocol 'known' to the xsl processor in
> >>> Cocoon?
> >>
> >> I've been down this path once before. There is a Jira issue
> >> (somewhere; sorry, I'm just on the way to sleep) about rewriting the
> >> imports. I never had success with it. I'll look for that issue and  
> >> any
> >> notes I may have.
> >
> > It is in:
> >
> > https://issues.apache.org/jira/browse/FOR-1000
> >
> > But according to:
> >
> > http://www.mail-archive.com/user@.../msg02743.html 
> > (Thorsten Scherler)
> >
> > it should work. I'll continue the investigation.
>
> It seems to be used in dispatcher, in at least the following file:
>
> whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/
> resources/stylesheets/helper/variable.helper.xsl:
>
> <xsl:stylesheet version="1.0"
>    xmlns:forrest="http://apache.org/forrest/properties/1.0"
>    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
>    <xsl:import href="lm://transform.xml.dotdots"/>
>    <xsl:import href="lm://transform.xml.pathutils"/>
> ...
>
> The dotdots LM string matches in one of the main locationmaps, and  
> should resolve just fine. That is, when using dispatcher, using an lm:  
> protocol in an xsl import seems to work just fine.
>
> The question is then: why doesn't it work in all other cases?

It should work fine everywhere. Make sure the resources are exposed via
the locationmap.

salu2

>
> Best regards,
> Sjur
>
--
Thorsten Scherler <thorsten.at.apache.org>
Open Source <consulting, training and solutions>

[Thorsten Scherler]

On Wed, 2009-08-19 at 10:50 +0300, Sjur Moshagen wrote:

> Den 19. aug. 2009 kl. 09.23 skrev Brian M Dube:
>
> >> Any idea on how to make the protocol 'known' to the xsl processor in
> >> Cocoon?
> >
> > I've been down this path once before. There is a Jira issue
> > (somewhere; sorry, I'm just on the way to sleep) about rewriting the
> > imports. I never had success with it. I'll look for that issue and any
> > notes I may have.
>
> It is in:
>
> https://issues.apache.org/jira/browse/FOR-1000
>
> But according to:
>
> http://www.mail-archive.com/user@.../msg02743.html 
> (Thorsten Scherler)
>
> it should work. I'll continue the investigation.

The puppy is in the xconf file:
Source Factories section:
<component-instance
class="org.apache.forrest.locationmap.source.impl.LocationmapSourceFactory" name="lm"/>

so that SHOULD be enough.

I am ATM working at a client so cannot really look into it but I may
find a spare minute to have a look.

salu2

>
> Best regards,
> Sjur
>
--
Thorsten Scherler <thorsten.at.apache.org>
Open Source <consulting, training and solutions>

[David Crossley]

Thorsten Scherler wrote:
>
> It should work fine everywhere. Make sure the resources are exposed via
> the locationmap.

So Sjur, you would have an entry in main/webapp/locationmap-transforms.xml

Thanks for following through on this facility.
Should be very powerful.

-David

[David Crossley]

Sjur Moshagen wrote:
> skrev Sina Khakbaz Heshmati:
> >
> >As far as such references are concerned in XSLT stylesheets, how  
> >about using fully qualified URLs and resolve those URLs using XML  
> >Catalogs.

That should work. Have you tried?

It would be good to show an example of that technique in the
sample site.

> > *At least* two reasons why this is worth considering:
> >
> >(1) Results in more natural XSLT stylesheets for those reading --
> >debugging-- the stylesheet. No-one knows what the lm: is but almost  
> >everyone knows HTTP.

And many people are confused by XML Catalogs too.

The location map is fantastic once one gets to grips
with it. But yes, agreed that it is hard to debug and
to follow.

> >(2) Most XSLT stylesheets are likely to be used in alternate  
> >environments where locationmap is not necessarily present.

Yes, but this lm technique can be used on Forrest-specific
stylesheet imports.

> This is not about using stylesheets, only about finding a way to look  
> up a file that both is understandable by the xslt processor (from  
> Cocoon, on which Forrest is built) and fits reasonably well within the  
> existing forrest infrastructure.

Stylesheets will have references to be resolved.
Both techniques should work.

I am hoping that once the first stylesheet is located
then any other imports with local hrefs will be found.

-David

[Sjur Moshagen]

Den 19. aug. 2009 kl. 17.15 skrev David Crossley:

> Thorsten Scherler wrote:
>>
>> It should work fine everywhere. Make sure the resources are exposed  
>> via
>> the locationmap.
>
> So Sjur, you would have an entry in main/webapp/locationmap-
> transforms.xml

Yes. This is what I have added:

<!-- ================================== -->
<!-- exslt transforms                   -->
<!-- ================================== -->
     <match pattern="exslt-transforms/*">
       <location src="{forrest:forrest.stylesheets}/exslt/{1}"/>
     </match>

Do I need a double star ** to capture also subdirs, ie following the  
original suggestion on using the subdir organisation of exslt.org?

Best regards,
Sjur

[Sjur Moshagen]

Den 19. aug. 2009 kl. 16.04 skrev Thorsten Scherler:

> On Wed, 2009-08-19 at 10:50 +0300, Sjur Moshagen wrote:
>> Den 19. aug. 2009 kl. 09.23 skrev Brian M Dube:
>>
>>>> Any idea on how to make the protocol 'known' to the xsl processor  
>>>> in
>>>> Cocoon?
>>>
>>> I've been down this path once before. There is a Jira issue
>>> (somewhere; sorry, I'm just on the way to sleep) about rewriting the
>>> imports. I never had success with it. I'll look for that issue and  
>>> any
>>> notes I may have.
>>
>> It is in:
>>
>> https://issues.apache.org/jira/browse/FOR-1000
>>
>> But according to:
>>
>> http://www.mail-archive.com/user@.../msg02743.html
>> (Thorsten Scherler)
>>
>> it should work. I'll continue the investigation.
>
> The puppy is in the xconf file:
> Source Factories section:
> <component-instance
> class
> =
> "org
> .apache.forrest.locationmap.source.impl.LocationmapSourceFactory"  
> name="lm"/>
>
> so that SHOULD be enough.

It is defined exactly like that in

main/webapp/WEB-INF/cocoon.xconf

It is *not* defined in any of the cli.xconf files, nor in any other  
xconf files.

But since it is working fine in dispatcher, the xconf file has to be  
ok. The problem has to be elsewhere.

Best regards,
Sjur

    [ https://issues.apache.org/jira/browse/FOR-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751057#action_12751057 ]

Sjur N. Moshagen commented on FOR-1176:
---------------------------------------

David, where did you intend that exslt-license.txt should be added? In the exslt directory? To $FORREST_HOME?

> enable plugins to utilise stylesheets from exslt.org
> ----------------------------------------------------
>
>                 Key: FOR-1176
>                 URL: https://issues.apache.org/jira/browse/FOR-1176
>             Project: Forrest
>          Issue Type: New Feature
>          Components: Core operations, Plugin: input.baetle, Plugins (general issues)
>    Affects Versions: 0.9-dev
>            Reporter: David Crossley
>            Priority: Blocker
>             Fix For: 0.9-dev
>
>
> Various plugins (e.g. "input.baetle") want to use selected stylesheets from exslt.org

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.