snip... >From what i can tell there is NOTHING, ANYWHERE, that says we need to > include the OSOA license header in any of our source files, and it seems > wrong to me to do so. >
You are absolutely right. This was me being over-zealous in adding header information. I can fix that. > > What the OSOA license does say is that we need to include two things: > > 1. A link or URL to the Service Component Architecture Specification at > this location: > http://www.osoa.org/display/Main/Service+Component+Architecture+Specifications > > 2. The full text of the copyright notice as shown in the Service Component > Architecture Specification. > > To date we have been including those two things in artifact top level > LICENSE/NOTICE files and its got through lots of release reviews including > all the ones while in the Incubator with lots of eyes looking so i don't see > why we want to change. > > > > A slightly related point is that the Apache headers we include in each of > our source files are not strictly necessary but are just included for good > measure, the code is covered by the top level LICENSE/NOTICE files in the > released artifact and that is all thats absolutely required. > > It is a bug that the host-webapp module jar LICENSE/NOTICE file weren't > updated for the OSOA license when the taglib was added, IMHO thats all that > needs fixing here. > > > I'm not sure that will satisfy everyone now that this has been blown up so > much though so how about also removing the Apache header from all the spec > derived files and replacing it with the SCA copyright. As i pointed out > above the header isn't really necessary anyway and that way the files would > match the .xsd files we have eg > https://svn.apache.org/repos/asf/tuscany/java/sca/modules/assembly-xsd/src/main/resources/sca-binding-ejb.xsd. > This does seem to go slightly against the ASF policy of having attributions > in the NOTICE file where possible though, see: > http://www.apache.org/legal/src-headers.html > > ...ant > > Sounds OK to me. I will add the copyright from the specs in question and also the link to the web site. Simon
