Re: [sca-j] FW: Copyright and license headers

[Simon Nash <oasis@cjnash.com>]

Mark Combellack wrote:
> Hi,
> 
>  
> 
> The Chairs had an action item (2009-02-13-02) to determine how the files 
> for JAVA-121 should be licensed. I asked Mary for some advice on this 
> subject and her reply can be seen below.
> 
>  
> 
>  From this reply, it is clear that we need to add the OASIS copyright 
> and header to each file.
> 
This text is already there in the files we have created so far,
so no change should be needed to those files.

   Simon
>  
> 
> Thanks,
> 
>  
> 
> Mark
> 
> Mark Combellack| Software Developer| Avaya | Eastern Business Park | St. 
> Mellons | Cardiff | CF3 5EA | Voice: +44 (0) 29 2081 7624 | 
> mcombellack@avaya.com <mailto:|mcombellack@avaya.com>
> 
> ------------------------------------------------------------------------
> 
> *From:* Mary McRae [mailto:marypmcrae@gmail.com] *On Behalf Of *Mary McRae
> *Sent:* 12 March 2009 15:34
> *To:* Mark Combellack
> *Cc:* 'David Booz'
> *Subject:* RE: Copyright and license headers
> 
>  
> 
> Hi Mark,
> 
>  
> 
>   A quick answer is that what the SCA-Assemby and SCA-C TCs are using is 
> fine; if you prefer you can copy the full ‘notices’ section from the 
> spec template into your files. You could also provide links to the noted 
> policies (trademark and IPR)
> 
>  
> 
> No, you may not use any other license or change the terms in any way.
> 
>  
> 
> Regards,
> 
>  
> 
> Mary
> 
>  
> 
> *From:* Mark Combellack [mailto:mcombellack@avaya.com]
> *Sent:* Thursday, March 12, 2009 11:20 AM
> *To:* Mary McRae
> *Cc:* David Booz
> *Subject:* Copyright and license headers
> 
>  
> 
> Hi Mary,
> 
>  
> 
> I have been given an action item as co-chair of the SCA-J TC to find out 
> how we should license our files that we are about to add to the OASIS 
> SVN repository. As part of our discussions, the question was asked of 
> what copyright and license headers should we put on the files?
> 
>  
> 
> I have had a quick skim over the OASIS Policies and Procedures but I 
> failed to find anything relevant. Perhaps I have missed something.
> 
>  
> 
> I notice that the SCA-Assembly [2] and SCA-C [3] TCs are using the 
> following license text in their files:
> 
>  
> 
> Copyright(C) OASIS(R) 2005,2009. All Rights Reserved.
> 
> OASIS trademark, IPR and other policies apply.
> 
>  
> 
>  
> 
> The original OSOA license [1] from which the OASIS work was based was 
> very liberal so I am presuming that we would want a similar licensing 
> scheme that allowed the SCA-J files to be used by as many projects as 
> possible.
> 
>  
> 
>  
> 
> I was after some advice as to what copyright and license we can use. My 
> questions include:
> 
>  
> 
>     * Is there a standard OASIS header that should be added? Is it the
>       one used by the SCA-Assembly and SCA-C TCs
>     * Can the TC choose its own licensing terms?
>     * Can we dual license the files – e.g. under some OASIS licence and
>       the Apache licence
> 
>  
> 
> Thanks for you help,
> 
>  
> 
> Mark
> 
>  
> 
> [1] http://www.osoa.org/xmlns/sca/1.0/license.txt
> 
> [2] 
> http://tools.oasis-open.org/version-control/browse/wsvn/sca-assembly/SCA_XSDS/Policy_Intents_Definitions.xml?sc=1
> 
> [3] 
> http://tools.oasis-open.org/version-control/browse/wsvn/sca-c-cpp/SCA_CPP_HEADERS/oasis/sca/ComponentContext.h?rev=9&sc=1 
> <http://tools.oasis-open.org/version-control/browse/wsvn/sca-c-cpp/SCA_CPP_HEADERS/oasis/sca/ComponentContext.h?rev=9&sc=1>
> 
> Mark Combellack| Software Developer| Avaya | Eastern Business Park | St. 
> Mellons | Cardiff | CF3 5EA | Voice: +44 (0) 29 2081 7624 | 
> mcombellack@avaya.com <mailto:|mcombellack@avaya.com>
> 
>  
>