<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
Hi Kostas,
<div><br>
</div>
<div>Well, ChatGPT is certainly a more useful answer than the google AI equivalent….</div>
<div><br>
</div>
<div>David<br id="lineBreakAtBeginningOfMessage">
<div><br>
<blockquote type="cite">
<div>On Sep 26, 2025, at 10:08 AM, Orginos, Konstantinos via Hadstruct <hadstruct@jlab.org> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<article class="text-token-text-primary w-full focus:outline-none scroll-mt-[calc(var(--header-height)+min(200px,max(70px,20svh)))]" tabindex="-1" dir="auto" data-turn-id="903e4210-7e05-4392-89a0-975cc267b7d6" data-testid="conversation-turn-2" data-scroll-anchor="true" data-turn="assistant">
<div class="text-base my-auto mx-auto pb-10 [--thread-content-margin:--spacing(4)] thread-sm:[--thread-content-margin:--spacing(6)] thread-lg:[--thread-content-margin:--spacing(16)] px-(--thread-content-margin)">
<div class="[--thread-content-max-width:40rem] thread-lg:[--thread-content-max-width:48rem] mx-auto max-w-(--thread-content-max-width) flex-1 group/turn-messages focus-visible:outline-hidden relative flex w-full min-w-0 flex-col agent-turn" tabindex="-1">
<div class="flex max-w-full flex-col grow">
<div data-message-author-role="assistant" data-message-id="5e34e1b0-e3a2-4d71-b3c1-ae2390850d7e" dir="auto" class="min-h-8 text-message relative flex w-full flex-col items-end gap-2 text-start break-words whitespace-normal [.text-message+&]:mt-5" data-message-model-slug="gpt-5">
<div class="flex w-full flex-col gap-1 empty:hidden first:pt-[3px]">
<div class="markdown prose dark:prose-invert w-full break-words light markdown-new-styling">
<p data-start="0" data-end="126">Great question — you’ve spotted something that shows up often in <em data-start="65" data-end="84">technical reports</em> but almost never in <em data-start="105" data-end="123">journal articles</em>.</p>
<p data-start="128" data-end="367">That disclaimer is a <strong data-start="149" data-end="201">U.S. Department of Energy (DOE)–style disclaimer</strong>. It originated in DOE and other federal agency technical report templates, not as a general requirement
for all federally funded research. Here’s the key background:</p>
<ul data-start="369" data-end="1604">
<li data-start="369" data-end="745">
<p data-start="371" data-end="745"><strong data-start="371" data-end="389">Why it exists:</strong><br data-start="389" data-end="392">
Agencies like DOE (and historically the Atomic Energy Commission, then ERDA) publish thousands of technical reports through the Office of Scientific and Technical Information (OSTI). Because the government sponsors the work but doesn’t want legal liability
for errors or implied endorsements, the disclaimer was standardized in DOE report templates.</p>
</li><li data-start="747" data-end="1180">
<p data-start="749" data-end="1180"><strong data-start="749" data-end="770">Where it appears:</strong><br data-start="770" data-end="773">
It’s typically required in <strong data-start="802" data-end="915">contractor technical reports, lab reports, and other formal deliverables submitted directly to the government</strong>.<br data-start="916" data-end="919">
It does <strong data-start="929" data-end="936">not</strong> apply to peer-reviewed journal articles, conference papers, or other publications, even if the research was federally funded. Journals have their own publisher disclaimers, and agencies don’t usually
mandate inserting this boilerplate there.</p>
</li><li data-start="1182" data-end="1604">
<p data-start="1184" data-end="1604"><strong data-start="1184" data-end="1212">When it became standard:</strong><br data-start="1212" data-end="1215">
The language traces back at least to the <strong data-start="1258" data-end="1267">1970s</strong>, when DOE succeeded the Atomic Energy Commission (1974). DOE’s <strong data-start="1331" data-end="1446">Order 241.1 (Scientific and Technical Information Management,
first issued in the late 1990s and updated since)</strong> explicitly requires that technical reports include the disclaimer. Variants of this wording have been in DOE and NASA report templates since the 1970s–80s.</p>
</li></ul>
<p data-start="1606" data-end="1625">So to your point:</p>
<ul data-start="1626" data-end="1876">
<li data-start="1626" data-end="1758">
<p data-start="1628" data-end="1758">If you’re reading <em data-start="1646" data-end="1662">journal papers</em> funded by DOE, NSF, NIH, etc., you won’t see that disclaimer — only a funding acknowledgment.</p>
</li><li data-start="1759" data-end="1876">
<p data-start="1761" data-end="1876">If you look at <em data-start="1776" data-end="1799">DOE technical reports</em> (on OSTI.gov, for example), you’ll see that exact block almost every time.</p>
</li></ul>
<p data-start="1878" data-end="2101">👉 In short: <strong data-start="1891" data-end="1960">It’s not a blanket requirement for all federally funded research.</strong> It’s a legal protection clause required on U.S. government technical reports (especially DOE/OSTI
deliverables), dating back to the 1970s.</p>
<p data-start="2103" data-end="2258" data-is-last-node="" data-is-only-node="">Would you like me to show you a couple of concrete DOE reports (with dates) where this disclaimer appears, so you can see when and how it was standardized?</p>
<p data-start="2103" data-end="2258" data-is-last-node="" data-is-only-node=""><br>
</p>
</div>
</div>
</div>
</div>
<div class="z-0 flex min-h-[46px] justify-start"></div>
<div class="mt-3 w-full empty:hidden"></div>
</div>
</div>
</article></div>
_______________________________________________<br>
Hadstruct mailing list<br>
Hadstruct@jlab.org<br>
https://mailman.jlab.org/mailman/listinfo/hadstruct<br>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>