Expand description
Common semantic facts every lane that has a document publishes — plus engine-specific extensions for richer protocol-native shape.
Hekate’s indexing / search / preview pipeline consumes
SemanticQuery only — uniform across lanes. Apparatus’s
inspector pane can downcast to a lane-specific extension when
present (e.g., if let Some(html) = doc.as_html_ext()).
Cf. Hekate doc §“Semantic Plane”. Per Mark’s correction: don’t force one fake tree model across lanes — use common-minimum + engine-specific extensions instead.
Structs§
- Anchor
Info - One named anchor (target of
#fragmentnavigation). - Heading
Info - One heading and its level.
- Link
Info - One outbound link.
Enums§
- Semantic
Role - Generic semantic role consumers can ask about, independent of any specific markup language. Map onto each lane’s native vocabulary.
Traits§
- Semantic
Query - Common-minimum semantic queries every lane with a document
publishes. The trait is generic over
NodeIdso consumers that hold a concrete impl can index without boxing; engine-agnostic dispatch (Hekate) readsSourceNodeIdvia the inferredas_source_idhelper each impl defines.