Hej, HML (Hica Markup Language) is a structured document and configuration language initially built for the hica programming language ecosystem. There is a v0.3.0 specification published and a reference implementation in hica at HML repo , I'm looking for community feedback, critique, and curious developers who want to help build parsers and libraries in their favourite languages. Why another markup language? TOML and JSON are great for flat configurations, but they fall flat when you need complex hierarchical trees or mixed text documents. Contrary to those (and an unpopular opinion perhaps...), XML is fantastic at separating metadata from content . With HML I tried to bridge this gap. It aims to preserve the semantic strengths of XML while keeping the clean, low-noise readability of modern config formats. Some highlights Metadata vs. Content: Attributes in (...) for metadata; bodies in {...} for content. Text content requires an explicit wrapper element ( @body , @p , @text ). If you accidentally miss a colon in a property (e.g., timeout 30s ), HML throws a syntax error instead of silently parsing it as a string block. Built-in literals like timeout: 30s or interval: 500ms make configurations clean. Quickly create nested structures inline without writing boilerplate blocks. The parser never needs lookahead beyond a single token to determine context. Here is a quick look at an HML configuration snippet: ``` @service(id: "auth-api", public: true) { environment: "production" cache_ttl: 24h @upstream(url: "https://api.internal") { retry: @policy(max: 3, delay: 500ms) } } ``` Do you like to write handwritten recursive descent parsers, or messing around with tools like nom , pest , antlr , or gocc ? It would be amazing to have libraries in other languages! Read the full spec here Comment below if you’re interested in building a parser or if you have thoughts on the design principles. submitted by /u/cladamski79 [link] [comments]