Repository navigation
Conversation
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.