<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>DDD - Tag - DClimber — Business Software, Event Modeling, and Delivery</title>
        <link>https://dclimber.com/tags/ddd/</link>
        <description>DDD - Tag - DClimber — Business Software, Event Modeling, and Delivery</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>info@dclimber.com (Dastan Abdrakhmanov)</managingEditor>
            <webMaster>info@dclimber.com (Dastan Abdrakhmanov)</webMaster><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Fri, 11 Sep 2026 00:00:00 &#43;0000</lastBuildDate><atom:link href="https://dclimber.com/tags/ddd/" rel="self" type="application/rss+xml" /><item>
    <title>Event Modeling in HCL specs</title>
    <link>https://dclimber.com/posts/event-modeling-in-hcl-specs/</link>
    <pubDate>Fri, 11 Sep 2026 00:00:00 &#43;0000</pubDate>
    <author>Author</author>
    <guid>https://dclimber.com/posts/event-modeling-in-hcl-specs/</guid>
    <description><![CDATA[Announcing a .em.hcl language spec for Event Modeling.
It lets people document their event models as code.
Yes, there are currently projects like:
yaml: https://www.esdm.io/ https://emlang-project.github.io/ json: https://github.com/dilgerma/event-modeling-spec So you might ask why HCL?
I see it this way:
For this project, the block form is useful because the source resembles the concepts being discussed.
My personal motivation was:
I want a schema in a language I can easily edit by hand; sorry to Mermaid diagrams, but they are NOT human-friendly for event modeling The JSON spec is also not something I am willing to write by hand I want to store it in a git repo And I want it to be rendered as a nice HTML event model that can live on GitLab/GitHub Pages as my system documentation.]]></description>
</item>
</channel>
</rss>
