Skip to main content

Eclipse Dataspace Working Group Charter

Version 1.0 - Revision history at end of document

Vision and Scope

The mission of the Eclipse Dataspace Working Group is to provide a forum for individuals and organizations to build and promote open-source software, specifications, and open collaboration models needed to create scalable, modular, extensible, industry-ready open-source components based on open standards for dataspaces.

The primary objective of the Eclipse Dataspace Working Group is to encourage, develop, and promote open-source solutions that will enable the development, as well as the participation in dataspaces for organizations of all types and sizes. It does not favor a specific industry or type of organization and is fully dedicated to enable global adoption of dataspace technologies to foster the creation and operation of trusted data sharing ecosystems.

The working group will have a strong focus on participating in standards development, implementation and onboarding of existing open-source projects and providing guidance to associated projects on alignment with the overarching goal of supporting a broad ecosystem of interoperable dataspaces.

To this end, the working group aims to foster a component driven model that supports project collections in 3 distinct groups:

Dataspace Core & Protocols:

DCP focuses on the core protocol specifications and their standardization. It also provides alignment between the protocol specifications and OSS projects implementing mandatory dataspace functionality.

Dataspace Data Planes & Components

DDPC focuses on alignment between projects that implement data planes, which are essential components for dataspaces as well as additional optional components which enable advanced dataspace scenarios. These includes components which are not essential to create a viable dataspace but add capabilities that increase the business value of dataspaces.

Dataspace Authority & Management

DAM focuses on alignment of tools and workflows to enable the implementation of dataspaces. Its associated projects will support Dataspace Authorities to manage their dataspaces. This includes policy management, member management, and also starter kits for dataspace authorities.

Overall the 3 groups of open-source projects are aiming to create an ecosystem of projects covering diverse aspects of dataspace solutions. Implementations are non-exclusive and competing/overlapping projects can exist. Especially in the group of Dataspace Data Planes & Components multiple overlapping projects are expected to emerge and co-exists from the beginning. Even Dataspace Core Components can have diverging implementations. Protocols are going to be the unifying aspect between projects, providing minimum viable interoperability.

Mission of the Working Group

  • Foster open source implementations of needed components for dataspaces (build a core first).
  • Define, document, standardize and promote protocols that Dataspace-related open source projects may choose to utilize in their development.
  • Define, document, and promote processes that Dataspace-related open source projects may choose to utilize in their development.
  • Define rules and a branding process for projects which participate in the Dataspace Working Group to inform the market of their relation to dataspaces and their process maturity.
  • Define compatibility rules and a compatibility and branding process for implementations of these components to ensure interoperability.
  • Enable reference distributions and foster integrations in various developer toolchains.
  • Drive the funding model that enables this working group and its community to operate on a sustainable basis.
  • Promote the Eclipse Dataspace brand, along with any additional brands as approved by the Steering Committee and the Eclipse Foundation, and their value in the marketplace.
  • Provide vendor neutral marketing and other services to the Dataspace ecosystem.
  • Communicate/Liaise with other open-source and specification communities.
  • Leverage Eclipse-defined licensing and intellectual property flows that encourage community participation, protect community members, and encourage usage.
  • Manage the overall technical and business strategies related to its open source projects.

Governance and Precedence

Applicable Documents

The following governance documents are applicable to this charter, each of which can be found on the Eclipse Foundation Governance Documents page or the Eclipse Foundation Legal Resources page:

  • Eclipse Foundation Bylaws
  • Eclipse Foundation Working Group Process
  • Eclipse Foundation Working Group Operations Guide
  • Eclipse Foundation Code of Conduct
  • Eclipse Foundation Communication Channel Guidelines
  • Eclipse Foundation Membership Agreement
  • Eclipse Foundation Intellectual Property Policy
  • Eclipse Foundation Antitrust Policy
  • Eclipse Foundation Development Process
  • Eclipse Foundation Trademark Usage Guidelines
  • Eclipse Foundation Specification Process
  • Eclipse Foundation Specification License
  • Eclipse Foundation Technology Compatibility kit license

All Members must be parties to the Eclipse Foundation Membership Agreement, including the requirement set forth in Section 2.2 to abide by and adhere to the Bylaws and then-current policies of the Eclipse Foundation, including but not limited to the Intellectual Property and Antitrust Policies.

