Re: Woden4SAWSDL Released

[Jeremy Hughes <hu...@apache.org>]

Hi, it's great that you guys are using Woden for this. Please do let
us know on woden-dev of any requirements you have / bug fixes needed
etc.

I'm curious as to what modifications you needed to make to Woden M7a
in order to get your tests to work - are there bugs in Woden which we
need to fix? Ditto with XmlSchema.

One plea - your distribution Woden4SAWSDL-M1.jar contains built Woden
classes, Woden is licensed under the Apache License 2.0 [1] which has
certain requirements on derivative works in section 4. Please see my
comments in line ...

   1. You must give any other recipients of the Work or Derivative
Works a copy of this License; and

You don't include the license

   2. You must cause any modified files to carry prominent notices
stating that You changed the files; and

you say you have a modified Woden M7a, I haven't diff'd the source
tree, so perhaps you could confirm that the Woden source which you've
modified has these prominent notices

   3. You must retain, in the Source form of any Derivative Works that
You distribute, all copyright, patent, trademark, and attribution
notices from the Source form of the Work, excluding those notices that
do not pertain to any part of the Derivative Works;

your source zip doesn't contain the Woden LICENSE.* or NOTICE files ..
it is important that you do.

 and

   4. If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained within
such NOTICE file, excluding those notices that do not pertain to any
part of the Derivative Works, in at least one of the following places:
within a NOTICE text file distributed as part of the Derivative Works;
within the Source form or documentation, if provided along with the
Derivative Works; or, within a display generated by the Derivative
Works, if and wherever such third-party notices normally appear. The
contents of the NOTICE file are for informational purposes only and do
not modify the License. You may add Your own attribution notices
within Derivative Works that You distribute, alongside or as an
addendum to the NOTICE text from the Work, provided that such
additional attribution notices cannot be construed as modifying the
License.

Please include the NOTICE file in the binary distro.

I'm sorry this sounds a bit heavy. One simple way of keeping to the
above is to not ship Woden classes merged into your own jar. You could
either distribute the Woden jars as distributed on Apache or if you do
need to make modifications, check out Woden source from Apache, make
the mods, use the Woden build process to build it and ship the
resulting zips. Ideally we'd be able to make the fixes you require and
either give you a new release that meets your needs or you could take
a SNAPSHOT jar from us (along with all the caveats that go with
SNAPSHOTS of course).

Many thanks,
Jeremy

[1] http://www.apache.org/licenses/LICENSE-2.0.html

On 22/05/07, Doug Brewer <tw...@uga.edu> wrote:
>
> We are pleased to announce that the Woden4SAWSDL project has released
> milestone 1.
>
> Currently the status is:
>
> Deserialization is complete and passes the SAWSDL test cases with the
> modified version of Woden M7a and a modified WS Commons XmlSchema.
>
> Serialization is still being worked on.
>
> A link to find all unit test case reports, source code, and binaries
> http://lsdis.cs.uga.edu/projects/meteor-s/opensource/woden4sawsdl/
>
> The Woden4SAWSDL Team
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org