https://korea-wg.openchainproject.org/en/tags/duration/Recent content in Duration on OpenChain KWGHugoenhttps://korea-wg.openchainproject.org/en/guide/iso5230_guide/6-conformance/2-duration/Mon, 01 Jan 0001 00:00:00 +0000https://korea-wg.openchainproject.org/en/guide/iso5230_guide/6-conformance/2-duration/<h2 id="1-clause-overview">1. Clause Overview</h2> <p>ISO/IEC 5230 conformance does not remain valid indefinitely once obtained. When a new version of the specification is published, a program that was conformant against the previous version retains its conformance for only 18 months after the new version is published. §3.6.2 requires organizations to maintain a document confirming that the program meets all requirements of the specification within the past 18 months of obtaining conformance. This clause serves as a mechanism to ensure that open source compliance programs remain continuously operational rather than stopping at formal certification.</p>https://korea-wg.openchainproject.org/en/guide/iso18974_guide/4-conformance/2-duration/Mon, 01 Jan 0001 00:00:00 +0000https://korea-wg.openchainproject.org/en/guide/iso18974_guide/4-conformance/2-duration/<h2 id="1-clause-overview">1. Clause Overview</h2> <p>§4.4.2 has the same structure as ISO/IEC 5230 §3.6.2 (Duration). It requires organizations to maintain a retrospective document confirming that all requirements of the specification <strong>have been met during the past 18 months</strong> of obtaining conformance (this is a past-fact confirmation, not a future commitment). When a new version of the specification is published, conformance under the previous version is maintained for a grace period of 18 months, during which it is recommended to update to the latest version.</p>