In the event of any conflict between the terms set forth in this working group's charter and the Eclipse Foundation Bylaws, Membership Agreement, Development Process, Specification Process, Working Group Process or any policies of the Eclipse Foundation, the terms of the respective Eclipse Foundation Bylaws, Membership Agreement, process or policy shall take precedence.

Membership

With the exception of Guest members as described below, an entity must be at least a Contributing Member of the Eclipse Foundation, have executed the Eclipse Dataspace Working Group Participation Agreement, and adhere to the requirements set forth in this Charter to participate.

The participation fees associated with each of these membership classes are shown in the Annual Participation Fees section. These are annual fees, and are established by the Eclipse Dataspace Working Group Steering Committee, and will be updated in this charter document accordingly.

The fees associated with membership in the Eclipse Foundation are separate from any Working Group membership fees, and are decided as described in the Eclipse Foundation Bylaws and detailed in the Eclipse Foundation Membership Agreement.

There are five classes of the Eclipse Dataspace Working Group membership - Strategic, Participant, Committer, Supporter and Guest.

Classes of Membership

Strategic Members

Strategic Members are organizations that view this Working Group standards, specifications and technologies as strategic to their organization and are investing significant resources to sustain and shape the activities of this working group. Strategic Members of the working group are required to commit to strategic membership for a three (3) year period. Strategic Members of this working group must be at least a Contributing Member of the Eclipse Foundation.

Participant Members

Participant Members are typically organizations that deliver products or services based upon related standards, specifications and technologies, or view this working group's standards and technologies as strategic to their organization. These organizations want to participate in the development and direction of an open ecosystem related to this working group. Participant Members of this working group must be at least a Contributing Member of the Eclipse Foundation.

Committer Members

Committers are individuals who, through a process of meritocracy defined by the Eclipse Foundation Development Process, are able to contribute and commit code to the Eclipse Foundation projects included in the scope of this working group. Committers may become members of the working group by virtue of working for a member organization, or may choose to complete the membership-at-large process independently if they are not, along with completing this working group's Participation Agreement once defined. For further explanation and details, see the Eclipse Committer Membership page.

Supporting Members

Supporting Members are: (a) organizations that want to participate in an open ecosystem related to this working group and wish to show their initial support for it, and (b) organizations which are at least Contributing members of the Eclipse Foundation. Organizations may be Supporting Members for a maximum period of 1 year only, after which time they are expected to change their membership to a different level. Supporting Members may be invited to participate in committee meetings at the invitation of the respective committee, but under no circumstances do Supporting Members have voting rights in any working group body. Further, Supporting Members are not considered Participant Members as that term is defined in the Eclipse Foundation Specification Process. Supporting Members are required to execute the Working Group's Participation Agreement.

Guest Members

Guest Members are organizations which are Associate members of the Eclipse Foundation. Typical guests include R&D partners, universities, academic research centers, etc. Guests may be invited to participate in committee meetings at the invitation of the respective committee, but under no circumstances do Guest members have voting rights. Guest members are required to execute the Working Group's Participation Agreement.

Membership Summary

Committee Representation Strategic Member Participant Member Committer Member Supporter Member Guest Member
Steering Committee Appointed Elected Elected N/A N/A
Marketing and Brand Committee Appointed Elected Elected N/A N/A
Specification Committee Appointed Elected Elected N/A N/A
Technical Advisory Committee Appointed Elected Elected N/A N/A

Governance

This Eclipse Dataspace Working Group is designed as:

  • a vendor-neutral, member-, and contribution driven organization
  • a means to foster a vibrant and sustainable ecosystem of components and service providers
  • a means to organize the community of each project or component so that users and developers define the roadmap collaboratively.

Governing Bodies

Steering Committee

Powers and Duties

Steering Committee members are required to:

  • Define and manage the strategy of the working group.
  • Define and manage which Eclipse Foundation projects are included within the scope of this working group.
  • Ensure the consistency of logo usage and other marketing materials.
  • Define and manage the technical roadmap.
  • Review and approve this charter.
  • Review and approve any trademark policy referred to it by the Marketing and Brand Committee.
  • Define the annual fees for all classes of the working group members.
  • Establish an annual program plan.
  • Approve the annual budget based upon funds received through fees.
  • Approve (if any) customizations to the Eclipse Foundation Specification Process recommended by the Specification Committee.
  • Approve the creation of subcommittees and define the purpose, scope, and membership of each such subcommittee.
  • Approve the creation and retirement of Special Interest Groups (SIGs).

