Recent changes to ieee11073-10207https://sourceforge.net/p/opensdc/ieee11073-10207/2026-04-01T08:21:38.688000ZRecent changes to ieee11073-10207#413 SafetyClassification responsibility2026-04-01T08:21:38.688000Z2026-04-01T08:21:38.688000ZLukas Deichmannhttps://sourceforge.net/u/ldeichmann/https://sourceforge.netd0e1e97fda8364e74279d2aff6d8eeba2256a0fd<div class="markdown_content"><ul>
<li>Description has changed:</li>
</ul>
<p>Diff:</p>
<div class="codehilite"><pre><span></span><code><span class="gd">--- old</span>
<span class="gi">+++ new</span>
<span class="gu">@@ -1,3 +1,3 @@</span>
<span class="w"> </span>We need to clarify what kind of responsibility and for whom is derived from SafetyClassification. For metrics and similar data, it is mostly a task for the provider, derived from the intended use of the data etc.
<span class="gd">-For operations, it is the other way round, where the safety classification is &#34;intended&#34; to require the consumer to behave in a manner a certain manner to &#34;fulfill&#34; the specified SafetyClassification. The provider is eseentially mostly setting a specific SafetyClassification based on the effect of the operation, e.g., whether serious harm can be caused by the consumer</span>
<span class="gi">+For operations, it is the other way round, where the safety classification is &#34;intended&#34; to require the consumer to behave in a manner a certain manner to &#34;fulfill&#34; the specified SafetyClassification. The provider is essentially mostly setting a specific SafetyClassification based on the effect of the operation, e.g., whether serious harm can be caused by the consumer</span>
</code></pre></div>
</div>SafetyClassification responsibility2026-04-01T08:21:27.378000Z2026-04-01T08:21:27.378000ZLukas Deichmannhttps://sourceforge.net/u/ldeichmann/https://sourceforge.net08c1ebe9c0bfdac365cdd5ff2c4ec018dfb962c4<div class="markdown_content"><p>We need to clarify what kind of responsibility and for whom is derived from SafetyClassification. For metrics and similar data, it is mostly a task for the provider, derived from the intended use of the data etc.</p>
<p>For operations, it is the other way round, where the safety classification is "intended" to require the consumer to behave in a manner a certain manner to "fulfill" the specified SafetyClassification. The provider is eseentially mostly setting a specific SafetyClassification based on the effect of the operation, e.g., whether serious harm can be caused by the consumer</p></div>SafetyClassification responsibility2026-04-01T08:21:27.378000Z2026-04-01T08:21:27.378000ZLukas Deichmannhttps://sourceforge.net/u/ldeichmann/https://sourceforge.netf8142b988e34c9e25cfb75fd1829710135a70952<div class="markdown_content"><p>Ticket 413 has been modified: SafetyClassification responsibility<br/>
Edited By: Lukas Deichmann (ldeichmann)<br/>
Description updated:<br/>
--- description-old</p>
<p>+++ description-new</p>
<p>@@ -1,3 +1,3 @@</p>
<p>We need to clarify what kind of responsibility and for whom is derived from SafetyClassification. For metrics and similar data, it is mostly a task for the provider, derived from the intended use of the data etc.</p>
<p>-For operations, it is the other way round, where the safety classification is "intended" to require the consumer to behave in a manner a certain manner to "fulfill" the specified SafetyClassification. The provider is eseentially mostly setting a specific SafetyClassification based on the effect of the operation, e.g., whether serious harm can be caused by the consumer<br/>
+For operations, it is the other way round, where the safety classification is "intended" to require the consumer to behave in a manner a certain manner to "fulfill" the specified SafetyClassification. The provider is essentially mostly setting a specific SafetyClassification based on the effect of the operation, e.g., whether serious harm can be caused by the consumer</p></div>#412 Table 14 Corrigendum incorrect names2026-03-02T09:56:57.817000Z2026-03-02T09:56:57.817000ZBjörn Andersenhttps://sourceforge.net/u/b-andersen/https://sourceforge.net1507d1c5e5442e8583a9d3e997a71670d12b0531<div class="markdown_content"><ul>
<li><strong>labels</strong>: Table 14 --> Table 14, not breaking backward compatibility</li>
<li><strong>status</strong>: unread --> accepted</li>
<li><strong>assigned_to</strong>: Lukas Deichmann</li>
<li><strong>Milestone</strong>: untriaged --> Revision</li>
</ul></div>#336 B.324 revise/remove PatientType2026-03-02T09:51:08.556000Z2026-03-02T09:51:08.556000ZBjörn Andersenhttps://sourceforge.net/u/b-andersen/https://sourceforge.net1fb6ba5565ea7fc34464a381c453f38fc85849fd<div class="markdown_content"><ul>
<li><strong>assigned_to</strong>: Björn Andersen</li>
</ul></div>#410 How to provide a display range2026-03-02T09:49:39.703000Z2026-03-02T09:49:39.703000ZBjörn Andersenhttps://sourceforge.net/u/b-andersen/https://sourceforge.netb8a7db0f2523e321d5f750b75b34dcfc732e805f<div class="markdown_content"><ul>
<li><strong>labels</strong>: --> not breaking backward compatibility</li>
<li><strong>status</strong>: unread --> open</li>
<li><strong>assigned_to</strong>: Björn Andersen</li>
<li><strong>Milestone</strong>: untriaged --> Revision</li>
</ul></div>#409 Supposed inconsistancy between SystemErrorReport/ReportPart/ErrorInfo and OperationInvokedReport/ReportPart/InfocationInfo/InvocationErrorMessage2026-03-02T09:46:55.032000Z2026-03-02T09:46:55.032000ZBjörn Andersenhttps://sourceforge.net/u/b-andersen/https://sourceforge.nete7b5b38dbfaeb1f2cea2efbc10f11ce084e81681<div class="markdown_content"><ul>
<li><strong>labels</strong>: --> C.111, SystemErrorReport, breaking CONSUMER backward compatibility</li>
<li><strong>status</strong>: unread --> open</li>
<li><strong>assigned_to</strong>: Lukas Deichmann</li>
<li><strong>Milestone</strong>: untriaged --> Revision</li>
</ul></div>#404 multiple invocation states within one report2026-03-02T09:33:05.873000Z2026-03-02T09:33:05.873000ZBjörn Andersenhttps://sourceforge.net/u/b-andersen/https://sourceforge.neta279906e5b95f2df3f693833e25a8cef7d589b28<div class="markdown_content"><ul>
<li><strong>labels</strong>: InvocationState --> InvocationState, breaking PROVIDER backward compatibility</li>
<li><strong>assigned_to</strong>: David</li>
</ul></div>#114 Add extension that allows to classify errors2026-03-02T09:31:31.333000Z2026-03-02T09:31:31.333000ZBjörn Andersenhttps://sourceforge.net/u/b-andersen/https://sourceforge.neta93508d1c74607d9882a2f6f5da62c55424cfc7a<div class="markdown_content"><ul>
<li><strong>labels</strong>: Extension, OperationInvokedReport --> Extension, OperationInvokedReport, not breaking backward compatibility</li>
</ul></div>#115 C.77 OperationInvokedReportPart and multi-state updates2026-03-02T09:29:56.222000Z2026-03-02T09:29:56.222000ZBjörn Andersenhttps://sourceforge.net/u/b-andersen/https://sourceforge.netdc8730196321b09911f967c58b00595be6e4f659<div class="markdown_content"><ul>
<li><strong>labels</strong>: C.77, C.96 --> C.77, C.96, breaking CONSUMER backward compatibility</li>
</ul></div>