EXSLT license and license convention (Was: docv12txt.xsl)

[David Crossley <cr...@apache.org>]

Ross Gardler wrote:
> Ross Gardler wrote:
> 
> > So, currently the code is regarded as public domain. What does this mean 
> > with regards to commiting it to Forrest? - one day I'll understand all 
> > this legal stuff (yeah right!)

We are all in the same boat, but we have help in other
ASF forums whenever we need it.

> A little more digging in their archives turned up the following mail, 
> which was posted in June 2004, in response to my mail of January 2004. 
> Anyway, I think it contains our answer:

Good discovery Ross. All you need to do is create a file in
our /legal/ directory following the naming conventions [*]
add their jar and go. Since they also ask for attribution
you would add them to NOTICE.txt

[*] naming convention for license files

If the supporting product is bundled as a jar file, and provides
a separate license file, then add that file with same jar name
and the .txt extension.

Otherwise use your judgement as to the appropriate filename
and the contents of that license file. Some examples in this
category are the w3c-dtd and oreilly. This latter seems to cover
a specific case and also broadly all O'Reilly code examples
(together with attribution for each case).

-- 
David Crossley

Re: adding EXSLT capabilities

[David Crossley <cr...@apache.org>]

Ross Gardler wrote:
> David Crossley wrote:
> > The next issue with using the EXSLT is how to
> > distribute it within Forrest and how to manage it
> > and keep our version up-to-date.
> > 
> > Should we store the total distribution (all-exslt.zip)
> > as lib/core/exslt-${UTCtimestamp}.zip for example,
> > and then have the forrest build system unpack it into
> > the core stylesheets area.
> 
> For the document2text I just need a single function within one of the 
> packages. However, there are some very useful functions in there.
> 
> The all-exslt.zip is 1.1Mb in size so this seems like overkill. The 
> str.zip is just 85Kb. Based on this I would suggest it would be best to 
> just include the str.zip at this stage and we remember that the other 
> facillities are there when we hit particular problems.
> 
> Comments?

We could add them as needed then. Still, it was the management
method and naming convention that i was looking for:
lib/core/exslt-str-${UTCtimestamp}.zip and unpack on build.
Would that work?

-- 
David Crossley

Re: adding EXSLT capabilities

[Ross Gardler <rg...@apache.org>]

David Crossley wrote:
> The next issue with using the EXSLT is how to
> distribute it within Forrest and how to manage it
> and keep our version up-to-date.
> 
> Should we store the total distribution (all-exslt.zip)
> as lib/core/exslt-${UTCtimestamp}.zip for example,
> and then have the forrest build system unpack it into
> the core stylesheets area.
> 

For the document2text I just need a single function within one of the 
packages. However, there are some very useful functions in there.

The all-exslt.zip is 1.1Mb in size so this seems like overkill. The 
str.zip is just 85Kb. Based on this I would suggest it would be best to 
just include the str.zip at this stage and we remember that the other 
facillities are there when we hit particular problems.

Comments?

Ross

adding EXSLT capabilities

[David Crossley <cr...@apache.org>]

The next issue with using the EXSLT is how to
distribute it within Forrest and how to manage it
and keep our version up-to-date.

Should we store the total distribution (all-exslt.zip)
as lib/core/exslt-${UTCtimestamp}.zip for example,
and then have the forrest build system unpack it into
the core stylesheets area.

-- 
David Crossley