Composition

Each Strategic Member of the working group is entitled to a seat on the Steering Committee.

Participant Members shall be entitled to at least one (1) seat on the Steering Committee. In addition, an additional seat on the Steering Committee shall be allocated to the Participant Members for every additional five (5) seats beyond one (1) allocated to Strategic Members via election. Participant Member seats are allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse Foundation Bylaws.

One seat is allocated to Committer Members via election. The Committer Member seat is allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse Bylaws.

The Committee elects a chair of the Steering Committee. This chair is elected among the members of the Committee. They will serve for a 12 month period or until their successor is elected and qualified, or as otherwise provided for in this Charter. There is no limit on the number of terms the chair may serve.

Meeting Management

The Steering Committee meets at least twice a year.

Marketing and Brand Committee

Powers and Duties

The Marketing and Brand Committee members are required to:

  • Define strategic marketing priorities, goals, and objectives for the working group.
  • Coordinate and support the implementation of developer and end-user outreach programs.
  • Raise issues for discussion and provide feedback to the Foundation on the execution of marketing, brand, and communications activities for the working group.
  • Assist the Eclipse Foundation in the working group's participation in conferences and events related to the working group.
  • Define the trademark policy, if applicable, and refer to it for approval by the Steering Committee.
  • Collaborate with other working group members to develop co-marketing strategies, amplify messaging on social channels, and share best practices.

Committee members are expected to be leaders in communicating key messaging on behalf of the working group, and to play a leadership role in driving the overall success of the working group marketing efforts. In particular, members are encouraged to engage their respective marketing teams and personnel to amplify and support the achievement of the working group's goals and objectives.

Composition

Each Strategic Member of the working group is entitled to a seat on the Marketing Committee.

Participant Members shall be entitled to at least one (1) seat on the Marketing Committee. In addition, an additional seat on the Marketing Committee shall be allocated to the Participant Members for every additional five (5) seats beyond one (1) allocated to Strategic Members via election. Participant Member seats are allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse Bylaws.

One seat is allocated to Committer Members via election. The Committer Member seat is allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse Bylaws.

The Committee elects a chair who reports to the Steering Committee. This chair is elected among the members of the Committee. They will serve for a 12 month period or until their successor is elected and qualified, or as otherwise provided for in this Charter. There is no limit on the number of terms the chair may serve.

Meeting Management

The Marketing and Brand Committee meets at least twice a year.

Specification Committee

Powers and Duties

Specification Committee members are required to:

  • Ensure that all specification projects operate in an open, transparent, and vendor-neutral fashion in compliance with the specification process.
  • Apply and govern the specification projects in the scope of this working group according to the approved specification process.
  • Approve specifications for adoption by the community.
  • Work with the related Project Management Committee (PMC) to ensure that the EFSP is complied with by all related working group specification projects.
  • Review and approve the trademark policy to ensure compatibility of independent implementations of specifications.
  • Define (if any) customizations to the EFSP. The EFSP with the approved customizations is the specification process to be used by all specifications related to this working group, and refer for approval by the Steering Committee.

Composition

Each Strategic Member of the working group is entitled to have a seat on the Specification Committee.

Participant Members shall be entitled to at least one (1) seat on the Specification Committee. In addition, an additional seat on the Specification Committee shall be allocated to the Participant Members for every additional five (5) seats beyond one (1) allocated to Strategic Members via election. Participant Member seats are allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse Bylaws.

One seat is allocated to Committer Members via election. The Committer Member seat is allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse Bylaws.

Any additional individuals as designated from time to time by the Executive Director.

The Committee elects a chair who reports to the Steering Committee. This chair is elected among the members of the Committee. They will serve for a 12 month period or until their successor is elected and qualified, or as otherwise provided for in this Charter. There is no limit on the number of terms the chair may serve.

Meeting Management

The Specification Committee meets at least once a quarter.

Technical Advisory Committee

Powers and Duties

