<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Research on STEM to STEAM</title><link>https://adamfermier.github.io/madsciguys/categories/research/</link><description>Recent content in Research on STEM to STEAM</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 30 May 2026 09:53:57 -0400</lastBuildDate><atom:link href="https://adamfermier.github.io/madsciguys/categories/research/index.xml" rel="self" type="application/rss+xml"/><item><title>Scientific Method in Digital Age</title><link>https://adamfermier.github.io/madsciguys/docs/4-arts/pharma/scientific-method/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://adamfermier.github.io/madsciguys/docs/4-arts/pharma/scientific-method/</guid><description>&lt;h2 id="scientific-method-in-the-digital-age"&gt;Scientific Method in the Digital Age&lt;a class="td-heading-self-link" href="#scientific-method-in-the-digital-age"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The core principles of the scientific method—asking questions, forming hypotheses, designing experiments, collecting data, and sharing results—remain unchanged. However, in the digital era, how we document, analyze, and communicate our work must evolve to ensure research is transparent, reproducible, and collaborative.&lt;/p&gt;
&lt;p&gt;Inspired by &lt;a href="https://the-turing-way.org"&gt;The Turing Way&lt;/a&gt;, this section explores methodologies and best practices for reproducible research in pharmaceutical science. The Turing Way emphasizes that reproducibility is not just a technical challenge, but a cultural one, requiring open tools, clear documentation, and inclusive collaboration.&lt;/p&gt;</description></item><item><title>Knowledge Management: The Strategic Foundation of Research</title><link>https://adamfermier.github.io/madsciguys/docs/4-arts/knowledge-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://adamfermier.github.io/madsciguys/docs/4-arts/knowledge-management/</guid><description>&lt;p&gt;Knowledge Management is a key revenue source as it helps ensure you do not repeat what others may know and ensures you are spending the scarce resources you have in the most effective manner.&lt;/p&gt;
&lt;p&gt;It does NOT happen automatically. Organizations need to take deliberate action to manage what they know and organize it in a manner that others in the areas of research can find and quickly learn and add their knowledge to this structured approach.&lt;/p&gt;</description></item><item><title>From Trenches to Transformation: How Design Study Methodology Can Accelerate Knowledge Evolution in 2025</title><link>https://adamfermier.github.io/madsciguys/docs/4-arts/knowledge-management/design-study-methodology/</link><pubDate>Sun, 06 Jul 2025 00:00:00 +0000</pubDate><guid>https://adamfermier.github.io/madsciguys/docs/4-arts/knowledge-management/design-study-methodology/</guid><description>How the systematic approach to problem-driven research from Sedlmair, Meyer, and Munzner&amp;rsquo;s 2012 paper can be enhanced with AI, global collaboration, and adaptive frameworks to tackle 2025&amp;rsquo;s complex challenges.</description></item><item><title>Design Researcher</title><link>https://adamfermier.github.io/madsciguys/persona/design-researcher/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://adamfermier.github.io/madsciguys/persona/design-researcher/</guid><description>&lt;p&gt;A design researcher combines user insight, ethnography, and systems thinking to shape products and services that are meaningful and usable. This persona is key to connecting creative strategy with technical development and scientific discovery.&lt;/p&gt;
&lt;p&gt;In the STEAM knowledge graph, the design researcher operates primarily in the &lt;strong&gt;Arts&lt;/strong&gt; domain, but their methods — grounded in evidence and systematic reflection — connect back to &lt;strong&gt;Science&lt;/strong&gt; (empirical rigor), &lt;strong&gt;Mathematics&lt;/strong&gt; (measurement and analysis), and &lt;strong&gt;Technology&lt;/strong&gt; (interaction design).&lt;/p&gt;</description></item><item><title>Ontological Semantics</title><link>https://adamfermier.github.io/madsciguys/docs/4-arts/knowledge-management/ontological-semantics/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://adamfermier.github.io/madsciguys/docs/4-arts/knowledge-management/ontological-semantics/</guid><description>&lt;h2 id="architecture-of-ontological-semantics"&gt;Architecture of Ontological Semantics&lt;a class="td-heading-self-link" href="#architecture-of-ontological-semantics"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The key components required to build a knowledge framework leveraging Ontological Semantics — the theoretical grounding that has enabled the current field of Large Language Models — which help us create knowledge out of existing sources in a systematic manner.&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code class="language-plantuml" data-lang="plantuml"&gt;@startuml
!theme plain
skinparam defaultFontSize 13
skinparam component {
 BackgroundColor #EBF5FB
 BorderColor #2980B9
 FontColor #1A252F
 RoundCorner 10
}
skinparam database {
 BackgroundColor #FEF9E7
 BorderColor #F39C12
}
skinparam rectangle {
 BackgroundColor #EAFAF1
 BorderColor #27AE60
 RoundCorner 8
}
skinparam arrow {
 Color #2C3E50
 FontColor #555
 FontSize 11
}

title Architecture of Ontological Semantics

package &amp;#34;Static Knowledge Sources&amp;#34; {
 database &amp;#34;Ontology\n(World Model)&amp;#34; as ONT
 database &amp;#34;Fact Repository\n(Domain Facts)&amp;#34; as FACT
 database &amp;#34;Lexicon\n(Word Forms &amp;amp; Meanings)&amp;#34; as LEX
 database &amp;#34;Onomasticon\n(Named Entities)&amp;#34; as ONOM
}

component &amp;#34;Knowledge Representation\nLanguage&amp;#34; as KRL

rectangle &amp;#34;Semantic Analyzer\n(Large Language Model)&amp;#34; as LLM

rectangle &amp;#34;Use Cases&amp;#34; as UC {
 component &amp;#34;Text Summarization&amp;#34; as TS
 component &amp;#34;Question &amp;amp; Answering&amp;#34; as QA
 component &amp;#34;AI Agents&amp;#34; as AG
}

ONT --&amp;gt; KRL : &amp;#34;defines concepts&amp;#34;
FACT --&amp;gt; KRL : &amp;#34;instantiates&amp;#34;
LEX --&amp;gt; KRL : &amp;#34;maps words → meaning&amp;#34;
ONOM --&amp;gt; KRL : &amp;#34;resolves named entities&amp;#34;

KRL --&amp;gt; LLM : &amp;#34;structured meaning\nrepresentation&amp;#34;

LLM --&amp;gt; TS
LLM --&amp;gt; QA
LLM --&amp;gt; AG
@enduml
&lt;/code&gt;&lt;/pre&gt;&lt;hr&gt;
&lt;h2 id="the-four-static-knowledge-sources"&gt;The Four Static Knowledge Sources&lt;a class="td-heading-self-link" href="#the-four-static-knowledge-sources"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;h3 id="ontology--the-world-model"&gt;Ontology — the World Model&lt;a class="td-heading-self-link" href="#ontology--the-world-model"&gt;#&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;The ontology defines the concepts that exist in a domain and the relationships between them. It is the &lt;strong&gt;schema&lt;/strong&gt; of the knowledge graph: what nodes (concepts) and edge types (relationships) are valid. Without an ontology, a knowledge base is just a bag of facts with no shared meaning.&lt;/p&gt;</description></item></channel></rss>