Re: PM-KR Mission Updated — Procedural vs Declarative, Context Handling, Concrete Applications

Dear Milton and PM-KR Community,

Thank you, Milton, for the **critical mathematical insight** from your 
mandala graph theory work. You've identified exactly the right framing:

**Not:** "Procedural INSTEAD of declarative"
**But:** "**Procedural optimization GIVEN declarative foundation**"

I've immediately revised our mission statement to reflect this synergy.

## Mission Statement Changes (v1.1 → v1.2)

**Updated Mission:** 
https://www.w3.org/community/pm-kr/procedural-memory-knowledge-representation-pm-kr-community-group/

**Key changes:**

1. **Section renamed:** "The Declarative Dilemma" → **"The Declarative 
Foundation + Procedural Execution Synergy"**

2. **Opening statement added:**
    > "Nothing is 'wrong' with declarative approaches — they're 
**necessary but insufficient**. PM-KR provides **procedural optimization 
given declarative foundation** (insight from PM-KR Co-Chair Milton 
Ponson's mandala graph theory)."

3. **Comparison table enhanced** with new row showing **"Declarative + 
PM-KR"** as complete system (declarative foundation + procedural 
execution layer)

4. **Positioning clarified:**
    > "We're not replacing RDF/OWL/JSON-LD — we're **adding the 
execution layer** that makes them **runnable, renderable, and 
multi-modal**."

**Your quote from Gemini is now prominently featured:**
 > "In practice, complex AI systems often combine both. **Declarative 
knowledge forms the foundational understanding of the environment, while 
procedural knowledge provides the methods to act upon that environment**."

This strengthens our response to Dave — PM-KR builds ON semantic web 
foundations, not against them.

## Addressing Your Suggestions

### 1. **Wiki Page for Cross-Posting Between Community Groups**

**Agreed.** I'll create a GitHub-based PM-KR Community Wiki with:
- Cross-posting tracking (AIKR-CG, VC-WG, JSON-LD-WG)
- Weekly summaries
- Literature/prior art references

**Action:** Wiki structure created this week, link posted to mailing list.

### 2. **Weekly Summary Reports**

**Format:** Condensed summaries (no AI verbosity), structured as:
- Key Developments
- New Members
- Literature/Prior Art
- Cross-CG Discussions
- Technical Questions Raised
- Action Items

**Action:** First weekly summary (2026-W09: Feb 24-28) published Monday, 
March 3.

### 3. **Blurred Declarative/Procedural Distinction (Human Brain Model)**

**Your insight:** Mathematicians and computer scientists use different 
languages for the same underlying reality. Mandala graph theory 
addresses both simultaneously because the distinction is artificial.

**PM-KR reflection:** Like human brain (declarative memory + procedural 
memory blend seamlessly), PM-KR unifies declarative semantics (JSON-LD) 
+ procedural execution (RPN) in ONE representation.

**The "blurred distinction" is a feature, not a bug.**

## HP Calculator and "Dead Brain Mode" Analogy

Milton mentioned Daniel's HP calculator analogy. My interpretation:

**HP calculators use RPN (Reverse Polish Notation):**
- Procedural execution model (stack-based)
- "Dead brain mode": Execute complex calculations mechanically 
(following procedure)
- **Key insight:** The RPN program IS the semantics (procedure = meaning)

**PM-KR parallel:**
- Declarative layer: Semantics (what "∫" means in different contexts)
- Procedural layer (RPN): Execution (how to compute)
- **Blurred distinction:** The RPN program IS the declarative meaning

## Updated Positioning vs Dave Raggett's Feedback

**Dave's question:** "What's wrong with a declarative approach?"

**Previous framing risk:** Sounded like we're dismissing semantic web 
legacy.

**New framing (thanks to Milton):**
- Declarative approaches are **necessary** (provide semantic foundation)
- PM-KR **complements** them (adds execution layer)
- Together = complete system (declarative foundation + procedural execution)

**This also addresses Dave's PKN reference:** PM-KR does something 
similar — declarative semantics (RDF/JSON-LD) + procedural execution 
(RPN programs) + metadata (Verifiable Credentials).

## Week 1 Lesson (Revised)

**Not:** "Procedural vs declarative"
**But:** **"Declarative + procedural synergy"**

