You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Jeremy Boynes <jb...@apache.org> on 2007/09/29 19:53:50 UTC
Field of use constraint on OSOA license?
The recent Tuscany distribution contains XSDs licensed under the OSOA
license[1] which contains the following:
"Permission to copy, make derivative works of, and distribute the
Service Component Architecture
JavaDoc, Interface Definition Files and XSD files in any medium
without fee or royalty as part
of a compliant implementation of the Service Component Architecture
Specification is hereby granted."
Is the restriction to a "compliant implementation" a field of use
constraint that Tuscany project should be concerned about?
--
Jeremy
[1] http://www.osoa.org/xmlns/sca/1.0/license.txt
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Field of use constraint on OSOA license?
Posted by Mike Edwards <mi...@gmail.com>.
Folks,
At present, I believe that the OSOA SCA specifications do not contain
any actual conformance statements that would allow anyone to judge
whether an implementation is compliant or not. As a result, this
restriction is somewhat moot.
As a result, I don't consider this restriction of great concern to Tuscany.
The situation is likely to be very different when it comes to the OASIS
versions of the SCA specifications. OASIS requires conformance
statements and the OASIS SCA TCs have charters which not only require
the creation of conformance statements in the specifications but also
require the creation of Test Suites for each of the specs. In this
respect, the OASIS SCA specifications will be closer to the JCP JSR
process, which requires a test suite to be created alongside the
specifications.
Folks who have views on conformance and test suites for SCA are welcome
to submit their ideas to the relevant OASIS SCA TCs.
Yours, Mike.
Jeremy Boynes wrote:
> The recent Tuscany distribution contains XSDs licensed under the OSOA
> license[1] which contains the following:
> "Permission to copy, make derivative works of, and distribute the
> Service Component Architecture
> JavaDoc, Interface Definition Files and XSD files in any medium without
> fee or royalty as part
> of a compliant implementation of the Service Component Architecture
> Specification is hereby granted."
>
> Is the restriction to a "compliant implementation" a field of use
> constraint that Tuscany project should be concerned about?
> --
> Jeremy
>
> [1] http://www.osoa.org/xmlns/sca/1.0/license.txt
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Field of use constraint on OSOA license?
Posted by Roland Weber <os...@dubioso.net>.
Hello Jeremy,
Jeremy Boynes wrote:
> The recent Tuscany distribution contains XSDs licensed under the OSOA
> license[1] which contains the following:
> "Permission to copy, make derivative works of, and distribute the
> Service Component Architecture
> JavaDoc, Interface Definition Files and XSD files in any medium without
> fee or royalty as part
> of a compliant implementation of the Service Component Architecture
> Specification is hereby granted."
>
> Is the restriction to a "compliant implementation" a field of use
> constraint that Tuscany project should be concerned about?
No, AFAICT. Every JSR has the same restriction for compliant
implementations. A Field of Use restriction would be "not in
embedded devices". I'm not sure how this is handled until
you've reached the point where the implementation passes the
testcases to become a compliant implementation. But I've
never heard of problems with that stipulation either.
cheers,
Roland
> [1] http://www.osoa.org/xmlns/sca/1.0/license.txt
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Field of use constraint on OSOA license?
Posted by Mike Edwards <mi...@gmail.com>.
Folks,
Robert Burrell Donkin wrote:
> no performance rights so i guess that we'll have to strike out the
> sing-a-long-a-spec from the next apachecon ;-)
Done to protect the innocent ;-)
Yours, Mike.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Field of use constraint on OSOA license?
Posted by Robert Burrell Donkin <ro...@gmail.com>.
On Jan 7, 2008 9:58 PM, Jeremy Boynes <jb...@apache.org> wrote:
> There is an updated license here:
> http://www.osoa.org/xmlns/sca/1.0/license.txt
>
> and I've attached a copy of the text below. To my layman's
> understanding that seems OK but it would be good to have official
> blessing.
>
> Thanks Janet for getting this through.
no performance rights so i guess that we'll have to strike out the
sing-a-long-a-spec from the next apachecon ;-)
looks good to me: thanks to everyone who sorted this out
might be a good idea raising this on legal discuss so that it can be
included in the third party licensing policy draft
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Field of use constraint on OSOA license?
Posted by Robert Burrell Donkin <rd...@apache.org>.
On Mon, 2008-01-07 at 21:58 +0000, Jeremy Boynes wrote:
> There is an updated license here:
> http://www.osoa.org/xmlns/sca/1.0/license.txt
>
> and I've attached a copy of the text below. To my layman's
> understanding that seems OK but it would be good to have official
> blessing.
looks fine to me. unless i've missed anything, i'd be happy this add to
category A in http://people.apache.org/~rubys/3party.html.
- robert
Re: Field of use constraint on OSOA license?
Posted by Jeremy Boynes <jb...@apache.org>.
There is an updated license here:
http://www.osoa.org/xmlns/sca/1.0/license.txt
and I've attached a copy of the text below. To my layman's
understanding that seems OK but it would be good to have official
blessing.
Thanks Janet for getting this through.
--
Jeremy
On Jan 7, 2008, at 3:56 PM, Janet Campbell wrote:
> Yes, my understanding is that the new version of the license has
> now been
> posted.
>
> Janet Campbell
> Phone: +1.613.224.9461, x.229 (GMT -5)
> Fax: +1.613.224.5172
> janet.campbell@eclipse.org
>
> -----Original Message-----
> From: Oisin Hurley [mailto:ohurley@iona.com]
> Sent: Friday, December 21, 2007 5:36 AM
> To: Janet Campbell
> Cc: general@incubator.apache.org; 'Legal Discuss'
> Subject: Re: Field of use constraint on OSOA license?
>
>
> On 20 Dec 2007, at 20:50, Janet Campbell wrote:
>
>> We have been in touch with the OSOA folks and the license restriction
>> referred to below has now been removed.
>
> Thanks for pushing that through, Janet. Have you secured the new
> license text, and has it been posted on the OSOA site do you know?
>
> best regards
> Oisin
============================================
License for the Service Component Architecture JavaDoc, Interface
Definition files and XSD files.
The Service Component Architecture JavaDoc, Interface Definition files,
and XSD files are being provided by the copyright holders under the
following license. By using and/or copying this work, you agree that
you have read, understood and will comply with the following terms and
conditions:
Permission to copy, display, make derivative works of, and distribute
the Service Component Architecture JavaDoc, Interface Definition Files
and XSD files (the "Artifacts") in any medium without fee or royalty is
hereby granted, provided that you include the following on ALL copies
of the Artifacts, or portions thereof, that you make:
1. A link or URL to the Artifacts at this location:
http://www.osoa.org/display/Main/Service+Component+Architecture
+Specifications
2. The full text of this copyright notice as shown in the Artifacts.
THE ARTIFACTS ARE PROVIDED "AS IS," AND THE AUTHORS MAKE NO
REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, REGARDING THE
ARTIFACTS AND THE IMPLEMENTATION OF THEIR CONTENTS, INCLUDING, BUT NOT
LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, NON-INFRINGEMENT OR TITLE.
THE AUTHORS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL,
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR RELATING TO ANY
USE OR DISTRIBUTION OF THE ARTIFACTS.
The name and trademarks of the Authors may NOT be used in any manner,
including advertising or publicity pertaining to the Service Component
Architecture Specification or its contents without specific, written
prior permission. Title to copyright in the Service Component
Architecture Specification and the JavaDoc, Interface Definition Files
and XSD Files will at all times remain with the Authors.
No other rights are granted by implication, estoppel or otherwise.
Revision level 1.1, last updated on 2007/11/19
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Field of use constraint on OSOA license?
Posted by Jeremy Boynes <jb...@apache.org>.
There is an updated license here:
http://www.osoa.org/xmlns/sca/1.0/license.txt
and I've attached a copy of the text below. To my layman's
understanding that seems OK but it would be good to have official
blessing.
Thanks Janet for getting this through.
--
Jeremy
On Jan 7, 2008, at 3:56 PM, Janet Campbell wrote:
> Yes, my understanding is that the new version of the license has
> now been
> posted.
>
> Janet Campbell
> Phone: +1.613.224.9461, x.229 (GMT -5)
> Fax: +1.613.224.5172
> janet.campbell@eclipse.org
>
> -----Original Message-----
> From: Oisin Hurley [mailto:ohurley@iona.com]
> Sent: Friday, December 21, 2007 5:36 AM
> To: Janet Campbell
> Cc: general@incubator.apache.org; 'Legal Discuss'
> Subject: Re: Field of use constraint on OSOA license?
>
>
> On 20 Dec 2007, at 20:50, Janet Campbell wrote:
>
>> We have been in touch with the OSOA folks and the license restriction
>> referred to below has now been removed.
>
> Thanks for pushing that through, Janet. Have you secured the new
> license text, and has it been posted on the OSOA site do you know?
>
> best regards
> Oisin
============================================
License for the Service Component Architecture JavaDoc, Interface
Definition files and XSD files.
The Service Component Architecture JavaDoc, Interface Definition files,
and XSD files are being provided by the copyright holders under the
following license. By using and/or copying this work, you agree that
you have read, understood and will comply with the following terms and
conditions:
Permission to copy, display, make derivative works of, and distribute
the Service Component Architecture JavaDoc, Interface Definition Files
and XSD files (the "Artifacts") in any medium without fee or royalty is
hereby granted, provided that you include the following on ALL copies
of the Artifacts, or portions thereof, that you make:
1. A link or URL to the Artifacts at this location:
http://www.osoa.org/display/Main/Service+Component+Architecture
+Specifications
2. The full text of this copyright notice as shown in the Artifacts.
THE ARTIFACTS ARE PROVIDED "AS IS," AND THE AUTHORS MAKE NO
REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, REGARDING THE
ARTIFACTS AND THE IMPLEMENTATION OF THEIR CONTENTS, INCLUDING, BUT NOT
LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, NON-INFRINGEMENT OR TITLE.
THE AUTHORS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL,
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF OR RELATING TO ANY
USE OR DISTRIBUTION OF THE ARTIFACTS.
The name and trademarks of the Authors may NOT be used in any manner,
including advertising or publicity pertaining to the Service Component
Architecture Specification or its contents without specific, written
prior permission. Title to copyright in the Service Component
Architecture Specification and the JavaDoc, Interface Definition Files
and XSD Files will at all times remain with the Authors.
No other rights are granted by implication, estoppel or otherwise.
Revision level 1.1, last updated on 2007/11/19
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
RE: Field of use constraint on OSOA license?
Posted by Janet Campbell <ja...@eclipse.org>.
Yes, my understanding is that the new version of the license has now been
posted.
Janet Campbell
Phone: +1.613.224.9461, x.229 (GMT -5)
Fax: +1.613.224.5172
janet.campbell@eclipse.org
-----Original Message-----
From: Oisin Hurley [mailto:ohurley@iona.com]
Sent: Friday, December 21, 2007 5:36 AM
To: Janet Campbell
Cc: general@incubator.apache.org; 'Legal Discuss'
Subject: Re: Field of use constraint on OSOA license?
On 20 Dec 2007, at 20:50, Janet Campbell wrote:
> We have been in touch with the OSOA folks and the license restriction
> referred to below has now been removed.
Thanks for pushing that through, Janet. Have you secured the new
license text, and has it been posted on the OSOA site do you know?
best regards
Oisin
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Field of use constraint on OSOA license?
Posted by Paul Fremantle <pz...@gmail.com>.
Seems like we need to ensure the next release has the updated licenses
in it. Thanks for helping to sort this out Jeremy!
Paul
On Dec 21, 2007 11:50 AM, Oisin Hurley <oh...@iona.com> wrote:
> > The updated license files are published on the OSOA site:
> >
> > http://www.osoa.org/xmlns/sca/1.0/license.txt
> >
> > and
> >
> > http://www.osoa.org/sdo/2.1/schemas/license.txt
>
> Thanks for the update, Mike. I couldn't find the update on the
> site but I see now that you've made a Latest News entry with the
> updated links. One more for the RSS reader.
>
>
> best regards
> Oisin
>
> ----------------------------
> IONA Technologies PLC (registered in Ireland)
> Registered Number: 171387
> Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Field of use constraint on OSOA license?
Posted by Oisin Hurley <oh...@iona.com>.
> The updated license files are published on the OSOA site:
>
> http://www.osoa.org/xmlns/sca/1.0/license.txt
>
> and
>
> http://www.osoa.org/sdo/2.1/schemas/license.txt
Thanks for the update, Mike. I couldn't find the update on the
site but I see now that you've made a Latest News entry with the
updated links. One more for the RSS reader.
best regards
Oisin
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Field of use constraint on OSOA license?
Posted by Mike Edwards <mi...@gmail.com>.
Oisin,
The updated license files are published on the OSOA site:
http://www.osoa.org/xmlns/sca/1.0/license.txt
and
http://www.osoa.org/sdo/2.1/schemas/license.txt
Yours, Mike.
Oisin Hurley wrote:
>
> On 20 Dec 2007, at 20:50, Janet Campbell wrote:
>
>> We have been in touch with the OSOA folks and the license restriction
>> referred to below has now been removed.
>
> Thanks for pushing that through, Janet. Have you secured the new
> license text, and has it been posted on the OSOA site do you know?
>
> best regards
> Oisin
>
> ----------------------------
> IONA Technologies PLC (registered in Ireland)
> Registered Number: 171387
> Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
RE: Field of use constraint on OSOA license?
Posted by Janet Campbell <ja...@eclipse.org>.
Yes, my understanding is that the new version of the license has now been
posted.
Janet Campbell
Phone: +1.613.224.9461, x.229 (GMT -5)
Fax: +1.613.224.5172
janet.campbell@eclipse.org
-----Original Message-----
From: Oisin Hurley [mailto:ohurley@iona.com]
Sent: Friday, December 21, 2007 5:36 AM
To: Janet Campbell
Cc: general@incubator.apache.org; 'Legal Discuss'
Subject: Re: Field of use constraint on OSOA license?
On 20 Dec 2007, at 20:50, Janet Campbell wrote:
> We have been in touch with the OSOA folks and the license restriction
> referred to below has now been removed.
Thanks for pushing that through, Janet. Have you secured the new
license text, and has it been posted on the OSOA site do you know?
best regards
Oisin
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Field of use constraint on OSOA license?
Posted by Oisin Hurley <oh...@iona.com>.
On 20 Dec 2007, at 20:50, Janet Campbell wrote:
> We have been in touch with the OSOA folks and the license restriction
> referred to below has now been removed.
Thanks for pushing that through, Janet. Have you secured the new
license text, and has it been posted on the OSOA site do you know?
best regards
Oisin
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Field of use constraint on OSOA license?
Posted by Oisin Hurley <oh...@iona.com>.
On 20 Dec 2007, at 20:50, Janet Campbell wrote:
> We have been in touch with the OSOA folks and the license restriction
> referred to below has now been removed.
Thanks for pushing that through, Janet. Have you secured the new
license text, and has it been posted on the OSOA site do you know?
best regards
Oisin
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
RE: Field of use constraint on OSOA license?
Posted by Janet Campbell <ja...@eclipse.org>.
We have been in touch with the OSOA folks and the license restriction
referred to below has now been removed.
Janet Campbell
Legal Counsel & Manager, Intellectual Property
Eclipse Foundation Inc.
-----Original Message-----
From: Oisin Hurley [mailto:ohurley@iona.com]
Sent: Monday, October 01, 2007 9:09 AM
To: general@incubator.apache.org
Cc: Legal Discuss
Subject: Re: Field of use constraint on OSOA license?
> This is the point that concerns me. As I read it, users are only
> permitted to "copy, make derivative works of, and distribute" these
> items "as part of a compliant implementation." FoU may be the wrong
> term, but that clause is imposing restrictions on users that go
> beyond the Apache License as they are constrained to a "compliant
> implementation".
We use these files in the Eclipse SOA Tools Project, and we are
certainly not building any type of SCA implementation -- merely a
brightly colored editor to visualize SCA Assemblies. So, FWIW,
these files have made it through the Eclipse Legal process...
best regards
Oisin
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
RE: Field of use constraint on OSOA license?
Posted by Janet Campbell <ja...@eclipse.org>.
We have been in touch with the OSOA folks and the license restriction
referred to below has now been removed.
Janet Campbell
Legal Counsel & Manager, Intellectual Property
Eclipse Foundation Inc.
-----Original Message-----
From: Oisin Hurley [mailto:ohurley@iona.com]
Sent: Monday, October 01, 2007 9:09 AM
To: general@incubator.apache.org
Cc: Legal Discuss
Subject: Re: Field of use constraint on OSOA license?
> This is the point that concerns me. As I read it, users are only
> permitted to "copy, make derivative works of, and distribute" these
> items "as part of a compliant implementation." FoU may be the wrong
> term, but that clause is imposing restrictions on users that go
> beyond the Apache License as they are constrained to a "compliant
> implementation".
We use these files in the Eclipse SOA Tools Project, and we are
certainly not building any type of SCA implementation -- merely a
brightly colored editor to visualize SCA Assemblies. So, FWIW,
these files have made it through the Eclipse Legal process...
best regards
Oisin
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Field of use constraint on OSOA license?
Posted by Oisin Hurley <oh...@iona.com>.
> This is the point that concerns me. As I read it, users are only
> permitted to "copy, make derivative works of, and distribute" these
> items "as part of a compliant implementation." FoU may be the wrong
> term, but that clause is imposing restrictions on users that go
> beyond the Apache License as they are constrained to a "compliant
> implementation".
We use these files in the Eclipse SOA Tools Project, and we are
certainly not building any type of SCA implementation -- merely a
brightly colored editor to visualize SCA Assemblies. So, FWIW,
these files have made it through the Eclipse Legal process...
best regards
Oisin
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Field of use constraint on OSOA license?
Posted by Oisin Hurley <oh...@iona.com>.
> This is the point that concerns me. As I read it, users are only
> permitted to "copy, make derivative works of, and distribute" these
> items "as part of a compliant implementation." FoU may be the wrong
> term, but that clause is imposing restrictions on users that go
> beyond the Apache License as they are constrained to a "compliant
> implementation".
We use these files in the Eclipse SOA Tools Project, and we are
certainly not building any type of SCA implementation -- merely a
brightly colored editor to visualize SCA Assemblies. So, FWIW,
these files have made it through the Eclipse Legal process...
best regards
Oisin
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Field of use constraint on OSOA license?
Posted by Jeremy Boynes <jb...@apache.org>.
On Sep 30, 2007, at 11:30 AM, Niclas Hedhman wrote:
> On Sunday 30 September 2007 01:53, Jeremy Boynes wrote:
>> The recent Tuscany distribution contains XSDs licensed under the OSOA
>> license[1] which contains the following:
>> "Permission to copy, make derivative works of, and distribute the
>> Service Component Architecture
>> JavaDoc, Interface Definition Files and XSD files in any medium
>> without fee or royalty as part
>> of a compliant implementation of the Service Component Architecture
>> Specification is hereby granted."
>>
>> Is the restriction to a "compliant implementation" a field of use
>> constraint that Tuscany project should be concerned about?
>
> Perhaps it is more of a matter for the legal-discuss@ list than
> here...
This has come up there before but I have not seen a resolution. I
cc'ed them on this reply.
>
> But, I agree with Roland that this is not FoU restrictions. I find the
> formulation a bit odd, but think the intent is to ensure that the spec
> doesn't "evolve" beyond the control of OSOA. Especially since it
> mentions "Permission to ... make derivative works of ... Interface
> Definition
> Files".
This is the point that concerns me. As I read it, users are only
permitted to "copy, make derivative works of, and distribute" these
items "as part of a compliant implementation." FoU may be the wrong
term, but that clause is imposing restrictions on users that go
beyond the Apache License as they are constrained to a "compliant
implementation".
This seems the same issue we had with libraries from JSRs and which
led to the creation of our own XSDs and API files in Geronimo so that
we could provide them under the AL (back in the days before Sun's
were available under CDDL). Tuscany already has an AL version of the
APIs so this would only affect the XSDs.
--
Jeremy
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Field of use constraint on OSOA license?
Posted by Jeremy Boynes <jb...@apache.org>.
On Sep 30, 2007, at 11:30 AM, Niclas Hedhman wrote:
> On Sunday 30 September 2007 01:53, Jeremy Boynes wrote:
>> The recent Tuscany distribution contains XSDs licensed under the OSOA
>> license[1] which contains the following:
>> "Permission to copy, make derivative works of, and distribute the
>> Service Component Architecture
>> JavaDoc, Interface Definition Files and XSD files in any medium
>> without fee or royalty as part
>> of a compliant implementation of the Service Component Architecture
>> Specification is hereby granted."
>>
>> Is the restriction to a "compliant implementation" a field of use
>> constraint that Tuscany project should be concerned about?
>
> Perhaps it is more of a matter for the legal-discuss@ list than
> here...
This has come up there before but I have not seen a resolution. I
cc'ed them on this reply.
>
> But, I agree with Roland that this is not FoU restrictions. I find the
> formulation a bit odd, but think the intent is to ensure that the spec
> doesn't "evolve" beyond the control of OSOA. Especially since it
> mentions "Permission to ... make derivative works of ... Interface
> Definition
> Files".
This is the point that concerns me. As I read it, users are only
permitted to "copy, make derivative works of, and distribute" these
items "as part of a compliant implementation." FoU may be the wrong
term, but that clause is imposing restrictions on users that go
beyond the Apache License as they are constrained to a "compliant
implementation".
This seems the same issue we had with libraries from JSRs and which
led to the creation of our own XSDs and API files in Geronimo so that
we could provide them under the AL (back in the days before Sun's
were available under CDDL). Tuscany already has an AL version of the
APIs so this would only affect the XSDs.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Field of use constraint on OSOA license?
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Sunday 30 September 2007 01:53, Jeremy Boynes wrote:
> The recent Tuscany distribution contains XSDs licensed under the OSOA
> license[1] which contains the following:
> "Permission to copy, make derivative works of, and distribute the
> Service Component Architecture
> JavaDoc, Interface Definition Files and XSD files in any medium
> without fee or royalty as part
> of a compliant implementation of the Service Component Architecture
> Specification is hereby granted."
>
> Is the restriction to a "compliant implementation" a field of use
> constraint that Tuscany project should be concerned about?
Perhaps it is more of a matter for the legal-discuss@ list than here...
But, I agree with Roland that this is not FoU restrictions. I find the
formulation a bit odd, but think the intent is to ensure that the spec
doesn't "evolve" beyond the control of OSOA. Especially since it
mentions "Permission to ... make derivative works of ... Interface Definition
Files".
IANAL,
--
Niclas Hedhman, Software Developer
I live here; http://tinyurl.com/2qq9er
I work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org