Technical Advisory Committee members are required to:

  • Recommend to the Steering Committee which Eclipse Foundation open-source projects should be included within the purview of the Eclipse Dataspace Working Group.
  • Establish, evolve, and enforce policies and processes that augment the Eclipse Foundation Development Process and the Eclipse Foundation Specification Process to support dataspace requirements for the Eclipse Foundation open source projects that choose to contribute content to the Eclipse Dataspace-branded releases. Where appropriate, process definition work may be referred to the Specification Committee to be developed under the Eclipse Foundation Specification process.
  • Establish a roadmap at least annually for review and approval by the Steering Committee.
  • Establish a roadmap process which will solicit input from and build rough consensus with stakeholders including Projects and Project Management Committees.
  • Establish a coordinated release plan that balances the many competing requirements. The release plan describes the themes and priorities that focus these releases, and orchestrates the dependencies among project plans.
  • Coordinate the distribution release process and cross-project planning, facilitate the mitigation of architectural issues and interface conflicts, and generally address all other coordination and integration issues.
  • Set, evolve, and enforce engineering policies and procedures for the creation and distribution of Eclipse Dataspace-branded releases, along with all intermediate releases.

The Technical Advisory Committee discharges its responsibility via collaborative evaluation, prioritization, and compromise. The Technical Advisory Committee will establish a set of principles to guide its deliberations which will be approved by the Steering Committee and the Executive Director.

Composition

Each Strategic Member of the working group is entitled to have a seat on the Technical Advisory Committee.

Participant Members shall be entitled to at least one (1) seat on the Technical Advisory Committee. In addition, an additional seat on the Technical Advisory Committee shall be allocated to the Participant Members for every additional five (5) seats beyond one (1) allocated to Strategic Members via election. Participant Member seats are allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse Bylaws.

One seat is allocated to Committer Members via election. The Committer Member seat is allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse Bylaws.

One seat is allocated for a representative of each Project Management Committee (PMC) responsible for the governance of one or more projects within the purview of the Eclipse Dataspace Working Group.

Any additional individuals as designated from time to time by the Executive Director.

The Committee elects a chair who reports to the Steering Committee. This chair is elected among the members of the Committee. They will serve for a 12 month period or until their successor is elected and qualified, or as otherwise provided for in this Charter. There is no limit on the number of terms the chair may serve.

Meeting Management

The Technical Advisory Committee meets at least once a quarter.

Special Interest Groups

A Special Interest Group (SIG) is a lightweight structure formed within the Working Group with a focus to collaborate around a particular topic or domain of direct interest to the working group. SIGs are designed to drive the objectives of a subset of the Members of the Working Group in helping them achieve a dedicated set of goals and objectives. The scope of the SIG must be consistent with the scope of the Working Group Charter.

The creation of a SIG requires approval of the Steering Committee. Each SIG may be either temporary or a permanent structure within the working group. SIGs can be disbanded at any time by self-selection presenting reasons to and seek approval from the Steering Committee. Steering Committees may disband a SIG at any time for being inactive or non-compliant with the Working Group's Charter, or by request of the SIG itself. SIGs operate as a non-governing Body of the Working Group. There are no additional annual fees to Members for participation in a SIG.

Sponsorship

Sponsors are companies or individuals who provide money or services to the working group on an ad hoc basis to support the activities of the Working Group and its managed projects. Money or services provided by sponsors are used as set forth in the working group annual budget. The working group is free to determine whether and how those contributions are recognized. Under no condition are sponsorship monies refunded.

Sponsors need not be members of the Eclipse Foundation or of the Working Group.

Common Dispositions

The dispositions below apply to all governance bodies for this working group, unless otherwise specified. For all matters related to membership action, including without limitation: meetings, quorum, voting, vacancy, resignation or removal, the respective terms set forth in the Eclipse Foundation Bylaws apply.

Appointed representatives on the Body may be replaced by the Member organization they are representing at any time by providing written notice to the Steering Committee. In the event a Body member is unavailable to attend or participate in a meeting of the Body, they may be represented by another Body member by providing written proxy to the Body's mailing list in advance. As per the Eclipse Foundation Bylaws, a representative shall be immediately removed from the Body upon the termination of the membership of such representative's Member organization.

Voting

Simple Majority

Excepting the actions specified below for which a Super Majority is required, votes of the Body are determined by a simple majority of the representatives represented at a committee meeting at which a quorum is present.

Super Majority

For actions (i) requesting that the Eclipse Foundation Board of Directors approve a specification license; (ii) approving specifications for adoption; (iii) modifying the working group charter; (iv) approving or changing the name of the working group; and (v) approving changes to annual Member contribution requirements; any such actions must be approved by no less than two-thirds (2/3) of the representatives represented at a committee meeting at which a quorum is present.

Term and Dates of Elections

This section applies to all committees.