Mathematical perspective (Milton): The distinction between 
declarative/procedural is an artifact of how we describe the same 
underlying reality. Mandala graph theory addresses both simultaneously 
because the distinction is conceptual, not fundamental.

**PM-KR's mission:** Make that artificial distinction disappear in 
practice — ONE unified representation serving both needs.

Thank you, Milton, for the mathematical clarity. 🙏

Best regards,

**Daniel Campos Ramos**
PM-KR Co-Chair
Brazilian Registered Electrical Engineer
W3C PM-KR Community Group
capitain_jack@yahoo.com

**Milton Ponson**
PM-KR Co-Chair (Mathematical Foundations)
Rainbow Warriors Core Foundation
CIAMSD Institute-ICT4D Program
rwiciamsd@gmail.com

**P.S. Action Items:**
1. ✅ Mission statement updated (v1.2): 
https://www.w3.org/community/pm-kr/procedural-memory-knowledge-representation-pm-kr-community-group/
2. 🔄 GitHub Wiki for cross-posting: This week
3. 🔄 Weekly summary (2026-W09): Monday, March 3

**Links:**
- Updated Mission (v1.2): 
https://www.w3.org/community/pm-kr/procedural-memory-knowledge-representation-pm-kr-community-group/
- Milton's Gemini analysis: https://share.google/aimode/pL2tANlD6ee0Cp2uz
- GitHub Specs: 
https://github.com/danielcamposramos/Knowledge3D/tree/main/docs/vocabulary
- Mailing List: public-pm-kr@w3.org

