all properties contained in this spec, in various forms
other parsing artifacts to be used by knowledgeable modules.
other parsing artifacts to be used by knowledgeable modules. Parsers can put stuff in here.
original text content, not pre-processed - this is generally useless
the content, pre-processed, with includes and macros expanded etc.
the content, pre-processed, with includes and macros expanded etc. But no parsing done
NOTE this is not a different representation, like html or something... it is just the content, pre-processed
todo should be an Either
find template with predicate
the content, pre-processed, with includes expanded etc.
the content, pre-processed, with includes expanded etc.
NOTE this is not a different representation, like html or something... it is just the content, pre-processed
the assumption is that specs can parse themselves and cache the AST elements
errors must contain "CANNOT PARSE" and more information
todo parsed should be an Either
set during parsing and folding - false if page has any user-specific elements any scripts or such will make this false this is very pessimistic right now for safety issues: even a whiff of non-static content will turn this off
category - you can categorize the specs
we support draft specs vs non=draft (published)
visibility of this spec - see razie.tconf.Visibility
a specification - can be a text, a wiki or anything else we can parse to extract some piece of configuration
Specifications are meant to be parsed and DOM/diesel elements collected. Also, they are addressable (specPath)
We do not concern with the way these are found - that's the inventory, but usually they are passed into an engine etc