|
ISO 56005:2020
https://www.iso.org/obp/ui#iso:std:iso:56005:ed-1:v1:en (also in French) ISO 56005:2020(en) Innovation management — Tools and methods for intellectual property management — Guidance
https://www.iso.org/obp/ui#iso:std:iso:56005:ed-1:v1:en (also in French) ISO 56005:2020(en) Innovation management — Tools and methods for intellectual property management — Guidance
|
By
Jim Hutchison
· #3673
·
|
|
Siemens unified tooling
Hi, Siemens tooling sounds very exciting, good tools are a boon to moving forward quickly! Considering “relevant” use cases is such a great opportunity to benefit from embracing the diverse use cases
Hi, Siemens tooling sounds very exciting, good tools are a boon to moving forward quickly! Considering “relevant” use cases is such a great opportunity to benefit from embracing the diverse use cases
|
By
Jim Hutchison
· #2294
·
|
|
The OpenChain Open Source Policy Template - Release Candidate 1
Hi, The example policy, page 2, F2, suggests a license interpretation as to what all Open Source licenses permit. For instance, there are licenses which indicate “no derivatives”, or requesting limits
Hi, The example policy, page 2, F2, suggests a license interpretation as to what all Open Source licenses permit. For instance, there are licenses which indicate “no derivatives”, or requesting limits
|
By
Jim Hutchison
· #1957
·
|
|
Compliance Office and Liaison Office
The notion that these roles are "extra" work/cost, is something where the initial goal would shape our choices to make the results more efficient than without OpenChain-like actions. You will get the
The notion that these roles are "extra" work/cost, is something where the initial goal would shape our choices to make the results more efficient than without OpenChain-like actions. You will get the
|
By
Jim Hutchison
· #1142
·
|
|
Compliance Office and Liaison Office
In previous reads, I enjoyed a simple view of a Liaison as public-facing and the definition in 1.1 seems pretty good for that usage * FOSS Liaison - a designated person who is assigned to receive exte
In previous reads, I enjoyed a simple view of a Liaison as public-facing and the definition in 1.1 seems pretty good for that usage * FOSS Liaison - a designated person who is assigned to receive exte
|
By
Jim Hutchison
· #1140
·
|
|
Olá! The OpenChain Specification 1.1 is in Portuguese
Congratulations on this significant achievement Bill and Gianna! I look forward to the expanded circulation to more folks reading the OpenChain specification, leading to benefit for themselves and the
Congratulations on this significant achievement Bill and Gianna! I look forward to the expanded circulation to more folks reading the OpenChain specification, leading to benefit for themselves and the
|
By
Jim Hutchison
· #936
·
|
|
OpenChain for projects
Hi, Looking back, this raises an interesting point: How can properly identified "un-known compliance" software be distributed down-chain? Clearly distributing out-of-governance would be undesirable, b
Hi, Looking back, this raises an interesting point: How can properly identified "un-known compliance" software be distributed down-chain? Clearly distributing out-of-governance would be undesirable, b
|
By
Jim Hutchison
· #600
·
|
|
Conformance - privacy subcommittee meeting
Hi, Considering Privacy, many principalities (EU, Brazil, USA, etc.) have described Privacy to involve PII (Personally Identifiable Information). OpenChain may be collecting PII, for some interpretati
Hi, Considering Privacy, many principalities (EU, Brazil, USA, etc.) have described Privacy to involve PII (Personally Identifiable Information). OpenChain may be collecting PII, for some interpretati
|
By
Jim Hutchison
· #540
·
|
|
Updates on the OpenChain certification website
Hi Gary, For the CSV upload does the CSV include the questions, or just answers? If solely answers, we’ll need a date/version for the questionnaire used. If also questions, there is perhaps a temptati
Hi Gary, For the CSV upload does the CSV include the questions, or just answers? If solely answers, we’ll need a date/version for the questionnaire used. If also questions, there is perhaps a temptati
|
By
Jim Hutchison
· #474
·
|
|
OSADL demo for consideration of certification prototype -- OpenChain agenda 12/7
Hi Michel, These are helpful observations, as we are looking for a solution folks would want to use productively. In considering OpenChain, we should be able to steer clear of contract/agreement terms
Hi Michel, These are helpful observations, as we are looking for a solution folks would want to use productively. In considering OpenChain, we should be able to steer clear of contract/agreement terms
|
By
Jim Hutchison
· #241
·
|
|
OpenChain spec v0.1
That sounds like a great idea. It will help set the tone/context for the document. Regards, Jim
That sounds like a great idea. It will help set the tone/context for the document. Regards, Jim
|
By
Jim Hutchison
· #216
·
|
|
OpenChain
Hello Michel, Do you find that there could be value in attestation/certification by a part of group, which is the only part working on the released software headed up/down the chain? Regards, Jim Hutc
Hello Michel, Do you find that there could be value in attestation/certification by a part of group, which is the only part working on the released software headed up/down the chain? Regards, Jim Hutc
|
By
Jim Hutchison
· #209
·
|
|
OpenChain
[hutch] To the extent that the application of OpenChain results in a collection of indications of how OpenChain is applied to a participant in a supply chain, these indications (artifacts of certifica
[hutch] To the extent that the application of OpenChain results in a collection of indications of how OpenChain is applied to a participant in a supply chain, these indications (artifacts of certifica
|
By
Jim Hutchison
· #198
·
|