On 2/28/26 9:51 AM, Milton Ponson wrote:
> In the AIKR CG I repeatedly mentioned being personally busy fleshing 
> out mandala graph theory. What I actually did not mention is that it 
> addresses both declarative and procedural approaches.
>
> I now realize that mathematicians and computer scientists when 
> addressing foundational principles of artificial intelligence tend to 
> speak slightly different languages, and consequently I did not even 
> use the computer speak terms declarative and procedural in my notes.
>
> So I checked if I maybe right after all and this is what I found:
> what is the difference and what are the key benefits of the 
> declarative and procedural approach in knowledge representation for 
> artificial intelligence
>
> https://share.google/aimode/pL2tANlD6ee0Cp2uz
>
> It seems I have been addressing doing both at the same time 
> mathematically,  so maybe we should rephrase the mission statement to 
> reflect the fact that we are trying to optimize the procedural 
> approach, given the appropriate declarative approach as a starting 
> point. This also resonates with the HP calculator and *dead brain 
> mode* analogy given by Daniel.
> And it would the also reflect the way the human brain works where the 
> distinction between the two is blurred as I also mentioned in a post 
> in another Community Group.
> Sometimes I wonder if a Wiki page combining elements, findings, 
> discussions of multiple Community Groups could help. We are already 
> cross-posting all the time.
> Would be an excellent idea for the PM-KR community group.
>
> As a mathematician I would also like to point out the usefulness of 
> creating weekly summary reports of reviews of new literature of 
> interest, points brought up in posts, and links to work in other 
> community groups, based on interaction and reflections triggered by 
> cross-posts.
> And these in terms could be cross-posted.
> And these should be written in a condensed summary form, without all 
> the verbal add-ons that AI chatbots typically generate.
>
> Milton Ponson
> Rainbow Warriors Core Foundation
> CIAMSD Institute-ICT4D Program
> +2977459312
> PO Box 1154, Oranjestad
> Aruba, Dutch Caribbean
>
> On Sat, Feb 28, 2026, 08:04 Daniel Ramos <capitain_jack@yahoo.com> wrote:
>
>     Dear PM-KR Community,
>
>     Following feedback from W3C veteran **Dave Raggett** (dsr@w3.org),
>     I've significantly revised the PM-KR Community Group mission
>     statement to address critical questions about our approach.
>
>     **Updated Mission:**
>     https://www.w3.org/community/pm-kr/procedural-memory-knowledge-representation-pm-kr-community-group/
>
>     ## What Changed (Summary)
>
>     ### 1. **Why Procedural Over Declarative?** (New Section)
>
>     **Dave's question:** "What's wrong with a declarative approach?"
>
>     We've added a detailed comparison showing:
>
>     | **Approach** | **Execution** | **Transparency** |
>     **Composability** | **Context Handling** |
>     |--------------|---------------|------------------|-------------------|----------------------|
>     | **Declarative (RDF/OWL)** | ❌ No (describes, doesn't execute) |
>     ✅ Transparent | ⚠️ Limited (static relationships) | ⚠️ Manual
>     modeling |
>     | **Neural Networks** | ✅ Yes (procedural) | ❌ Opaque (black box)
>     | ❌ No (monolithic) | ✅ Learned (but unexplainable) |
>     | **PM-KR** | **✅ Yes (procedural)** | **✅ Transparent** | **✅ Yes
>     (compositional)** | **✅ Explicit context rules** |
>
>     **Key insight:** PM-KR combines **transparency of declarative
>     systems** with **executability of neural networks** while adding
>     **composability** that neither provides.
>
>     **Example:** Mathematical symbol "∫" (integral)
>     - **Declarative (RDF):** `rdfs:label "integral" ; math:relatedTo
>     :summation` ❌ Doesn't tell you HOW to compute or render
>     - **PM-KR:** Provides `visual_rpn` (glyph rendering),
>     `execution_rpn` (integration algorithm), `audio_rpn`
>     (pronunciation), context-specific rules ✅
>
>     **Positioning:** PM-KR is the **execution layer** that complements
>     declarative standards (RDF/OWL/JSON-LD), not replacing them.
>
>     ### 2. **Handling Context-Dependent Meanings** (New Section)
>
>     **Dave's question:** "What about subtly different meanings in
>     different contexts?"
>
>     **PM-KR's answer:** Explicit context rules (procedural programs)
>
>     **Example: "Chair" in Different Contexts**
>     - **Furniture catalog:** Photorealistic rendering + price metadata
>     - **Architectural BIM:** Collision mesh + load-bearing physics
>     - **Game environment:** Low-poly mesh + interaction rules
>     (sittable, throwable)
>     - **Accessibility:** Audio pronunciation + 3D-printable tactile mesh
>
>     **Result:**
>     - Same base knowledge (`chair = seat + back + legs`)
>     - Context-specific execution (inspectable procedural rules)
>     - Composable (contexts inherit/override base procedures)
>     - Transparent (not hidden in neural weights)
>
>     See revised mission for full JSON-LD example.
>
>     ### 3. **Concrete Applications** (New Section)
>
>     **Dave's recommendation:** "Explain PM-KR in respect to why it is
>     needed and what applications it targets."
>
>     **Added 5 detailed examples:**
>
>     1. **Education (MIT OpenCourseWare)**
>        - ONE procedural calculus textbook → AI tutors AND students
>     consume same source
>        - Impact: Accessibility (visual, audio, tactile), AI
>     integration, maintenance
>
>     2. **Gaming (D&D SRD)**
>        - Game rules as procedural programs → Human DMs read, AI DMs
>     execute (same source)
>        - Impact: Zero divergence, AI DM uses canonical rules (no
>     hallucination)
>
>     3. **Science (Nature Protocols)**
>        - Experimental protocols as procedural programs → Scientists
>     read, lab robots execute
>        - Impact: Reproducibility crisis addressed (protocol
>     description = execution)
>
>     4. **Accessibility (Multi-Modal Textbooks)**
>        - Visual equations, spoken descriptions, tactile 3D-printed
>     graphs (all from ONE source)
>        - Impact: Blind students access same knowledge as sighted (not
>     separate "accessible version")
>
>     5. **AI Training (Wikipedia Procedural KB)**
>        - Wikipedia as PM-KR source → AI queries during inference (no
>     training duplication)
>        - Impact: Carbon reduction (train once, reference forever)
>
>     Each example shows **why procedural execution is needed** (not
>     just declarative description) and **what problem it solves**.
>
>     ## Community Discussion Invited
>
>     **Questions for the group:**
>
>     1. **Declarative integration:** How should PM-KR's execution layer
>     integrate with existing RDF/OWL ontologies? Should we define
>     mapping rules?
>
>     2. **Context rule semantics:** Are the proposed context
>     inheritance/override rules sufficient? What edge cases are we missing?
>
>     3. **Application priorities:** Which of the 5 applications
>     (education, gaming, science, accessibility, AI training) should we
>     prioritize for early validation?
>
>     4. **Neural network comparison:** Is our positioning vs neural
>     networks (procedural + transparent vs procedural + opaque) clear?
>     How can we strengthen this distinction?
>
>     5. **PKN relationship:** Dave mentioned PKN (Procedural Knowledge
>     Networks) as combining declarative approaches with qualitative
>     metadata. Should we establish liaison with PKN researchers?
>
>     **Please share:**
>     - Critical feedback (what's unclear, what's wrong?)
>     - Additional use cases from your domain
>     - Alternative approaches we should consider
>     - Relevant prior art (papers, systems, standards)
>
>     ## Acknowledgment
>
>     Thank you, **Dave Raggett**, for the rigorous feedback. Your
>     questions transformed our mission statement from "here's what
>     we're doing" to "here's WHY procedural over declarative, HOW we
>     handle context, and WHAT applications need this."
>
>     This is exactly the rigor PM-KR needs to mature into a viable W3C
>     standard.
>
>     **To all members:** Please continue challenging our assumptions.
>     PM-KR's strength will come from community scrutiny and diverse
>     perspectives.
>
>     ## Current Status (Week 1 Complete)
>
>     **Momentum (Feb 20-28, 2026):**
>     - ✅ 18+ members (MIT, Huawei, JSON-LD co-creator Manu Sporny)
>     - ✅ Mission statement revised based on community feedback (v1.0 →
>     v1.1)
>     - ✅ Initial specification drafts in GitHub
>     - ✅ Reference implementation (Knowledge3D: Python/CUDA)
>     - ✅ Empirical validation (50-90% compression, dual-client contract
>     working)
>
>     **Next steps:**
>     - **Q2 2026:** PM-KR Core Specification v0.5 (draft for community
>     review)
>     - **Q3 2026:** W3C TPAC breakout session
>     - **Q4 2026:** PM-KR Core Specification v1.0
>
>     ## Resources
>
>     **Updated Mission Statement:**
>     -
>     https://www.w3.org/community/pm-kr/procedural-memory-knowledge-representation-pm-kr-community-group/
>
>     **GitHub Repository:**
>     - https://github.com/danielcamposramos/Knowledge3D
>     - Specifications: `/docs/vocabulary/`
>     - Reference implementation: `/knowledge3d/`
>
>     **Mailing List Archives:**
>     - https://lists.w3.org/Archives/Public/public-pm-kr/
>
>     **How to Contribute:**
>     - Join: https://www.w3.org/community/pm-kr/
>     - Participate: Review specs, propose use cases, implement prototypes
>     - Discuss: Email public-pm-kr@w3.org with feedback, questions, ideas
>
>     ## Closing Thoughts
>
>     PM-KR is a **community effort**. Our mission statement will
>     continue evolving based on your feedback, empirical validation,
>     and real-world use cases.
>
>     **Week 1 lesson:** Rigorous critique (like Dave's) makes PM-KR
>     stronger. Please keep challenging us.
>
>     **What PM-KR needs from you:**
>     - Critical feedback (technical, conceptual, strategic)
>     - Domain expertise (education, gaming, science, accessibility, AI)
>     - Implementation experience (prototypes, benchmarks, validations)
>     - Prior art pointers (papers, systems, standards we should know)
>
>     Let's build the future of knowledge representation together —
>     **transparently, collaboratively, rigorously**. 🚀
>
>     Best regards,
>
>     **Daniel Campos Ramos**
>     PM-KR Co-Chair
>     Brazilian Registered Electrical Engineer
>     W3C PM-KR Community Group
>     capitain_jack@yahoo.com
>
>     **Milton Ponson**
>     PM-KR Co-Chair (Mathematical Foundations)
>
>     **P.S.** If you haven't joined yet:
>     https://www.w3.org/community/pm-kr/
>
>     No W3C membership required — Community Groups are open to all.
>
>     **Links:**
>     - Updated Mission (v1.1):
>     https://www.w3.org/community/pm-kr/procedural-memory-knowledge-representation-pm-kr-community-group/
>     - GitHub Specs:
>     https://github.com/danielcamposramos/Knowledge3D/tree/main/docs/vocabulary
>     - Mailing List: public-pm-kr@w3.org
>     - NotebookLM Research Space:
>     https://notebooklm.google.com/notebook/1bd10bda-8900-4c41-931e-c9ec67ac865f
>
>
>
>

Received on Saturday, 28 February 2026 13:13:26 UTC