[
https://issues.apache.org/jira/browse/ODFTOOLKIT-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183454#comment-15183454
]
Svante Schubert commented on ODFTOOLKIT-419:
--------------------------------------------
A small update:
The ball is being played into OASIS field:
https://lists.oasis-open.org/archives/office/201603/msg00002.html
In addition I took a look into POI OOXML schema deployment, but there is still
some uncertainty how they have created the schema bundle. Of course the schema
is not in their source repository, the responsible pom.xml seems to be the
following:
https://apache.googlesource.com/poi/+/REL_3_11_BRANCH/sonar/ooxml-schema/pom.xml
As soon I know that OASIS will not be able to push the schema to Maven for
themselves, I will ask the POI people how they manage the deployment.
Kind regards
Svante
> OASIS-licensed schema files not compatible with ASF policy
> ----------------------------------------------------------
>
> Key: ODFTOOLKIT-419
> URL: https://issues.apache.org/jira/browse/ODFTOOLKIT-419
> Project: ODF Toolkit
> Issue Type: Bug
> Components: generator, validator
> Reporter: Stian Soiland-Reyes
> Priority: Critical
> Labels: licensing, oasis, schema
>
> odfdom includes OASIS-licensed schemas in
> https://github.com/apache/odftoolkit/tree/trunk/validator/src/main/resources/schema/odf1.2
> (and siblings)
> Their copyright (but not their license) is declared in
> https://github.com/apache/odftoolkit/blob/trunk/NOTICE#L11
> These files have an OASIS license, which include a BSD-like permissive
> license:
> {quote}
> This document and translations of it may be copied and furnished to
> others, and
> derivative works that comment on or otherwise explain it or assist in
> its
> implementation may be prepared, copied, published, and distributed, in
> whole or
> in part, without restriction of any kind, provided that the above
> copyright
> notice and this section are included on all such copies and derivative
> works.
> {quote}
> but also a no-modification clause:
> {quote}
> However, this document itself may not be modified in any way, including by
> removing the copyright notice or references to OASIS, except as needed
> for the
> purpose of developing any document or deliverable produced by an OASIS
> Technical Committee (in which case the rules applicable to copyrights,
> as set
> forth in the OASIS IPR Policy, must be followed) or as required to
> translate it
> into languages other than English.
> {quote}
> As also discussed in LEGAL-111 and TAVERNA-925 the ASF policy is to NOT
> include source code that can't be modified:
> http://www.apache.org/legal/resolved.html#no-modification
> and so I believe the OASIS schema files can't be part of ASF source code
> releases of odfdom -- policy-wise, not legally. (We are legally OK as the
> files have not been modified).
> I am not sure about the license of 1.1 and 1.0 schemas as they don't have
> their license stated in their headers:
> https://github.com/apache/odftoolkit/blob/trunk/validator/src/main/resources/schema/odf1.1/OpenDocument-schema-v1.1.rng
> but their license on
> http://docs.oasis-open.org/office/v1.1/OS/OpenDocument-v1.1-html/OpenDocument-v1.1.html
> also includes:
> {quote}
> However, this document itself may not be modified in any way (..)
> {quote}
> One workaround would be to include by URL during the build - e.g. from
> http://docs.oasis-open.org/office/v1.2/os/
> http://docs.oasis-open.org/office/v1.1/OS/
> (but no v1.0 version of just the schemas)
> -- of course this means dependency on the docs.oasis-open.org server
> remaining available..
> (The schema files are also present under
> https://github.com/apache/odftoolkit/tree/trunk/generator/schema2template/src/main/resources/examples/odf/odf-schemas
> )
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
