>From the cover page of the ODF 1.2 specification:

"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. 
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."

That should take care of copies of the specifications bundled in distributions, 
kept in project repositories etc.

The ODF 1.2 schema files have the same statement in their notices.  

Why is this not sufficient?  

It seems more appropriate to obtain from ASF Legal a determination of the class 
of license this is for the specific purposes that you propose to make of it.  

 - Dennis

-----Original Message-----
From: Svante Schubert [mailto:[email protected]] 
Sent: Wednesday, March 21, 2012 07:28
To: Biao Han
Cc: [email protected]
Subject: Test documents for Signature feature and Maven support for ODF 
artifacts

Hi Devin,

as you had been the lead developer of the ODF signature feature.
Would you be curious enough to test if the new signature documents from
the OpenDocument Interoperability and Conformance OIC TC for signature
work in our implementation?
Please take a look at the bottom of
http://tools.oasis-open.org/version-control/browse/wsvn/oic/Advisories/00008-DSig_Namespaces/trunk/description.html

Those had been mentioned on our today's call.

BTW currently, the ODF TC chair (Rob) is asking permission from OASIS to
redistribute the ODF RelaxNG schema files on a Maven repository, so we
do not have to download them for every build of the ODF toolkit -
requiring Internet access - but once with Maven similar as the OOXML
schema are downloaded via Maven by the Apache POI project.
The next step would be to be able to download the specification for
bundling it within our deployment as documentation and even more
interesting to be able to download sets of test documents via Maven to
be able to reuse them cross-project and keeping our repository lean.

Best,
Svante

Reply via email to