Skip to content

Commit 32ab2bd

Browse files
committed
Create openchain-standards-model-provisions.0.1.md
Added first iteration of the model provisions document for discussion.
1 parent 43434e4 commit 32ab2bd

File tree

1 file changed

+80
-0
lines changed

1 file changed

+80
-0
lines changed
Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
# Overview
2+
3+
This is a document to explore model provisions for OpenChain ISO/IEC 5230 or ISO/IEC DIS 18974 in procurement contracts and similar material. It is based on the public domain Risk Grid version 12 hosted in the OpenChain Reference Library on GitHub:
4+
https://github.com/OpenChain-Project/Reference-Material/blob/master/General-Compliance-Support-Material/Risk-Grid/risk-grid-12.md
5+
6+
The goal of this document is to ensure people can understand options. We will not be prescriptive and these model provisions will remain part of the OpenChain reference material. They will not be included in the OpenChain standards themselves.
7+
8+
# Structure:
9+
10+
Each issue is formatted as follows:
11+
12+
- Issue
13+
- Commentary
14+
- Who is best placed to bear risk?
15+
- Best mechanism to tackle risk
16+
- Sample Wording
17+
- Supplier's Arguments
18+
- Customer's Arguments
19+
20+
# Overarching Topics
21+
22+
## Issue - Inclusion of OpenChain ISO/IEC 5230
23+
24+
### Commentary
25+
26+
None listed.
27+
28+
### Who is best placed to bear risk?
29+
30+
Supplier.
31+
32+
### Best mechanism to tackle risk
33+
34+
None listed.
35+
36+
### Sample Wording
37+
38+
The Supplier warrants that the Software originates from an OpenChain ISO/IEC 5230:2000 Conformant Program [under the control of the Supplier / under the control of a provider to the Supplier].
39+
40+
The Supplier [further] warrants that[, so far as it is aware,] the Software complies the Program Guidelines provided by OpenChain ISO/IEC 5230:2000 at the time of delivery.
41+
42+
[The Supplier does not warrant that use, modification or further distribution by the Customer of the Software constitutes a continuation of adherence to OpenChain ISO/IEC 5230:2000 Program Guidelines].
43+
44+
### Supplier's Arguments
45+
46+
The Supplier may argue that the inclusion of these requirements or the extent of the requirements included introduce a cost-burden that need to be offset.
47+
48+
### Customer's Arguments
49+
50+
The Customer is receiving a potential liability regarding third-party intellectual property along with the Software deliverable from the Supplier. As such, it is reasonable to request that the Supplier adheres to international standards related to the licensing of this third-party intellectual property.
51+
52+
## Issue - Inclusion of OpenChain ISO/IEC DIS 18974
53+
54+
### Commentary
55+
56+
None listed.
57+
58+
### Who is best placed to bear risk?
59+
60+
Supplier.
61+
62+
### Best mechanism to tackle risk
63+
64+
None listed.
65+
66+
### Sample Wording
67+
68+
The Supplier warrants that the Software originates from an OpenChain ISO/IEC DIS 18974 Conformant Program [under the control of the Supplier / under the control of a provider to the Supplier].
69+
70+
The Supplier [further] warrants that[, so far as it is aware,] the Software complies the Program Guidelines provided by OpenChain ISO/IEC DIS 18974 at the time of delivery.
71+
72+
[The Supplier does not warrant that use, modification or further distribution by the Customer of the Software constitutes a continuation of adherence to OpenChain ISO/IEC DIS 18974 Program Guidelines].
73+
74+
### Supplier's Arguments
75+
76+
The Supplier may argue that the inclusion of these requirements or the extent of the requirements included introduce a cost-burden that need to be offset.
77+
78+
### Customer's Arguments
79+
80+
The Customer is receiving a potential liability regarding security along with the Software deliverable from the Supplier. As such, it is reasonable to request that the Supplier adheres to international standards related to the managing of security assurance related to the Software.

0 commit comments

Comments
 (0)