[ 
https://issues.apache.org/jira/browse/TAVERNA-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182397#comment-15182397
 ] 

Stian Soiland-Reyes commented on TAVERNA-927:
---------------------------------------------

h2. w3c licenses

Agree that from LEGAL-111 the [W3C Document 
License|https://www.w3.org/Consortium/Legal/2015/doc-license] is not acceptable 
in source form, as, similar to the OASIS schema files we identified in 
TAVERNA-925 - as it comes with a non-modification clause. 
http://www.apache.org/legal/resolved.html#no-modification

It should be valid in binary form - but of course for ontologies there is no 
"binary form".  While downloading from the original URLs are possible during 
build, experience has shown that this typically causes build timeouts as you 
rely on an increasing number of third-party hosted systems. While w3.org would 
presumably remain up for the foreseeable future, they are also known to apply 
tarpits for often requested schemas and ontologies - requesting down-stream 
parties to include those in their source trees instead. 

In the related ODFTOOLKIT-419 we discussed the possibility of making Maven 
artifacts that contain such schemas and deploy them to Maven Central. In that 
way it would be mirrored and accessible. Tis could in theory be the kind of 
thing that [Apache Extras|apache-extras.org] could have done - but since the 
closure of Google code this is fairly read-only now.. for Taverna we could do 
something similar under our related http://github.com/taverna-extras/ - I'm not 
sure what group Id to use, but I guess something silly like 
io.github.tavernaextras ?

Note that the [W3C Software 
License|https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document]
 is category A and [is 
OK|http://www.apache.org/legal/resolved.html#category-a], so 
./taverna-robundle/src/main/xsd/xmldsig-core-schema.xsd is in the clear.

http://www.w3.org/TR/xmlenc-core/xenc-schema.xsd is unclear, as it does not 
have any headers - however https://www.w3.org/TR/xmlenc-core/ says 

{quote}
Copyright © 2002 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, 
trademark, document use and software licensing rules apply.
{quote}

.. where *software licensing* links to the software license.  It is unclear if 
the xsd counts as a document or software.


It might be worth checking with the W3C folks what is the license of these 
ontologies and schemas - as it would appear that the intention from w3c is for 
"code components" to be licensed under the permissive W3C Software License - as 
https://www.w3.org/Consortium/Legal/2015/doc-license says:

{quote}
In addition, "Code Components" —Web IDL in sections clearly marked as Web IDL; 
and W3C-defined markup (HTML, CSS, etc.) and computer programming language code 
clearly marked as code examples— are licensed under the W3C Software License.
{quote}



> Review Category B licenses in taverna-language
> ----------------------------------------------
>
>                 Key: TAVERNA-927
>                 URL: https://issues.apache.org/jira/browse/TAVERNA-927
>             Project: Apache Taverna
>          Issue Type: Task
>          Components: Taverna Language
>    Affects Versions: language 0.15.1
>            Reporter: Stian Soiland-Reyes
>            Priority: Critical
>             Fix For: language 0.16.0
>
>
> As [raised by Justin 
> Mclean|http://mail-archives.apache.org/mod_mbox/incubator-general/201603.mbox/%3C5C3A916C-245A-4ADF-A890-3B575B3B6C8D%40classsoftware.com%3E]:
> {quote}
> There are some licensing issues:
> - Several items [3][4][5][6] are licensed under W3C document license, this is 
> not a category A license and looks like they can only be included in binary 
> release [2]. (i.e. Category B but it's not listed) You may need to clarify 
> this on legal discuss.
> - Files [8][9][16][17][18][19][20] licensed under CC-BY-3 can only be 
> included in a binary release. [10]
> - I assume CC-A [11][12] would also need to be handled the same way.
> - It is unclear how [13] is licensed.
> - Looks like [14][15] are not licensed under a Category A license. Again 
> probably needs to be discussed on legal discuss.
> The LICENSE and NOTICE in ./taverna-tavlang-tool/src/main/resources/META-INF/ 
> may need updating, looks like the contents don’t match the top level license 
> and year is incorrect.
> 1. 
> apache-taverna-language-0.15.1-incubating/taverna-robundle/src/test/resources/workflowrun.bundle.zip
> 2. https://issues.apache.org/jira/browse/LEGAL-111
> 3. 
> ./taverna-scufl2-schemas/src/main/resources/org/apache/taverna/scufl2/rdfxml/xsd/xml.xsd
> 4. ./taverna-robundle/src/main/resources/ontologies/prov-aq.rdf
> 5. ./taverna-robundle/src/main/resources/ontologies/prov-o.rdf
> 6. ./taverna-robundle/src/main/resources/ontologies/prov-o.rdf
> 7. ./taverna-robundle/src/main/resources/ontologies/dcam.owl
> 8. ./taverna-robundle/src/main/resources/ontologies/dcam.owl
> 9. ./taverna-robundle/src/main/resources/ontologies/dcterms_od.owl
> 10. http://www.apache.org/legal/resolved.html#category-b
> 11. ./taverna-robundle/src/main/resources/ontologies/foaf.rdf
> 12. ./taverna-scufl2-wfdesc/src/main/resources/com/xmlns/foaf/foaf.rdf
> 13. ./taverna-robundle/src/main/xsd/xenc-schema.xsd
> 14. ./taverna-robundle/src/main/resources/ontologies/oa.rdf
> 15. ./taverna-robundle/src/main/resources/ontologies/ro.owl
> 16. 
> ./taverna-scufl2-wfdesc/src/main/resources/org/purl/wf4ever/wfdesc/wfdesc.ttl
> 17. 
> ./taverna-scufl2-wfdesc/src/main/resources/org/purl/wf4ever/wfdesc/wfprov.ttl
> 18. 
> ./taverna-scufl2-wfdesc/src/main/resources/org/purl/wf4ever/wfdesc/roterms.ttl
> 19. 
> ./taverna-scufl2-wfdesc/src/main/resources/org/purl/wf4ever/wfdesc/wf4ever.ttl
> 20 
> ./taverna-scufl2-schemas/src/main/resources/org/apache/taverna/scufl2/rdfxml/xsd/roevo.xsd
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to