[
https://issues.apache.org/jira/browse/TAVERNA-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187175#comment-15187175
]
Ian Dunlop edited comment on TAVERNA-925 at 3/9/16 2:49 PM:
------------------------------------------------------------
Do we know of anyone using ODF manifests for RO Bundles? Is it more trouble
than it is worth. How often does the schema change? How much of the schema gets
used by the RO Bundle code. Maybe it is better to just write the code manually.
So much magic going on here!
Has no other Apache project included an OASIS licensed schema before?
was (Author: ianwdunlop):
Do we know of anyone using ODF manifests for RO Bundles? Is it more trouble
than it is worth. How often does the schema change? How much of the schema gets
used by the RO Bundle code. Maybe it is better to just write the code manually.
So much magic going on here!
> Avoid OASIS licensed OpenDocument-v1.2-os-manifest-schema.rng?
> --------------------------------------------------------------
>
> Key: TAVERNA-925
> URL: https://issues.apache.org/jira/browse/TAVERNA-925
> Project: Apache Taverna
> Issue Type: Bug
> Components: Taverna Language
> Affects Versions: language 0.15.1
> Reporter: Stian Soiland-Reyes
> Labels: licensing, ucf
>
> Taverna Language includes the Open Document manifest schema, which has an
> OASIS license
> https://github.com/apache/incubator-taverna-language/blob/master/taverna-robundle/src/main/xsd/OpenDocument-v1.2-os-manifest-schema.rng
> (This is then compiled to JAXB Java beans and used to create/parse the UCF
> META-INF/manifest.xml inside the wfbundle workflow files - see
> target/generated-sources/xjc/org/apache/taverna/robundle/xml/odf/manifest
> after building)
> {quote}
> This product contains Open Document Format(ODF) Schema documents.
> Copyright (c) OASIS Open 2002-2011. All Rights Reserved.
> {quote}
> Our file matches 100% with
> http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-manifest-schema.rng
> OpenDocument-v1.2-os-manifest-schema.xsd is derived directly with trang
> with the same copyright header added.
> (See commit
> https://github.com/apache/incubator-taverna-language/commit/b4c49f6e5c28f5113cacb353eb473e3b5f8bff24
> )
> And so we also added it to our LICENSE as
> https://github.com/apache/incubator-taverna-language/blob/master/LICENSE#L327
> We initially looked at Apache ODFDom which includes this similarly in
> https://svn.apache.org/repos/asf/incubator/odf/trunk/NOTICE
> https://svn.apache.org/repos/asf/incubator/odf/trunk/validator/src/main/resources/schema/odf1.2/OpenDocument-v1.2-os-manifest-schema.rng
> which made it seem like it would be OK for us to distribute.
> but the license includes a trouble-some no-modification clause:
> > However, this document itself may not be modified in any way, including by
> > removing the copyright notice or references to OASIS (..)
> Not being able to remove the copyright notice is OK - but this says no
> modifications to the document AT ALL. So while we haven't done any such
> changes, downloaders of ASF software should:
> http://www.apache.org/legal/resolved.html#no-modification
> > Apache projects must not include material under such licenses in version
> > control or in released source packages. It is however acceptable for a
> > build process to automatically download such non-software materials like
> > fonts and standardized data and include them in the resulting binaries.
> > Such use makes it clear that these dependencies are not a part of the open
> > source code of the project.
> OASIS license was discussed in
> https://issues.apache.org/jira/browse/LEGAL-111
> and concluded as:
> > As I understood it, since the standards do not allow modification, we may
> > include them in binary releases, but not source releases.
> So that should mean that we can't (ASF policy wice) distribute
> OpenDocument-v1.2-os-manifest-schema.rng or
> OpenDocument-v1.2-os-manifest-schema.xsd **in our source code**.
> However we would be fine to refer to those externally during the build - but
> of course this would mean that
> http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-manifest-schema.rng
> would have to be online at build time.
> In commit
> https://github.com/apache/incubator-taverna-language/commit/c27b90e953c01e428ac352649038e17e71d6c705
> I tried to compile the rng directly with jaxb-maven-plugin which I think
> didn't work well.
> It might still be worth checking if this would be possible to do with the rng
> directly from docs.oasis-open.org.
> It would even be possible to share the converted .xsd somewhere outside ASF
> -- a cheaky quick-fix would be
> https://cdn.rawgit.com/wf4ever/robundle/b4c49f6e5c28f5113cacb353eb473e3b5f8bff24/src/main/xsd/OpenDocument-v1.2-os-manifest-schema.xsd
> Or perhaps the best is to remove the OpenDocument.* schema compilation
> all-together and create JAXB Java beans by hand with the appropriate
> annotations? Do not copy from target/generated-sources/xjc/ as that would
> count as derived work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
