Schema work

[Rob Beezer]

Massive session to work on the schema (relative to the dev version) on the
sample article. About 17 changes to the sample article to conform, and about an
equal number of changes to the schema itself.

https://github.com/PreTeXtBook/pretext/pull/2989

Remaining items are the subject of a couple of issues for maintainers of
PreFigure and dynamic exercises (not rushing them!).

I was a bit more cavalier than usual, but it was not so easy deciding what was a
source change and what was a schema change. And I may back-out some things (see
next post).

Perhaps the only major change was to disallow #exercisegroup in a #worksheet.
The primary reason is that #sidebyside and #sbsgroup provide much of the same
functionality and with much greater flexibility. Secondary reasons include
difficulty page-breaking an #exercisegroup, and the difficulties making it
accessible (most recently with the XSL-FO work on an accessible PDF).

@Oscar - see 4b0b0d3feaa57 - are these attributes right for a #worksheet?

@David A - see c3f33de7b2c6c - does #annotations (plural) require @text? The PF
schema must say so?

Anyone - see ac2692c0f0cf42c - a #program *after* a #statement in a
PROJECT-LIKE? A "coding activity"? I don't recall the origin of this one.

Rob

[David Austin]

@David A - see c3f33de7b2c6c - does #annotations (plural) require @text?  The PF
schema must say so?

This was a recent change, but it's also backwards compatible.  I've also been doing quite a bit of work on the PF schema and either way, the old or the new, should validate.  I will send you a PR with the new schema and fixing up the sample article tomorrow.  I'm getting back online now and will respond soon to a couple of other things as well.

David

 

Anyone - see ac2692c0f0cf42c - a #program *after* a #statement in a
PROJECT-LIKE?  A "coding activity"?  I don't recall the origin of this one.

Rob

--
You received this message because you are subscribed to the Google Groups "PreTeXt development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/MTAwMDAxMC5iZWV6ZXI.1783007672%40pnsh.

[Rob Beezer]

Thanks, David. No rush - keep re-entry relaxed.

My assistant added several #annotations/@text, which seem to just duplicate the
top-level #annotation, so apparently both of us are a bit uncertain. So
*please* get the sample article ship-shape! And I will look for a PF schema
update. Whenever.

Thanks,
Rob

On 7/2/26 10:13, David Austin wrote:
>
> @David A - see c3f33de7b2c6c - does #annotations (plural) require @text?
> The PF
> schema must say so?
>
>
> This was a recent change, but it's also backwards compatible.  I've also been
> doing quite a bit of work on the PF schema and either way, the old or the new,
> should validate.  I will send you a PR with the new schema and fixing up the
> sample article tomorrow.  I'm getting back online now and will respond soon to a
> couple of other things as well.
>
> David
>
>
> Anyone - see ac2692c0f0cf42c - a #program *after* a #statement in a
> PROJECT-LIKE?  A "coding activity"?  I don't recall the origin of this one.
>
> Rob
>
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to pretext-dev...@googlegroups.com <mailto:pretext-
> dev%2Bunsu...@googlegroups.com>.

> To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/

> MTAwMDAxMC5iZWV6ZXI.1783007672%40pnsh <https://groups.google.com/d/msgid/
> pretext-dev/MTAwMDAxMC5iZWV6ZXI.1783007672%40pnsh>.

>
> --
> You received this message because you are subscribed to the Google Groups
> "PreTeXt development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email

> to pretext-dev...@googlegroups.com <mailto:pretext-
> dev+uns...@googlegroups.com>.

> To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/

> CANXmVMD2k0KWJYwk9pr8cY55to-c7uMHf55E89S3xYz4NC9wgA%40mail.gmail.com <https://
> groups.google.com/d/msgid/pretext-dev/CANXmVMD2k0KWJYwk9pr8cY55to-
> c7uMHf55E89S3xYz4NC9wgA%40mail.gmail.com?utm_medium=email&utm_source=footer>.

[David Austin]

A new PreFigure schema is included and the #annotations elements in the sample article are fixed up in #2992.

To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/MTAwMDAzMi5iZWV6ZXI.1783014034%40pnsh.

[Oscar Levin]

Perhaps the only major change was to disallow #exercisegroup in a #worksheet.
The primary reason is that #sidebyside and #sbsgroup provide much of the same
functionality and with much greater flexibility. Secondary reasons include
difficulty page-breaking an #exercisegroup, and the difficulties making it
accessible (most recently with the XSL-FO work on an accessible PDF).

I think this is probably okay, although it would be good to get Mitch and Chrissy to look at the worksheets they have made.  Look at the sample article Worksheet 37.9.  Might be worth rewriting that as a group of 5 sidebysides in a sbsgroup before committing to this change.  The page breaking logic for HTML was not that difficult for exercisegroup, and the flexibility it provides to switch between one or more columns is very nice for authors.

 

@Oscar - see 4b0b0d3feaa57 - are these attributes right for a #worksheet

I have no idea where Claude got that idea from (oh, searching I see they are on the worksheets in the sample workbook).  I don't understand what they are intended to be used for, and searching the codebase, they are not implemented as anything at all.  For now, they should be removed, I'd say.