FITB schema items

[rbeezer]

For reaction from @dbrianwalton. If you provide an organized response (keep numbering, etc) I can probably have Claude read it with good effect. Thanks.

[rbeezer]

I'm bringing the RELAX-NG schema (schema/pretext.xml) up to date with the dynamic fill-in (FITB) exercises as authored in the sample article, and I'd like your guidance on the intended model before encoding it.

What already validates. The evaluation → evaluate → test → numcmp/strcmp/jscmp/mathcmp style is already in the schema, and the sample's fill-ins using it validate cleanly. (I also fixed an orphaned FillIn pattern — the dev @mode/@answer/@ansobj/@name/@width extension had never been wired to the inline fillin; inline interactive blanks now validate.)

What the schema does not yet model (used in the sample's "Dynamic Exercises"):

• <setup> (with @seed): computed-value definitions — <formula><eval obj="…"/></formula>, <variable name="…">…</variable>, and an older <var><condition string="…"|number="…"><feedback/></condition></var>.
• <eval obj="…"/>: inline references to setup objects, appearing inside <p>, <m>, <md>, <formula>, <variable>.
• <evaluation> computed style: directly holds eval/formula/variable/feedback (rather than evaluate+).

Questions:

1. Is the setup/eval/formula/variable computed style the current, canonical authoring? Does it coexist with evaluate/test, or supersede it?
2. What is the full content model of <setup> — which children/attributes (formula, variable, var, condition, randomization, …)?
3. Where should <eval obj=> be allowed inline — any math/text (m/md/p), or scoped to dynamic-exercise contexts? (This has the broadest reach into core content models, so I want the scope right.)
4. In the computed style, what exactly does <evaluation> contain (eval/formula/variable/feedback)?
5. Is the old-style <var>/<condition> deprecated — should the sample drop it — or should the schema keep admitting it for backward compatibility?
6. Are de-object/de-number/de-evaluate/de-random/de-expression authored forms, or only compiled (assembly-time) forms? (The schema should validate authored source, not compiled output.)

Once these are settled, the schema changes are mechanical — happy to draft the RELAX-NG once the model is confirmed.

Claude Opus 4.8, acting as a coding assistant for Rob Beezer