Remove HTMT and HTML <slot> references from the docs.

Drop the HTMT section from related-projects and the HTML <template>/<slot>
and HTMT rows from the framework slot mappings, since neither is ready yet.

Author: jnbdz

docs/related-projects.md

@@ -2,34 +2,6 @@
 
 VDP is part of an ecosystem of specifications and implementations for server-driven UI rendering.
 
-## HTMT — HyperText Markup Templating
-
-[GitHub](https://github.com/ViewDescriptorProtocol/HTMT){ .md-button }
-
-A templating engine using JSONPath-based `ht-*` data attributes for dynamic data binding in HTML/HTMX. HTMT extends standard HTML with custom attributes for declarative rendering and state management directly in the markup.
-
-**Key attributes:**
-
-| Attribute | Description |
-|-----------|-------------|
-| `ht-bind` | Bind data to element content |
-| `ht-loop` | Iterate over arrays |
-| `ht-template` | Reusable template blocks |
-| `ht-attr-[name]` | Bind to HTML attributes |
-| `ht-show` / `ht-hide` | Conditional visibility |
-| `ht-switch` / `ht-case` | Switch-case rendering |
-| `ht-class-[name]` | Conditional CSS classes |
-| `ht-root-[attribute]` | Root-scoped variant of any attribute, binding against the root of the data instead of the local scope |
-
-All attributes use JSONPath expressions (e.g., `$.user.name`) for data binding.
-
-HTMT templates can be used as VDP template targets — VDP declares *which* HTMT templates to render, while HTMT handles the actual data binding.
-
-!!! note "Status"
-    Working Draft (Alpha)
-
----
-
 ## js-HTF — JavaScript Hierarchical Template Framework
 
 [GitHub](https://github.com/ViewDescriptorProtocol/js-HTF){ .md-button }

docs/specification.md

@@ -26,7 +26,7 @@ REST APIs return structured data (JSON, XML) that carries no presentation inform
 
 - **View Descriptor**: A JSON object that describes a template tree — a root template URL and its slot assignments.
 - **Template URL**: A URL identifying a template resource. The URL MUST resolve to a renderable template in the client's rendering framework.
-- **Slot**: A named insertion point in a template where a sub-template can be composed. Slot names correspond to the template's own insertion point identifiers (e.g., Qute's `{#insert slotName}`, HTML's `<slot name="slotName">`).
+- **Slot**: A named insertion point in a template where a sub-template can be composed. Slot names correspond to the template's own insertion point identifiers (e.g., Qute's `{#insert slotName}`).
 - **View Descriptor Resource**: A standalone JSON document containing a view descriptor, addressable by its own URL, cacheable independently of the data it describes.
 - **Static Composition**: Composition written directly into a template's source — for example, a layout that always includes its `_head` partial. VDP does not describe static composition; it is internal to the template.
 - **Dynamic Composition**: Composition that changes per API response — a slot whose template is chosen by the server at request time. These are the slots a view descriptor declares.
@@ -366,8 +366,6 @@ VDP is agnostic to the template language. However, a template used with VDP MUST
 | Framework         | Slot Mechanism                  | Example                                 |
 |-------------------|---------------------------------|-----------------------------------------|
 | Qute              | `{#insert slotName}{/insert}`   | `{#insert mainContent}Default{/insert}` |
-| HTML `<template>` | `<slot name="slotName">`        | `<slot name="mainContent"></slot>`      |
-| HTMT              | `ht-template="slotName"`        | `<div ht-template="mainContent"></div>` |
 | Thymeleaf         | `th:fragment` / `th:replace`    | `<div th:replace="~{slotName}"></div>`  |
 | JSX/React         | `props.children` or named props | `{props.mainContent}`                   |
 | SwiftUI           | `@ViewBuilder` parameters       | `var mainContent: () -> Content`        |