HazardJ-Comment-WorldCCPrinciples-CmA
Greetings! Welcome to my little list of links regarding the WorldCC Contract Principles.

1. Principles and Clauses:
   OTF/WorldCC/ContractPrinciples-CmA/Principle/0.md
2. Clauses only, organized as some sections of an agreement:
   OTF/WorldCC/ContractPrinciples-CmA/Sec/0.md. Note that we organize the Clauses as "Sec," as with the vast majority of other CommonAccord sections.
3. Alternatives
   The Clauses reflect practices in contexts that vary greatly.
   1. This is an example from a Master Service Agreement (from GE Power). We have taken the list of provisions and show both the WorldCC Contract Principle and the corresponding MSA provisions: G/HazardJ-Comment-WorldCCPrinciples-CmA/MSA/0.md
   2. From the WorldCC resources - a form of Software License Agreement, posted under the number 9530:
      • IP Ownership:
        Ownership of Software.
        Developer agrees that the development of the Software is "work made for hire" within the meaning of the Copyright Act of 1976, as amended, and that the Software shall be the sole property of Buyer. Developer hereby assigns to Buyer, without further compensation, all of its right, title and interest in and to the Software and any and all related patents, patent applications, copyrights, copyright applications, trademarks and trade names in the United States and elsewhere. Developer will keep and maintain adequate and current written records with respect to the Software (in the form of notes, sketches, drawings and as may otherwise be specified by Buyer), which records shall be available to and remain the sole property of Buyer at all times. All versions of the Software shall contain Buyer's conspicuous notice of copyright. Developer will assist Buyer in obtaining and enforcing patent, copyright and other forms of legal protection for the Software in any country. Upon request, Developer will sign all applications, assignments, instruments and papers and perform all acts necessary or desired by Buyer to assign the Software fully and completely to Buyer and to enable Buyer, its successors, assigns and nominees, to secure and enjoy the full and exclusive benefits and advantages thereof.
      • Confidentiality (quasi-Data Protection):
        Confidentiality.
        
        1. Developer acknowledges that all material and information supplied by Buyer which has or will come into Developer's possession or knowledge of Developer in connection with its performance hereunder, is to be considered Buyer's confidential and proprietary information (the "Confidential Information"). By way of illustration, but not as a limitation, Confidential Information includes the Software, trade secrets, processes, data, knowhow, program codes, documentation, flowcharts, algorithms, marketing plans, forecasts, unpublished financial statements, budgets, licenses, prices, costs, and employee and customer lists. Developer's undertakings and obligations under this Section will not apply, however, to any Confidential Information which: (i) is or becomes generally known to the public through no action on Developer's part, (ii) is generally disclosed to third parties by Buyer without restriction on such third parties, or (iii) is approved for release by written authorization of Buyer. Upon termination of this Agreement or at any other time upon request, Developer will promptly deliver to Buyer all notes, memoranda, notebooks, drawings, records, reports, files, documented source codes and other documents (and all copies or reproductions of such materials) in its possession or under its control, whether prepared by Developer or others, which contain Confidential Information. Developer acknowledges that Confidential Information is the sole property of Buyer. Developer agrees that disclosure of such information to, or use by, third parties, either during or after this Agreement, will cause Buyer irreparable damage. Developer agrees to use best efforts to hold Confidential Information in the strictest confidence, not to make use of it other than for the performance of its obligations hereunder, to release it only to the Developer's employees or contractors with a need to know such information and not to release or disclose it to any other party. Developer further agrees not to release such information to any employee or contractor who has not signed a written agreement between Developer and the employee expressly binding the employee not to use or disclose the Confidential Information, except as expressly permitted herein. Buyer shall be listed as a third-party beneficiary of any such agreement. Developer will notify Buyer in writing of any circumstances within its knowledge relating to any unauthorized possession, use, or knowledge of such Confidential Information. At any time, upon request, the Developer will return any such information within its possession to Buyer.
        2. Developer acknowledges that Buyer's purpose in pursuing the development of the Software is to gain a significant competitive advantage over competitors operating without such Software and that such advantage will be jeopardized if such competitors learn of Buyer's negotiations with Developer or the performance by Developer of its obligations hereunder. Accordingly, Developer agrees to keep such negotiations and performance of its obligations hereunder strictly confidential and not to disclose any information to any third party or entity without the prior written permission of Buyer. In no event, shall Developer or any of its employees use Buyer as a reference in marketing Developer's services to any third party or entity without Buyer's prior written permission.
4. Particular Subject Matters
   
   1. Data Protection
      
      1. OTF/WorldCC/ContractPrinciples-CmA/Principle/DataSecurity/0.md The WorldCC "Contract Principle" regarding Data Security. Background and a recommended clause.
      2. The data protection provisions of a form of Master Services Agreement. Data must be protected along the chain of control. Here are some general provisions. These should be made consistent with the GDPR and should be compared with the WorldCC Principle. (It would be interesting to do a version that reflecte a privacy-preserving approach.) From a GE Power MSA: G/Agt-MasterService-CmA/Sec/PersonalData/0.md
      3. The terms for Kantara UMA: G/Kantara-UMA-Text-CmA/0.md
      4. The GDPR formatted as a prose object: OTF/EU-GDPR-Law-CmA/Form/0.md
      5. A "Privacy Policy" for Acme, done by refactoring the GDPR prose object. This is an example of a ProseChain. A ProseChain connects the "end-user" (aka citizen) via a company's terms to a broader legal community's view (e.g., model terms or legislation). It systematizes text "provenance": OTF/EU-GDPR-Law-CmA/Demo/Acme_UK.md