All representatives shall hold office until their respective successors are appointed or elected, as applicable. There shall be no prohibition on re-election or re-designation of any representative following the completion of that representative's term of office.

Strategic Members

Strategic Members Representatives shall serve in such capacity on committees until the earlier of their removal by their respective appointing Member organization or as otherwise provided for in this Charter.

Elected Representatives

Elected representatives shall each serve one-year terms and shall be elected to serve for a 12 month term or until their respective successors are elected and qualified, or as otherwise provided for in this Charter. Procedures governing elections of Representatives may be established pursuant to resolutions of the Steering Committee provided that such resolutions are not inconsistent with any provision of this Charter.

Meetings Management

As prescribed in the Eclipse Foundation Working Group Process, all meetings related to the working group will follow a prepared agenda and minutes are distributed two weeks after the meeting and approved at the next meeting at the latest, and shall in general conform to the Eclipse Foundation Antitrust Policy.

Meeting Frequency

All meetings may be held at any place that has been designated from time-to-time by resolution of the corresponding Body. All meetings may be held remotely using phone calls, video calls, or any other means as designated from time-to-time by resolution of the corresponding Body.

Place of Meetings

All meetings may be held at any place that has been designated from time-to-time by resolution of the corresponding Body. All meetings may be held remotely using phone calls, video calls, or any other means as designated from time-to-time by resolution of the corresponding Body.

Regular Meetings

No Body meeting will be deemed to have been validly held unless a notice of same has been provided to each of the representatives at least fifteen (15) calendar days prior to such meeting, which notice will identify all potential actions to be undertaken by the Body at the Body meeting. No representative will be intentionally excluded from Body meetings and all representatives shall receive notice of the meeting as specified above; however, Body meetings need not be delayed or rescheduled merely because one or more of the representatives cannot attend or participate so long as at least a quorum of the Body is represented at the Body meeting.

Actions

The Body may undertake an action only if it was identified in a Body meeting notice or otherwise identified in a notice of special meeting.

Invitations

The Body may invite any member to any of its meetings. These invited attendees have no right to vote.

Working Group Participation Fees

The initial Steering Committee will be tasked with defining a fee structure and budget for the current and following years based on resource requirements necessary to achieve the objectives of the group. Members agree to pay the annual fees as established by the Steering Committee and as agreed to by each participating member in their respective Working Group Participation Agreement.

No Participation Fees are charged in 2023. All Members who join prior to January 1, 2024, agree to begin paying the full annual fees associated with their participation effective January 2024 and each January thereafter. All Members who join the working group in 2024 or beyond shall pay the full annual fees effective the month they join the working group, and each anniversary month thereafter.

Established fees cannot be changed retroactively. Any change to the annual fees will be communicated to all Members via the mailing list and will be reflected in their next annual fees payment.

Working Group Annual Participation Fees Schedule A

The following fees have been established by the Eclipse Dataspace Steering Committee. These fees are in addition to each participant's membership fees in the Eclipse Foundation.

Eclipse Dataspace Strategic Member Annual Participation Fees

Strategic members are required to execute the Eclipse Dataspace Working Group Participation Agreement.

Strategic members are required to commit to three (3) years membership.

Member Organizations Annual Fees
Commercial €50 000
Academic, Non-profit, Public Sector €15 000

Eclipse Dataspace Participant Member Annual Participation Fees

Participant members are required to execute the Eclipse Dataspace Working Group Participation Agreement.

Member Organizations Annual Fees
Commercial €20 000
Academic, Non-profit, Public Sector €10 000

Eclipse Dataspace Committer Member Annual Participation Fees

Committer members pay no annual fees, but are required to execute the Eclipse Dataspace Working Group Participation Agreement.

Eclipse Dataspace Supporter Member Annual Participation Fees

Supporter members are required to execute the Eclipse Dataspace Working Group Participation Agreement.

Member Organizations Annual Fees
Commercial €5 000
Academic, Non-profit, Public Sector €1 000

Eclipse Dataspace Guest Member Annual Participation Fees

Guest members pay no annual fees, but are required to execute the Eclipse Dataspace Working Group Participation Agreement.

Charter Version History

  • v0.1 created March 30th, 2023
  • v0.2 created May 8th, 2023
  • Prefinal created July 12th, 2023
  • Draft v0.3 created July 17th, 2023 - Eclipse Foundation Review
  • v1.0 created November 3rd, 2023 - approved by Steering Committee

Back to the top