Showcase

One source of truth, embedded where it is read

The moment a definition is copied into a second document, the two copies drift. SemText's sem-embed points at the other document instead — a whole document, one block by id, or a block in a presentation mode — so the glossary entry, the procedure, the fact exists once and renders wherever it is read.

The contract

Three forms: a whole source document, a #section-id into it, and a mode for how the block presents. This example stays in source view — see the status note below.

embedding example

embedding.md · authored SemText

source

      
      <h2>Shared glossary</h2>
    
      <p>Definitions are written once and embedded where they are read —
    
      never copied between documents:</p>
    
      <sem-embed source="../glossary.sem.html"></sem-embed>
    
      <!-- one block of the source, by its id -->
    
      <sem-embed source="../glossary.sem.html#f-oidc"></sem-embed>
    
      <!-- the same block, presented as a card -->
    
      <sem-embed source="../glossary.sem.html#f-oidc" mode="card"></sem-embed>

render — pending bundle

Render view: this block wires to the SemText runtime bundle in the full example viewer (port-reference lane) — the source beside it is the same file, byte for byte.

Status

This is a proposal, not a catalogued element: the spec states no schema for sem-embed and no shipped tier renders it — this page deliberately does not fake a render. Until a schema lands, an embedded reference reads as its authored markup, which is a record, not a broken page.

There is no reference page for this pattern — it has no schema file in the spec. Vocabulary proposals land in npl-enhanced-content 's spec catalog.