how about a "wrapper" element?

[David Farmer]

There are some use cases that might benefit from a "wrapper" element.

All it does is serve as a container. It can take an optional
component attribute,
but no other attributes.

Some use cases:

1. One of your class sections has a project due on Tuesday,
and the other on Wednesday. Instead of having two paragraphs,
differing only by one word and having different component attributes,
you could just put a wrapper around individual words.

2. It lets you xi:include content which is not valid xml on its own.
For example, a few exercises, two paragraphs, etc.

Regards,

David

[Rob Beezer]

A bit brief. Sympathetic to the use case.

For two paragraphs with mildly different content we have the #custom element.

There are solutions for xi:include without a root element, with xpointer, I think.

Schema: what goes in #wrapper, and where can #wrapper live?

In XSL when you look up the tree, we would need to "skip over" #wrapper amny,
many places.

Rob

[David Farmer]

One of the first steps in the assembly is when the components
are selected and everything is merged into one file. At that point
all the wrapper
would be removed.

So, implementing wrapper would involve one change early in the process.
Everything in the later stages would be unchanged, because all the
wrapper tags are gone.

Maybe anything can go in wrapper, and it can go anywhere?

> --
> 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/MTAwMDAwVzdmRnR5QTY.1790710068%40pnsh.