Skip to content

ELF 500x draft: EXPRESSdocs Publishing Framework - #14

Open
ronaldtse wants to merge 1 commit into
mainfrom
feat/expressdocs-framework
Open

ronaldtse wants to merge 1 commit into
mainfrom
feat/expressdocs-framework

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

Draft of the ELF 500x specification: EXPRESSdocs Publishing Framework

Executes the scope proposed in #13, enumerated from current practice:
project layout, collection manifest, template contract, anchor and
URN semantics, build interface, delivery verification (expectations,
provenance, structured diagnostics), the performance contract
(compiled-template cache; content-addressed, toolchain-keyed caches
whose warm-skips validate what produced them; byte-identical
determinism), and conformance classes with the sample project as the
conformance corpus.

Docnumber 5002 is provisional; this is draft 0.1 for review.

Working draft of the EXPRESSdocs publishing framework as an
implementation-neutral contract, enumerated from current practice
(suma as the conforming engine, mn-samples-expressdocs as the
conformance corpus, iso-10303 as production adoption): project
layout, collection manifest, template contract, anchor/URN
semantics, build interface, delivery verification with expectations
and provenance, the three-part performance contract (compiled-template
cache, content-addressed toolchain-keyed caches, byte-identical
determinism), and conformance classes incl. the diagnostic-stability
rule (category+rule is stable; codes are labels).

Docnumber 5002 provisional; draft 0.1. Executes the scope agreed in
#13.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant