accordion, accordion-item, recipe and how-to set typeof on nodes they did not create and hand-write a <div property="text"> wrapper to supply the value. Replace both with a declaration.
The HTML must not change. That is the whole difficulty.
Tracking started Sep 14 — check back for trends.
f847949The obvious cleanup is to delete the wrapper and teach collectJsonLd to take a typed node's own text as a named property. It would break the HTML.
RDFa Core 1.1 §7.5 step 11 resolves a property's object as: @content → literal; else @typeof present and @about absent → the typed resource; else a plain literal from the text. So an element carrying both property and typeof has its object fixed to the typed resource and its text is unreachable as a literal. Today's output —
<div typeof="Answer" property="acceptedAnswer"><div property="text">…</div></div>
— expresses _:q acceptedAnswer _:a . _:a a Answer . _:a text "…". Without the inner element the third triple is gone. Since SPEC-082 renders the SEO carriers inline, refrakt publishes RDFa and JSON-LD on the same page, so the two would assert different graphs on every accordion, recipe and how-to.
What is wrong is that runes hand-write it. WORK-565's text: moves the wrapping into the applier, and the table declares only the role:
accordionItem: { type: 'Question', properties: { name: 'name' }, entities: { body: { type: 'Answer', property: 'acceptedAnswer', text: 'text' }, }, }
accordion, accordion-item, recipe and how-to declare their schema as tables, with no node.attributes.typeof = … mutation and no hand-written property="text" wrapper left in any transformrecipe's <li>s resolve through their existing data-names (ingredient, step) — no new names needed hererecipe's image source resolves through the name WORK-561 gave itschema="none" still strips the whole subtree on accordion, including the wrapper the applier now emitsproperty and typeof always has an inner carrier for its text — so the wrapper cannot be "optimised away" laterWrite the byte-identical assertion first. These four runes are where a plausible-looking simplification silently changes what the page asserts, and the reasoning that leads there is short enough that someone will re-derive it. The test is the only durable form of the argument; the prose above is a comment that will not run.
accordion is also the rune that motivated the whole spec, by way of WORK-548 — rendering a list of universal attributes as accordion items publishes roughly 970 fabricated Question entries across 88 pages. WORK-552 already shipped schema="none" as the author-side out. What this item adds is that the suppression and the emission are now declared in the same place, so the relationship between them is visible.
Note accordion's comment at packages/runes/src/tags/accordion.ts:111 — "Done here rather than in a later pass because extractSeo reads the …" — is the same constraint WORK-565 is built around. Update it rather than deleting it; it is the only place in the source that records why this cannot live in the engine.
Question entriesschema="none", shippedpackages/runes/src/tags/accordion.ts:111 — the comment to carry forward