Re: Question: Content Migration from OASIS Open Repositories to Chartered Work Product Repositories

[Robin Cover <robin@oasis-open.org>]

Hi Patrick.  On your question about "migrating" content from an OASIS Open Repository to an OASIS TC's repository or other TC's publication venue:

You did not indicate which open source license you would be using for the candidate OASIS Open Repository, but consideration of that license would be one element in a person's determination about taking Open Repo content and contributing it to an OASIS TC.  I think you probably mean "contribute" when you say "migrate" and "use".

The OASIS rules for Contributions to a TC will all apply if/when some CTI TC Member makes a contribution by copying content from an (any) OASIS Open Repository.  The decision to make a Contribution to a TC is always an individual (private, personal) decision in terms of the OASIS policies.

Some direct links to definitions, and to the CTI TC's IPR Mode are provided below, as example documentation [1] - [4]

I think relevant guidance on your question is found in the Open Repositories FAQ, Qs/As #16 and #18 (supplemented by #17), as also reflected in fixed/boilerplate text from OASIS Open Repository "Contributing" document, together with clarifications from the agreement/license text in the (Individual) CLA

========================

From the FAQ document

========================

16. What is the relationship between a TC's Open Repositories and its formal specifications?

https://www.oasis-open.org/resources/open-repositories/faq#relationToSpecifications

 [ 17. Can a contributor to a TC's Open Repository push a contribution to the TC for use in its formal specifications?

https://www.oasis-open.org/resources/open-repositories/faq#pushingContentToTC  ]

18. Can a TC member pull material from one of its Open Repositories into the TC's formal specifications?

https://www.oasis-open.org/resources/open-repositories/faq#pullingContentFromRepo

=============================================================

Text from OASIS Open Repository "Contributing" document

=============================================================

https://github.com/oasis-open/cti-stix2-json-schemas/blob/master/CONTRIBUTING.md#licensing-distinct-from-oasis-ipr-policy

https://github.com/oasis-open/cti-stix2-json-schemas/blob/master/CONTRIBUTING.md#governance-distinct-from-oasis-tc-process

Licensing Distinct from OASIS IPR Policy

Because different licenses apply to the OASIS TC's specification work, and this Open Repository, there is no guarantee that the licensure of specific repository material will be compatible with licensing requirements of an implementation of a TC's specification. Please refer to the LICENSE file for the terms of this material, and to the OASIS IPR Policy for the terms applicable to the TC's specifications, including any applicable declarations.

=================================

Agreement/license text in CLA

=================================

https://www.oasis-open.org/resources/open-repositories/cla/individual-cla

 required for all persons for substantive contributions 

[ https://www.oasis-open.org/resources/open-repositories/cla/entity-cla

 - "optional" ]

--------

Beyond providing these links to some relevant passages in the policies and

published guidance documents, I can't offer legal opinions -- and nothing

even here constitutes legal opinion or legal counsel from Robin-IANAL

Best wishes,

- Robin

[1]  IPR Policy definition

https://www.oasis-open.org/policies-guidelines/ipr#def-contribution

Contribution - any material submitted to an OASIS Technical Committee by a TC Member in writing or electronically, whether in an in-person meeting or in any electronic conference or mailing list maintained by OASIS for the OASIS Technical Committee and which is or was proposed for inclusion in an OASIS Deliverable. 

[2] IPR Policy "CONTRIBUTIONS" 

https://www.oasis-open.org/policies-guidelines/ipr#contributions

[3] 5. CONTRIBUTIONS

5.1 General

At the time of submission of a Contribution for consideration by an OASIS Technical Committee, each named co-Contributor (and its respective Affiliates) is deemed to agree to the following terms and conditions and to make the following representations (based on the actual knowledge of the TC Member(s) making the Contribution, with respect to items 3 - 5 below, inclusive):

    OASIS has no duty to publish or otherwise use or disseminate any Contribution.

    OASIS may reference the name(s) of the Contributor(s) for the purpose of acknowledging and publishing the Contribution.

    The Contribution properly identifies any holders of copyright interests in the Contribution.

    No information in the Contribution is confidential, and OASIS may freely disclose any information in the Contribution.

    There are no limits to the Contributor's ability to make the grants, acknowledgments, and agreements required by this Policy with respect to such Contribution.

[... see continuation]

See also:

Contribution Obligation - a licensing or non-assertion requirement, as described in Section 10 that results from making a Contribution as described in Section 9.1.

Contributor - a TC Party on whose behalf a Contribution is made by the TC Party's TC Member. 

[4] OASIS IPR Policy

10.3. Non-Assertion Mode TC Requirements

https://www.oasis-open.org/policies-guidelines/ipr#Non-Assertion-Mode

{with}

CTI TC IPR Statement

https://www.oasis-open.org/committees/cti/ipr.php

... This TC operates under the Non-Assertion Mode of the OASIS IPR Policy....

On Tue, Sep 20, 2016 at 9:43 PM, Patrick Maroney <Pmaroney@specere.org> wrote:

Chet,

I'm drafting the requests for the CTI TC Iinteroperability SC Open & Chartered Work Product Repositories and need to first validate a key assumption in the specification and organization of related content.

Part of the content in the proposed CTI TC Interoperability Open Repository will include "ad hoc" Configuration Instructions, Test Data Sets, and step-by-step procedures used to test and validate integration and interoperability between a given pair of Commercial Products and/or Open Source  Project Tools and Frameworks.   

We have all of these elements compiled for two reference implementations: 

(1) [CRITs <==> EclecticIQ]

(2) [CRITs <==> Soltra Hail-A-Taxii].  

David Eilken and I envision the continuation of these efforts to proto-type, refine, and build out our documentation processes, formats, relationships, and contacts for this ad hoc Interoperability initiative.  We also want engage with as many interetsed stakeholders in the OASIS and Open Source Communities to incorporate their contributions and any alternative approaches/ideas.

At some point in the future we will likely want to use portions of this "ad hoc" content to produce formalized work products and migrate it to the Interoperability Chartered Work Product Repositories.  This outcome is still TBD, but I want to ensure we plan for this eventuality and ensure we have a clear path to execute on this strategy.

The CLA for the Open Repository states that :

"Subject to the terms of this CLA, and without limiting the terms of the Applicable License, you also hereby grant to OASIS a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute your Contributions and such derivative works."

I believe this clause gives us clear license to freely subsume any and all content contributed to the CTI Open Repositories as direct or derivative formal work product in the Chartered Work Product Repositories.  This interpretation includes the  specific Interoperability content use case outlined here.

Is this correct?

Patrick Maroney
President
Integrated Networking Technologies, Inc.
Desk: (856)983-0001
Cell: (609)841-5104
Email: pmaroney@specere.org

--

Robin Cover
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: robin@oasis-open.org
Staff bio: http://www.oasis-open.org/people/staff/robin-cover
Cover Pages: http://xml.coverpages.org/
Newsletter: http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-296-1783