<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Resources on OpenChain KWG</title><link>https://korea-wg.openchainproject.org/en/tags/resources/</link><description>Recent content in Resources on OpenChain KWG</description><generator>Hugo</generator><language>en</language><atom:link href="https://korea-wg.openchainproject.org/en/tags/resources/index.xml" rel="self" type="application/rss+xml"/><item><title>§3.2.2 Effective Resources</title><link>https://korea-wg.openchainproject.org/en/guide/iso5230_guide/2-relevant-tasks/2-resourced/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/guide/iso5230_guide/2-relevant-tasks/2-resourced/</guid><description>&lt;h2 id="1-clause-overview"&gt;1. Clause Overview&lt;/h2&gt;&#10;&lt;p&gt;For an open source program to actually function, it is not enough to just define roles. Actual personnel&#10;must be assigned to each role, and sufficient time and budget must be provided to carry out the work.&#10;§3.2.2 requires organizations to document the persons responsible for each program role, confirm that&#10;staffing and budget are appropriately allocated, and to have a method for accessing legal expertise, a&#10;procedure for assigning internal responsibilities, and a procedure for handling non-compliance cases.&#10;This clause consists of five verification material items and is the stage that implements the role&#10;structure defined in §3.1 Program Foundation into an actual operational framework.&lt;/p&gt;</description></item><item><title>§4.2.2 Effectively Resourced</title><link>https://korea-wg.openchainproject.org/en/guide/iso18974_guide/2-relevant-tasks/2-resourced/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/guide/iso18974_guide/2-relevant-tasks/2-resourced/</guid><description>&lt;div class="alert alert-warning" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;★ 18974 Exclusive Items — Documented Evidence Strength&lt;/div&gt;&#10;&lt;p&gt;§4.2.2.3 is an ISO 18974 exclusive (★) item requiring &lt;strong&gt;Documented Evidence&lt;/strong&gt;. The method for accessing vulnerability resolution resources is not merely a procedure document — you must retain actual resource utilization records (security advisory contracts, account issuance records, access logs). For a detailed explanation of the strength difference, see &lt;a href="https://korea-wg.openchainproject.org/en/guide/iso18974_guide/1-program-foundation/5-standard-practice/#evidence-strength-for-iso-18974-exclusive--items--documented-evidence"&gt;§4.1.5 Standard Practices — Documented Evidence Notice&lt;/a&gt;.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;h2 id="1-clause-overview"&gt;1. Clause Overview&lt;/h2&gt;&#10;&lt;p&gt;§4.2.2 corresponds to ISO/IEC 5230 §3.2.2 (Effectively Resourced) but has two key differences. First, while 5230 requires 5 Verification Materials, 18974 requires 4. The §3.2.2.5 item from 5230 (procedure for reviewing and correcting non-compliance cases) is absorbed into §4.1.5 Standard Practice Implementation in 18974. Second, §3.2.2.3 (method for accessing legal expertise) is replaced in §4.2.2.3 by &lt;strong&gt;vulnerability resolution expertise&lt;/strong&gt;. Rather than legal expertise for license matters, the organization must secure technical and security expertise capable of actually resolving known vulnerabilities and document how that expertise is accessed.&lt;/p&gt;</description></item></channel></rss>