Published specifications

Example: preserve a published section and example

<section id="introduction">
  <h2>Introduction</h2>
  <p>This document describes the exchange format.</p>
  <aside class="example" id="example-triple">
    <div class="marker">Example 1: A triple</div>
    <pre>&lt;urn:customer:1&gt; &lt;urn:name&gt; "Ada" .</pre>
  </aside>
</section>

This illustrates the static HTML structures in a published specification, not a complete input document. GraphArch retains supported sections, anchors, and examples from the full published snapshot, then publishes a new specification and PDF from the collected graph.

Compare the complete N-Triples input snapshot with the generated specification and PDF. Look at Introduction and the numbered examples in N-Triples Language.

Supporting collectors

The Published W3C Specification Collector reads supported published HTML. The Legal Preamble Collector separately reads a supported legal disclosure, such as DPROD's preamble. Neither requires executing the original website generator.

Recognised published content

A specialised collector reads a pinned snapshot of a published W3C specification. It retains publication metadata, sections, headings, anchors, links, examples, and supported static HTML content as documentation graph content. The RDF 1.2 N-Triples showcase exercises this source path.

This collector reads published structure. It does not execute a ReSpec script or claim compatibility with every ReSpec authoring extension. Unsupported published markup fails explicitly. The ReSpec compatibility contract records the migration reference and its acceptance criteria.

A separate preamble collector recognises a supported legal-disclosure block in a source template. DPROD supplies details.preamble-section; its complete legal wording and source provenance are retained without executing the surrounding scripts or template language.

A specification renderer can show that fragment as a disclosure, while the PDF renderer gives it dedicated legal front matter. See front-matter notices for the fragment and target relationship.

Publication authority is independent

A collected specification's content does not require every output to have the source website's branding. The publication target and authority metadata select the generated specification's identity and presentation. See the specification workflow and showcase gallery for current examples.

Search documentation

Enter words to search this site.