{"id":10,"date":"2026-06-19T20:03:24","date_gmt":"2026-06-19T20:03:24","guid":{"rendered":"https:\/\/www.w3.org\/community\/holon\/?p=10"},"modified":"2026-06-19T20:03:24","modified_gmt":"2026-06-19T20:03:24","slug":"after-the-inaugural-what-comes-next-for-the-holon-community-group","status":"publish","type":"post","link":"https:\/\/www.w3.org\/community\/holon\/2026\/06\/19\/after-the-inaugural-what-comes-next-for-the-holon-community-group\/","title":{"rendered":"After the Inaugural: What Comes Next for the Holon Community Group"},"content":{"rendered":"\n<p><em>Posted 19 June 2026 \u2014 Kurt Cagle, Acting Chair, W3C Holon Community Group<\/em><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<p>Thank you to everyone who joined us this morning for the inaugural meeting of the W3C Holon Community Group. Thirty-plus people showing up at 7am Pacific on a public holiday \u2014 and staying engaged for nearly two hours \u2014 is a strong signal that this work matters to a lot of people across a lot of domains. The conversation in the chat channel alone was remarkable: category theory, biomedical graphs, scene description formats, and active inference all appearing within the first half hour. This is the room we wanted.<\/p>\n\n\n\n<p>The meeting recording, presentation deck, agenda, and transcript are available at the community GitHub repository:<\/p>\n\n\n\n<p><a href=\"https:\/\/github.com\/w3c-cg\/holon\/tree\/main\/community\/meetings\/2026-06-19\" target=\"_blank\" rel=\"nofollow\">https:\/\/github.com\/w3c-cg\/holon\/tree\/main\/community\/meetings\/2026-06-19<\/a><\/p>\n\n\n\n<p>We encourage anyone who missed the session, or who wants to share it with colleagues, to link there directly.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">A Terminology Question: What Do We Call a Tracked Entity?<\/h2>\n\n\n\n<p>One thread that surfaced clearly during the meeting \u2014 in both the presentation and the chat \u2014 is that the term <strong>agent<\/strong> is badly overloaded and may not serve us well going forward.<\/p>\n\n\n\n<p>It carries at least three incompatible meanings in the communities this group spans: the classical AI \/ rational-agent sense; the AI tooling sense (autonomous LLM stacks, &#8220;agentic&#8221; pipelines); and domain-specific senses in biomedical contexts where an agent may be a protein, a peptide, a molecule, or a cell. Using the same word for a tracked entity inside a holon invites confusion from the start.<\/p>\n\n\n\n<p>Several alternatives were raised or suggested:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Participant<\/strong> \u2014 neutral, implies being part of a context, but perhaps too passive<\/li>\n\n\n\n<li><strong>Character<\/strong> \u2014 maps well to game, media, and narrative theory uses; a character has identity, state, and trajectory through a world. The concern raised is that it skews too strongly toward the entertainment domain.<\/li>\n\n\n\n<li><strong>Actor<\/strong> \u2014 has distributed systems baggage (the actor model) as well as theatrical connotations<\/li>\n\n\n\n<li><strong>Subject<\/strong> \u2014 perhaps the most promising candidate. In RDF, subject already occupies a precise structural role (the S in an SPO triple). In linguistics and philosophy, a subject is the entity around which predication and action organise. It scales from proteins to player characters to legal persons without strain, and it carries no AI-agent connotations. One caveat worth noting: in medical and legal contexts, &#8220;subject&#8221; can imply a human under observation or study, with associated ethical weight (research subjects, GDPR data subjects), so we will want to examine how it lands in biomedical and regulatory domains.<\/li>\n<\/ul>\n\n\n\n<p>This is an open question, not a decision. We will raise it formally at the next meeting on <strong>3 July<\/strong>, but we would very much like to hear your thinking beforehand. Please post to the mailing list at <a href=\"mailto:public-cg-holon@w3.org\" target=\"_blank\" rel=\"nofollow\">public-cg-holon@w3.org<\/a> with your candidate and your reasoning \u2014 especially if you bring a domain perspective (biomedical, legal, geospatial, gaming, supply chain) that these candidates handle well or handle badly.<\/p>\n\n\n\n<p>Good terminology, established early, saves a great deal of rework later.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Working Groups: Formalising Structure<\/h2>\n\n\n\n<p>At the inaugural meeting we proposed the following initial working groups:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>I. Core Architecture<\/strong> \u2014 holon model, named graph containers, boundary semantics, the scene\/event graph partition structure<\/li>\n\n\n\n<li><strong>II. DataBook Standard<\/strong> \u2014 the Markdown-based substrate for holon grounding, provenance, and LLM integration<\/li>\n\n\n\n<li><strong>III. Network Architecture<\/strong> \u2014 federated holon meshes, messaging patterns, interoperability conventions<\/li>\n\n\n\n<li><strong>IV. Validation, Verification &amp; Security<\/strong> \u2014 SHACL-based boundary enforcement, portal constraints, security considerations<\/li>\n\n\n\n<li><strong>V. Industry Utilisation<\/strong> \u2014 domain application patterns across healthcare, media, supply chain, finance, education<\/li>\n\n\n\n<li><strong>VI. Ontology &amp; Heterarchical Alignment<\/strong> \u2014 alignment with BFO, UFO, DSRP, and related foundational frameworks<\/li>\n<\/ul>\n\n\n\n<p>At the <strong>3 July meeting<\/strong> we will be formally approving these working groups and their initial chairs. If you are interested in leading or co-chairing any of these groups, we want to hear from you.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Interest and Participation Form \u2014 Coming Shortly<\/h2>\n\n\n\n<p>To make it easy to capture who wants to contribute what, we are preparing a short participation form that will ask for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Your name, background, and organisational affiliation (if any)<\/li>\n\n\n\n<li>Which working groups you want to participate in<\/li>\n\n\n\n<li>Whether you are interested in a chair or editor role<\/li>\n\n\n\n<li>What you are hoping to get out of the CG and the respective working groups<\/li>\n\n\n\n<li>Any reference implementations or prior work you would like to contribute<\/li>\n<\/ul>\n\n\n\n<p>Watch the mailing list for the link \u2014 it will go out before the end of next week, well ahead of the July 3rd meeting, so we can arrive there with a clearer picture of who is doing what.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Next Meeting<\/h2>\n\n\n\n<p><strong>Date:<\/strong> Friday, 3 July 2026<br><strong>Time:<\/strong> 7:00\u20138:00am Pacific \/ 10:00\u201311:00am Eastern \/ 15:00\u201316:00 BST<br><strong>Agenda:<\/strong> Will be distributed to the mailing list no later than 48 hours prior.<\/p>\n\n\n\n<p>Agenda items for the July 3rd session are welcome now. If you have something you want to present, demonstrate, or raise for discussion, please send it to the mailing list or contact me directly at kurt.cagle@gmail.com.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<p><em>Kurt Cagle is a consulting ontologist, knowledge graph architect, and technical author. He serves as Acting Chair of the W3C Holon Community Group and publishes <a href=\"https:\/\/ontologist.substack.com\/\" target=\"_blank\" rel=\"nofollow\">The Ontologist<\/a> and <a href=\"https:\/\/inferenceengineer.substack.com\/\" target=\"_blank\" rel=\"nofollow\">The Inference Engineer<\/a> on Substack. Copyright 2026 Kurt Cagle.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Posted 19 June 2026 \u2014 Kurt Cagle, Acting Chair, W3C Holon Community Group Thank you to everyone who joined us this morning for the inaugural meeting of the W3C Holon Community Group. Thirty-plus people showing up at 7am Pacific on &hellip; <a href=\"https:\/\/www.w3.org\/community\/holon\/2026\/06\/19\/after-the-inaugural-what-comes-next-for-the-holon-community-group\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":795,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_s2mail":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-10","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.w3.org\/community\/holon\/wp-json\/wp\/v2\/posts\/10","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.w3.org\/community\/holon\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.w3.org\/community\/holon\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/holon\/wp-json\/wp\/v2\/users\/795"}],"replies":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/holon\/wp-json\/wp\/v2\/comments?post=10"}],"version-history":[{"count":1,"href":"https:\/\/www.w3.org\/community\/holon\/wp-json\/wp\/v2\/posts\/10\/revisions"}],"predecessor-version":[{"id":11,"href":"https:\/\/www.w3.org\/community\/holon\/wp-json\/wp\/v2\/posts\/10\/revisions\/11"}],"wp:attachment":[{"href":"https:\/\/www.w3.org\/community\/holon\/wp-json\/wp\/v2\/media?parent=10"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.w3.org\/community\/holon\/wp-json\/wp\/v2\/categories?post=10"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.w3.org\/community\/holon\/wp-json\/wp\/v2\/tags?post=10"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}