Comments (7)
VF to discuss and propose.
from w3process.
It seems that the confusion in this section may be coming from the assumption that "MOU" has a certain legal meaning when it does not. Please see attached for alternate proposed language that should address this issue.
W3C_MOU_060217.docx
from w3process.
I think VF's document contains this:
Hello all
Request:
- provide a definition for our use of the term "Memorandum of Understanding (MoU)" in the Liaisons section.
https://www.w3.org/2015/Process-20150901/#Liaisons
Rationales:
- the Team is often asked to sign "MoUs" with other organizations
that are just simple liaisons from our point of view, that is, they do
not justify Member review, but because the other parties call them
"MoU", and insist on doing so, we are often in an unclear situation (is
it a "real" MoU ? should we inform our members ?).
- MoU is as good as any other similar name like "Agreement" or
"Partnership", "Formal liaison", so we only need to provide details for
our own meaning of the term, and need not to change it.
Proposed modification:
- no change to the text using the term MoU, only make the term a link
to a new definition entry, that can be added elsewhere [It needs to be added to this section.]
- Suggested new definition:
"In the context of the W3C Process, an MoU is a formal agreement,
i.e. a contractual framework with W3C rights and obligations, that
involves joint deliverables, an agreed share of technical
responsibilities with due coordination, and/or considerations for
confidentiality and specific IPR. The agreement may actually be called
something else that an MoU, and something called an MoU may not be a W3C
MoU in that sense.
9 Liaisons
W3C uses the term "liaison" to refer to coordination of activities with a variety of organizations, through a number of mechanisms ranging from very informal (e.g., an individual from another organization participates in a W3C Working Group, or just follows its work) to mutual membership, to even more formal agreements. Liaisons are not meant to substitute for W3C membership.
All liaisons must be coordinated by the Team due to requirements for public communication; patent, copyright, and other IPR policies; confidentiality agreements; and mutual membership agreements.
The W3C Director may negotiate and sign a Liaison Agreement with another organization. For purposes of this section, a “Liaison Agreement” is a formal written and binding agreement signed by W3C and another party to establish terms such as the framework of a liaison, the parties’ rights and obligations, ownership of deliverables, intellectual property rights, and confidentiality. A Liaison Agreement may have a different name, such as a Memorandum of Understanding (MOU), a Letter of Intent (LOI), or another type of document or agreement, while still qualifying as a Liaison Agreement under this section. Before signing the Liaison Agreement, the Team must inform the Advisory Committee of the intent to sign and make the Liaison Agreement available for Advisory Committee review; Advisory Committee representatives may initiate an Advisory Committee Appeal of the decision to sign the Liaison Agreement. Once approved, a Liaison Agreement should be made public.
The Team may inform the Advisory Committee of the intent to sign non-binding MOUs or LOIs.
Information about W3C liaisons with other organizations and the guidelines W3C follows when creating a liaison [PUB28] is available on the Web.
from w3process.
I agree to clarify what an MoU is in the process document, using the definition above. We're not sure we need to have a long paragraph about liaisons as well?
from w3process.
In the context of the W3C Process, an MoU is a formal agreement,
i.e. a contractual framework with W3C rights and obligations, that
involves joint deliverables, an agreed share of technical
responsibilities with due coordination, and/or considerations for
confidentiality and specific IPR. The agreement may actually be called
something else that an MoU, and something called an MoU may not be a W3C
MoU in that sense.
from w3process.
from w3process.
I don't know why the language about Liaisons is there. This Is my proposed language:
"The W3C Director may negotiate a Memorandum of Understanding with another organization. For the purposes of the W3C Process a "Memorandum of Understanding" ("MoU") is a formal agreement or similar contractual framework between W3C and another party or parties (other than agreements between the hosts or between hosts and W3C members for the purposes of membership and agreements related to the ordinary provision of services for the purposes of running W3C), that specifies rights and obligations of each party toward the others. These rights and obligations may include joint deliverables, an agreed share of technical responsibilities with due coordination, and/or considerations for confidentiality and specific IPR. The agreement may be called something other than a "Memorandum of Understanding," and something called a "Memorandum of Understanding" may not be an MoU for the purposes of the Process.
from w3process.
Related Issues (20)
- Ground the different types of groups / maturity stages in Problem Statements HOT 4
- Strip section 6.2.2.1 “wide review” of the mailing list currently mentioned HOT 1
- Affiliation constraints on TAG membership HOT 17
- Chair should be required in charter HOT 38
- Run link checker on Process Drafts HOT 3
- Determining AC Consensus of Post-Review Changes HOT 8
- Description of the role of the AB HOT 9
- TAG appointment ambiguity about ratification by both AB and TAG HOT 14
- Ambiguity about (super) majority thresholds: of those voting, or of those eligible to vote? HOT 8
- Dealing with procedural disagreements within the Council
- Multiple possible outcomes of a successful AC Appeal HOT 2
- Align with Bylaws changes
- Making the Council's short circuit a little more flexible HOT 9
- Member Associations to Liaison Relationships HOT 2
- Creating a more visible banner for old process documents HOT 2
- Retire the "Streamlined Publication Approval" system HOT 3
- Proposed Recommendations aren't useful in the same way other maturity stages are HOT 5
- Switching tracks **and back** HOT 5
- Enhancing the W3C REC Update Process for Greater Efficiency and Engagement HOT 1
- FPWD and joint deliverables—the process may be missing an exclusion opportunity HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from w3process.