Derivatives and Integrals: An Annotated Discourse

<section xml:id="interesting-corollary" label="section-interesting-corollary">
    <title>An Interesting Corollary</title>
    <objectives xml:id="objectives-structures">
      <title>Fundamental Structures</title>
      <introduction>
        <p>
          This is an <tag>objectives</tag> element you are reading,
          and this is its introduction.
          This early section has really grown and tries to accomplish many things.
          Not all of them are listed here.
        </p>
      </introduction>
      <ol>
        <li xml:id="objective-structure">
          Display various
          <q>blocks</q>, fundamental units of the flow.
        </li>
        <li>More.</li>
        <li>Evermore.</li>
      </ol>
      <conclusion>
        <p>
          This concludes the (incomplete) objectives for this section,
          so now we can carry-on as before.
        </p>
      </conclusion>
    </objectives>
    <introduction>
      <p>
        This is a cross-reference to one of the objectives above,
        forced to use the <c>phrase-global</c> form of the text.
        It should describe the objective as belonging to the <em>section</em>
        (rather than the <em>objectives</em>),
        since objectives are one-per-subdivision and are numbered based upon the containing division:
        <xref ref="objective-structure" text="phrase-global" />.
        For comparison this is the (forced) <c>type-global</c> cross-reference:
        <xref ref="objective-structure" text="type-global" />.
      </p>
      <p>
        The Fundamental Theorem comes in two flavors,
        where usually one is a corollary of the other.
      </p>
    </introduction>
    <subsection xml:id="subsection-second-FTC">
      <title>Second Version of <acro>FTC</acro></title>

      <corollary xml:id="corollary-FTC-derivative">
        <creator>Leibniz, Newton</creator>
        <idx><h>Fundamental Theorem of Calculus</h><h>Corollary</h></idx>
        <statement>
          <p>
            Suppose <m>f(x)</m> is a continuous function.
            Then
            <men xml:id="equation-alternate-FTC">
              \frac{d}{dx}\definiteintegral{a}{x}{f(t)}{t}=f(x)
            </men>.
          </p>
        </statement>
        <proof xml:id="proof-FTC-corollary">
          <p>
            We simply take the indicated derivative,
            applying Theorem<nbsp /><xref ref="theorem-FTC" /> at <xref ref="equation-use-FTC" />
            <mdn>
              <mrow xml:id="equation-use-FTC">\frac{d}{dx}\definiteintegral{a}{x}{f(t)}{t}&amp;=\frac{d}{dx}\left(F(x)-F(a)\right)</mrow>
              <mrow number="no">&amp;=\frac{d}{dx}F(x)-\frac{d}{dx}F(a)</mrow>
              <mrow xml:id="equation-conclude">&amp;=f(x)-0 = f(x)</mrow>
            </mdn>.
          </p>
        </proof>
        <justification>
        <p>
          A justification, which is one of the variants of a proof.
        </p>
        </justification>





        <proof>
          <title>Alternate Proof</title>
          <p>
            You can have multiple proofs,
            and they can have titles which replace the word
            <q>Proof</q>
            as a heading.
            Here we just exercise displayed math with no automatic numbering,
            and an elective number on the middle equation.
            <md>
              <mrow>\frac{d}{dx}\definiteintegral{a}{x}{f(t)}{t}&amp;=\frac{d}{dx}\left(F(x)-F(a)\right)</mrow>
              <mrow number="yes">&amp;=\frac{d}{dx}F(x)-\frac{d}{dx}F(a)</mrow>
              <mrow>&amp;=f(x)-0 = f(x)</mrow>
            </md>
          </p>
        </proof>
      </corollary>
      <p>
        The alternative version of the Fundamental Theorem (<acro>FTC</acro>) in <xref ref="equation-alternate-FTC" /> is a compact way to express the result.
      </p>
      <p>
        For testing purposes, there is a simple bare Sage Cell here.
      </p>
<sage>
<input>
c = 832
c
</input>
</sage>
      <example xml:id="example-mysterious">
        <title>A Mysterious Derivative!</title>
        <p>
          So if we define a function with its variable employed as a limit of integration, like so
          <me>
            K(z)=\definiteintegral{345}{z}{x^4\sin(x^2)}{x}
          </me>
          then we get the derivative of that function so easily it seems like a mystery,
          <me>
            \frac{d}{dz}K(z)=z^4\sin(z^2)
          </me>.
          That's it.
        </p>
        <p>
          For testing purposes, there is a simple Sage Cell here,
          buried inside an example that should be a knowl
          (embedded in the page).
        </p>
<sage>
<input>2+2</input>
</sage>
        <p>
          We test a Sage cell inside a knowl,
          which should set the value of a variable that will be available to subsequent cells within the knowl.
        </p>
<sage>
<input>
a = 6
a
</input>
</sage>
<sage>
<input>
b = a + 10
b
</input>
</sage>
        <p>
          Even if you ran the cell at the top of this page,
          within this knowl the value of the variable <c>c</c> is not known,
          so the next cell will cause an error.
        </p>
<sage>
<input>
c + 400
</input>
</sage>
      </example>
      <p>
        The Sage cells on a page will
        <q>remember</q>
        results computed elsewhere on the page.
        If you rely on this feature,
        remind your readers to evaluate all the necessary cells and that they perhaps need to be evaluated in a certain order.
      </p>
<sage>
<input>
c/2
</input>
</sage>
      <p>
        There are some Sage cells in the previous (knowled) <tag>example</tag>.
        The results there are restricted to the knowl.
        In other words, the scope of those cells is the knowl.
        So if you opened the example and executed the Sage cells there,
        or if you skipped the example entirely, the next cell should not
        <q>know</q>
        the values of those variables and will raise an error.
      </p>
<sage>
<input>
a + b
</input>
</sage>
      <p>
        We cross-reference the example just prior,
        <xref ref="example-mysterious" text="type-global" />,
        to test the simple Sage cells that will now be part of a cross-reference knowl
        (an external file).
      </p>
      <claim xml:id="claim-with-cases">
        <title>An Equivalent Claim</title>
        <statement>
          <p>
            This claim is an equivalence:
            it is true if and only if it is correct.
          </p>
        </statement>
        <proof>
          <p>
            Our purpose here is to show how you can structure a proof with cases,
            such as an equivalence structured with the arrows typically used to demonstrate the two
            <q>directions</q>
            involved in the proof,
            by using the <attr>direction</attr> attribute on a <tag>case</tag> element.
          </p>
          <case direction="forward">
            <p>
              Nulla non lectus suscipit, bibendum leo quis, dignissim justo.
              In urna turpis, tincidunt id elementum id, faucibus ac tellus.
            </p>
          </case>
          <case direction="backward">
            <p>
              Quisque auctor ligula turpis,
              ut aliquam urna consectetur hendrerit.
              Aenean porta dolor et justo facilisis feugiat in sed sapien.
              Nullam porta ex et commodo semper.
            </p>
          </case>
          <case xml:id="inductive-step">
            <title>Case 3b: The inductive step</title>
            <p>
              A case may also have a <c>title</c>,
              whose formatting and structure is entirely up to the author.
              This then becomes the text of a cross-reference, as well.
            </p>
          </case>
          <case xml:id="questioning-case">
            <title>Why Not Try This?</title>
            <p>
              A <tag>case</tag>
              (or any other element with a default title)
              did not always handle title-ending punctuation correctly.
              So we try an example title with a question mark.
            </p>
          </case>
          <case direction="forward" xml:id="forward">
            <title>Necessity</title>
            <p>
              If you like, you can have both indications.
            </p>
          </case>
          <case xml:id="empty-case">
            <p>
              No direction, no title, then just a generic title.
            </p>
          </case>
        </proof>
        <proof>
          <title>Exciting Proof!</title>
          <p>
            We test here that punctuation at the end of the title of a proof is handled correctly.
          </p>
        </proof>
        <proof>
          <title>Exact Proof</title>
          <p>
            This proof should fill exactly three lines
            (as of defaults in place 2018-12-31)
            and so the tombstone/Halmos should be on a fourth line,
            and then <em>flush right</em>. xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx.
          </p>
        </proof>
      </claim>
      <claim xml:id="claim-with-tfae-cases">
        <title>A List of Equivalent Statements</title>
        <statement>
          <p>
            The following are equivalent.
            <ol marker="(i)">
              <li>This statement is equivalent to all those below.</li>
              <li>
                This statement is equivalent to the statement above and to all those below.
              </li>
              <li>
                This statement is equivalent to the two statements above and to the statement below.
              </li>
              <li>This statement is equivalent to all those above.</li>
            </ol>
          </p>
        </statement>
        <proof>
          <p>
            Our purpose here is to show how you can structure a proof with cases to address the circular logic required to prove the equivalence of a list of statements,
            by using the <attr>direction</attr> attribute on a <tag>case</tag> element.
            You should order the list of statements in the order that you would like to prove ``this statement implies the next.''
          </p>
          <case direction="cycle">
            <p>
              Here we would prove that the first statement implies the second.
            </p>
          </case>
          <case direction="cycle">
            <p>
              Here we would prove that the second statement implies the third.
            </p>
          </case>
          <case direction="cycle" xml:id="cycle">
            <title>The trickiest case</title>
            <p>
              This time we include a title to describe the nature of this case.
              But we would still need to prove that the third statement implies the last.
            </p>
          </case>
          <case direction="cycle">
            <title>Wrap-around</title>
            <p>
              Finally, we would complete the cycle of logic by proving that the last statement implies the first.
            </p>
          </case>
        </proof>
      </claim>
      <p>
        We can also use <attr>direction</attr> set to <c>cycle</c> in a stand-alone proof of our TFAE claim.
        If we include a <attr>ref</attr> on the <tag>proof</tag> that points to the original claim,
        then the formatting of the markers on the statement list will be honored in our cases.
      </p>
      <proof ref="claim-with-tfae-cases">
        <p>
          Once again we will prove that the four statements in <xref ref="claim-with-tfae-cases" /> are equivalent.
        </p>
        <case direction="cycle">
          <p>
            Another argument that the first statement implies the second.
          </p>
        </case>
        <case direction="cycle">
          <p>
            And another argument that the second statement implies the third.
          </p>
        </case>
        <case direction="cycle">
          <title>Not so tricky this time</title>
          <p>
            Why did we find it so difficult before to prove that the third statement implies the last?
          </p>
        </case>
        <case direction="cycle">
          <title>Wrap-around</title>
          <p>
            And once more we complete the cycle of logic.
          </p>
        </case>
      </proof>
      <p>
        A couple more times to check that the default list markers get applied to the directional cases properly.
      </p>
      <claim xml:id="another-claim-with-tfae-cases">
        <title>Another List of Equivalent Statements</title>
        <statement>
          <p>
            The <tag>ol</tag> that creates the list below does not have <attr>marker</attr>.
            <ol>
              <li>This statement is equivalent to the two below.</li>
              <li>
                This statement is equivalent to both the statement above and to the statement below.
              </li>
              <li>This statement is equivalent to the two above.</li>
            </ol>
          </p>
        </statement>
        <proof>
          <p>
            You know the drill by now.
          </p>
          <case direction="cycle">
            <p>
              Does the first statement imply the second?
            </p>
          </case>
          <case direction="cycle">
            <title>The
            <q>middle</q>
            case</title>
            <p>
              Does the second statement imply the third?
            </p>
          </case>
          <case direction="cycle">
            <p>
              And finally, does the third imply the first?
            </p>
          </case>
        </proof>
      </claim>
      <p>
        This proof includes a <attr>ref</attr> to the preceding claim.
      </p>
      <proof ref="another-claim-with-tfae-cases">
        <case direction="cycle">
          <p>
            Does the first statement imply the second?
          </p>
        </case>
        <case direction="cycle">
          <title>The
          <q>middle</q>
          case</title>
          <p>
            Does the second statement imply the third?
          </p>
        </case>
        <case direction="cycle">
          <p>
            And finally, does the third imply the first?
          </p>
        </case>
      </proof>
      <p>
        This proof does not include a <attr>ref</attr>,
        and so the direction indicators get default markers.
      </p>
      <proof>
        <case direction="cycle">
          <p>
            Does the first statement imply the second?
          </p>
        </case>
        <case direction="cycle">
          <p>
            And finally, does the second imply the first?
          </p>
        </case>
      </proof>
    </subsection>

    <subsection>
      <title>A Pedagogical Note about <xref ref="subsection-second-FTC" text="type-global" /></title>
      <subsubsection xml:id="subsubsection-different-integrals">
        <title>Symbolic and Numerical Integrals</title>
        <p>
          The Fundamental Theorem explains why we use the same notation for a definite integral,
          which is a numerical calculation,<fn>
          Which I think sometimes students lose sight of.
          </fn> and an antiderivative,
          which is a symbolic expression.
        </p>
        <exercise xml:id="exercise-essay">
          <title>Essay Question: Compare and Contrast</title>
          <statement>
            <p>
              Write a short paragraph which compares,
              and contrasts, the definite and indefinite integral.
              This is an exercise which sits in the midst of the narrative,
              so is formatted more like an example or a remark.
              It can have a hint and a solution, but this one does not.
              It can have a title, which this one does.
            </p>
          </statement>
          <hint>
            <p>
              Start writing!
            </p>
          </hint>


        </exercise>
      </subsubsection>
      <subsubsection>
        <title>Advice</title>
        <p>
          Using an
          <q>integral sign</q>
          for an antiderivative
          (aka indefinite integral)
          would seem to make the Fundamental Theorem a <foreign xml:lang="fr-FR">fait accompli</foreign>.
          So I would suggest not conflating the notation for two very different things until the Fundamental Theorem exposes them as being highly related.
        </p>
        <example xml:id="example-structured">
          <title>An Example of Structure</title>
          <statement>
            <p>
              This is an example of an example with a bit more structure.
              Specifically,
              the example has a <c>title</c>,
              as usual,
              but then has a <c>statement</c>,
              which is separate from the <c>solution</c>.
              Why did we implement an example in two ways?
            </p>
          </statement>
          <solution>
            <p>
              Authors asked for it and it seemed a very natural thing to do,
              even if we only had an unstructured version for a long time.
            </p>
          </solution>
        </example>
        <question xml:id="sample-question">
          <title>An Example of a Question</title>
          <statement>
            <p>
              Any kind of question can be marked as such with <tag>question</tag>.
              Or similarly, as a <tag>problem</tag>.
              They behave identically to <c>example</c> s, such as the one preceding and are numbered along with theorems,
              examples. etc.
            </p>
          </statement>
          <solution>
            <p>
              You can have a solution.
              Or several, even if you don't ask a question.
            </p>
          </solution>
          <solution>
            <p>
              See?
            </p>
          </solution>
        </question>
        <exercise xml:id="inline-exercise">
          <title>An Inline Exercise</title>
          <statement>
            <p>
              There are lots of exercises in this sample article,
              but mostly they are in special exercise sections.
              Sometimes you just want to sprinkle some exercises through the narrative.
              We call these <term>inline exercises</term>,
              in contrast to <term>divisional exercises</term>.
              The inline exercises look a bit more like a theorem or definition,
              with titles and fully-qualified numbers.
            </p>
            <p>
              These may also have hints, answers and solutions.
            </p>
          </statement>
          <hint>
            <p>
              A good hint.
            </p>
          </hint>
          <answer>
            <p>
              42.
            </p>
          </answer>
          <solution>
            <p>
              If your exercise feels like proving a theorem,
              then you might want to make some comments,
              but also clearly delineate which part of the solution is a the complete proof.
            </p>
            <proof>
              <p>
                Lorem ipsum dolor sit amet, consectetur adipiscing elit.
                Proin lorem diam, convallis in nulla sed, accumsan fermentum urna.
                Pellentesque aliquet leo elit,
                ut consequat nunc dapibus ac.
                Sed lobortis leo tincidunt, vulputate nunc at, ultricies leo.
                Vivamus purus diam,
                tristique laoreet purus eget, mollis gravida sapien.
                Nunc vulputate nisl ac mauris hendrerit cursus.
                Sed vel molestie velit.
                Suspendisse sem sem, elementum at vehicula id, volutpat ac mi.
                Nullam ullamcorper fringilla purus in accumsan.
                Mauris at nunc accumsan orci dictum vulputate id id augue.
                Suspendisse at dignissim elit, non euismod nunc.
                Aliquam faucibus magna ac molestie semper.
                Aliquam hendrerit sem sit amet metus congue tempor.
                Donec laoreet laoreet metus, id interdum purus mattis vulputate.
                Proin condimentum vitae erat varius mollis.
                Donec venenatis libero sed turpis pretium tempor.
              </p>
              <p>
                Praesent rutrum scelerisque felis sit amet adipiscing.
                Phasellus in mollis velit.
                Nunc malesuada felis sit amet massa cursus,
                eget elementum neque viverra.
                Integer sagittis dictum turpis vel aliquet.
                Fusce ut suscipit dolor, nec tristique nisl.
                Aenean luctus, leo et ornare fermentum,
                nibh dui vulputate leo, nec tincidunt augue ipsum sed odio.
                Nunc non erat sollicitudin, iaculis eros consequat, dapibus eros.
              </p>
            </proof>
          </solution>


        </exercise>
        <example xml:id="example-math-title">
          <title>An Example of with <m>\frac12</m> math formula <m>\displaystyle{\int e^x \, dx}</m> in the title</title>
          <statement>
            <p>
              Just for testing math in knowls,
              and also extra whitespace in a <tag>p</tag>.
            </p>
          </statement>
        </example>
        <p>
          There are many different blocks you can employ,
          and they mostly behave the same way.
          A <tag>project</tag>
              <idx><h>project</h></idx>
          is very similar to a <tag>question</tag>
              <idx><h>question</h></idx>
          or <tag>problem</tag>
              <idx><h>problem</h></idx>
        </p>
        <project>
          <title>Start Exploring <pretext /></title>
          <p>
            You could grab the <c>minimal.xml</c> file from the <c>examples/minimal</c> directory and experiment with that.
          </p>
          <p>
            Projects get their own independent numbering scheme,
            since they may be central to your textbook, workbook, or lab manual.
            If you process this sample article with level for project numbering set to <c>0</c> then you will get consecutive numbers from the beginning of your book,
            starting with 1.
          </p>
        </project>
        <exploration>
          <title>Exploring Explorations</title>
          <statement>
            <p>
              This is an <tag>exploration</tag>.
                  <idx><h>exploration</h></idx>
              Other similar possibilities are <tag>project</tag>,
                  <idx><h>project</h></idx>
              <tag>activity</tag>,
                  <idx><h>activity</h></idx>
              <tag>task</tag>,
                  <idx><h>task</h></idx>
              and <tag>investigation</tag>.
                  <idx><h>investigation</h></idx>
            </p>
            <p>
              Note that projects, activities, explorations,
              tasks and investigations <em>share</em>
              the independent numbering scheme,
              so it is really only intended you use one of these.
              If you want a variant of the name (<eg />
              <q>Directed Activity</q>
              ) you can use the <tag>rename</tag>
                  <idx><h>rename an environment</h></idx>
              facility
              (<xref ref="rename-facility" text="type-global" />).
            </p>
          </statement>
          <solution>
            <p>
              This is a
              <q>solution</q>
              to the exploration.
              In practice,
              you might choose to not make this visible for students,
              but instead include it as part of some guidance you might provide to instructors
              (<eg /> an
              <pubtitle>Instructor's Manual</pubtitle>).
            </p>
          </solution>
        </exploration>
        <activity xml:id="activity-with-hint-answer-solution">
          <title>Hints, Answers, Solutions</title>
          <prelude>
            <p>
              This is quite the activity upcoming.
              This is a <c>prelude</c> authored within the <c>activity</c> element,
              but visually just prior.
            </p>
          </prelude>
          <statement>
            <p>
              Another variant of these project-like items is to possibly include a <tag>hint</tag> and an <tag>answer</tag> before the <tag>solution</tag>.
            </p>
          </statement>
          <hint>
            <p>
              Just a little help.
            </p>
          </hint>
          <answer>
            <p>
              The result, but no help in getting there.
            </p>
          </answer>
          <solution>
            <p>
              Everything to get it all done, in detail.
            </p>
          </solution>
          <postlude>
            <p>
              This was quite the activity just now.
              This is a <c>postlude</c> authored within the <c>activity</c> element,
              but visually just after.
            </p>
          </postlude>
        </activity>
        <note xml:id="note-remark">
          <title>A Note on Remarks</title>
          <p>
            <tag>remark</tag>, <tag>convention</tag>, <tag>note</tag>,
            <tag>observation</tag> and <tag>warning</tag> are designed to hold very simple contents,
            with no additional structure
            (no proofs, no solutions, <etc />).
          </p>
          <p>
            But they do carry a title and a number,
            can be the target of a cross-reference,
            and may be optionally knowlized in HTML with the <c>html.knowl.remark</c> processing switch.
          </p>
          <p>
            And distinctly different from a <tag>note</tag> in a <tag>biblio</tag><fn>
            A gratuitous footnote to test prior bug confusing this with a <tag>note</tag> in a <tag>biblio</tag>.
            </fn>.
          </p>
        </note>
        <aside xml:id="an-aside">
          <title>An Aside with a <em>Formatted</em> Title</title>
          <idx>aside</idx>
          <p>
            An <tag>aside</tag> is similar to a remark,
            but is not as critical to the narrative.
            It is not numbered, and so requires a title.
            It can be the target of a cross-reference.
            They are meant to be short,
            and so are not knowlized at their first appearance.
            If the content is appropriate,
            these can be marked as <tag>historical</tag> or <tag>biographical</tag>,
            though longer items should use subdivisions (<eg /> sections,
            subsections) instead.
          </p>
        </aside>
        <p>
          An <tag>exercise</tag> can be structured with <tag>task</tag>.
        </p>
        <exercise xml:id="exercise-structured">
          <title>A very structured exercise</title>
          <introduction>
            <p>
              This is an over-arching introduction to the whole exercise.
              We follow with some tasks.
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
          </introduction>
          <task>
            <title>A super-simple task</title>
            <p>
              This first task is very simple, just a paragraph.
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
          </task>
          <task>
            <p>
              Now three paragraphs.
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
            <p>
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
            <p>
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
          </task>
          <task>
            <title>A title of a task that has a subtask with an <tag>answer</tag> for the Solutions</title>
            <introduction>
              <p>
                This second task is further divided by more tasks.
                This is its introduction.
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
              <p>
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
            </introduction>
            <task>
              <title>A task with a title and an <tag>answer</tag> for the Solutions</title>
              <statement>
                <p>
                  A really simple subtask.
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
                <p>
                  A short paragraph, before an answer.
                </p>
              </statement>
              <answer>
                <p>
                  With a proof.
                </p>
                <proof>
                  <p>
                    In interdum suscipit ullamcorper.
                    Morbi sit amet malesuada augue, id vestibulum magna.
                    Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                    Nulla at neque nisi.
                    Integer vel porta felis.
                  </p>
                </proof>
                <p>
                  And a bit more to say.
                </p>
              </answer>
            </task>
            <task>
              <statement>
                <p>
                  A subtask with an answer.
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
              </statement>
              <answer>
                <p>
                  Right!
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
              </answer>
            </task>
            <task>
              <introduction>
                <p>
                  Three simple sub-sub-tasks.
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
              </introduction>
              <task>
                <p>
                  First subsubtask.
                  Short paragraph.
                </p>
              </task>
              <task>
                <title>A second three-deep subsubtask!</title>
                <p>
                  Second subsubtask.
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
                <p>
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
              </task>
              <task>
                <p>
                  Third subsubtask.
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
                <p>
                  In interdum suscipit ullamcorper
                </p>
                <p>
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
              </task>
              <conclusion>
                <p>
                  The conclusion of the structured subtask.
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
              </conclusion>
            </task>
            <task>
              <p>
                A simple task as the last subtask.
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
            </task>
            <conclusion>
              <p>
                This concludes our structured second task.
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
            </conclusion>
          </task>
          <task>
            <statement>
              <p>
                This third top-level task is intermediate in complexity,
                you are reading the <c>statement</c>,
                which is followed by more items.
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
            </statement>
            <hint>
              <p>
                One hint.
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
              <p>
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
            </hint>
            <answer>
              <p>
                First answer.
                In interdum suscipit ullamcorper.
              </p>
            </answer>
            <answer>
              <p>
                Second answer.
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
              <p>
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
              <p>
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
            </answer>
            <solution>
              <p>
                At last, the solution.
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
            </solution>
          </task>
          <conclusion>
            <p>
              This is a conclusion where you could summarize the exercise.
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
          </conclusion>
        </exercise>
        <p>
          The following <tag>project</tag> is nearly identical to the preceding <tag>exercise</tag>.
        </p>
        <project xml:id="project-structured">
          <title>A very structured project</title>
          <prelude>
            <p>
              The next block is a project,
              demonstrating the use of the <c>task</c> element to structure its parts.
              You are reading the <c>prelude</c> now.
              The project has lots of nonsense words,
              so we can test spacing the nested items.
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
            <p>
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
          </prelude>
          <introduction>
            <p>
              This is an over-arching introduction to the whole project.
              We follow with some tasks.
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
          </introduction>
          <task>
            <p>
              This first task is very simple, just a paragraph.
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
          </task>
          <task>
            <p>
              Now three paragraphs.
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
            <p>
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
            <p>
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
          </task>
          <task>
            <introduction>
              <p>
                This second task is further divided by more tasks.
                This is its introduction.
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
              <p>
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
            </introduction>
            <task>
              <statement>
                <p>
                  A really simple subtask.
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
                <p>
                  A short paragraph, before an answer.
                </p>
              </statement>
              <answer>
                <p>
                  With a proof.
                </p>
                <proof>
                  <p>
                    In interdum suscipit ullamcorper.
                    Morbi sit amet malesuada augue, id vestibulum magna.
                    Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                    Nulla at neque nisi.
                    Integer vel porta felis.
                  </p>
                </proof>
                <p>
                  And a bit more to say.
                </p>
              </answer>
            </task>
            <task>
              <statement>
                <p>
                  A subtask with an answer.
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
              </statement>
              <answer>
                <p>
                  Right!
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
              </answer>
            </task>
            <task xml:id="project-task-level-two">
              <introduction>
                <p>
                  Two simple sub-sub-tasks.
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
              </introduction>
              <task>
                <p>
                  First subsubtask.
                  Short paragraph.
                </p>
              </task>
              <task>
                <p>
                  Second subsubtask.
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
                <p>
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
              </task>



              <task xml:id="deep-terminal-task">
                <statement>
                  <p>
                    Third subsubtask.
                    In interdum suscipit ullamcorper.
                    Morbi sit amet malesuada augue, id vestibulum magna.
                    Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                    Nulla at neque nisi.
                    Integer vel porta felis.
                  </p>
                  <p>
                    In interdum suscipit ullamcorper
                  </p>
                  <p>
                    In interdum suscipit ullamcorper.
                    Morbi sit amet malesuada augue, id vestibulum magna.
                    Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                    Nulla at neque nisi.
                    Integer vel porta felis.
                  </p>
                </statement>
              </task>
              <conclusion>
                <p>
                  The conclusion of the structured subtask.
                  In interdum suscipit ullamcorper.
                  Morbi sit amet malesuada augue, id vestibulum magna.
                  Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                  Nulla at neque nisi.
                  Integer vel porta felis.
                </p>
              </conclusion>
            </task>
            <task>
              <p>
                A simple task as the last subtask.
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
            </task>
            <conclusion>
              <p>
                This concludes our structured second task.
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
            </conclusion>
          </task>
          <task>
            <statement>
              <p>
                This third top-level task is intermediate in complexity,
                you are reading the <c>statement</c>,
                which is followed by more items.
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
            </statement>
            <hint>
              <p>
                One hint.
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
              <p>
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
            </hint>
            <answer>
              <p>
                First answer.
                In interdum suscipit ullamcorper.
              </p>
            </answer>
            <answer>
              <p>
                Second answer.
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
              <p>
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
              <p>
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
            </answer>
            <solution>
              <p>
                At last, the solution.
                In interdum suscipit ullamcorper.
                Morbi sit amet malesuada augue, id vestibulum magna.
                Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
                Nulla at neque nisi.
                Integer vel porta felis.
              </p>
            </solution>
          </task>
          <conclusion>
            <p>
              This is a conclusion where you could summarize the project.
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
          </conclusion>
          <postlude>
            <p>
              This postlude appears visually outside the project,
              but is authored within, to make clear its attachment to the project.
              In interdum suscipit ullamcorper.
              Morbi sit amet malesuada augue, id vestibulum magna.
              Nulla blandit dui metus, malesuada mollis sapien ullamcorper sit amet.
              Nulla at neque nisi.
              Integer vel porta felis.
            </p>
          </postlude>
        </project>
        <example xml:id="example-structured-with-task">
          <title>Notation mathématique 2</title>
          <prelude>
            <p>
              The following <tag>example</tag>,
              from Elise Desgreniers, is structured with <tag>task</tag>.
            </p>
          </prelude>
          <introduction>
            <p>
              Écrivez chacun des exemples suivants avec les conditions pertinentes.
            </p>
          </introduction>
          <task>
            <statement>
              <p>
                Soit l'ensemble <m>A=\lbrace 1,2,3,4,5\rbrace</m>.
              </p>
              <p>
                On constate que cet ensemble contient uniquement des entiers positifs allant de 1 à 5.
              </p>
              <p>
                Donc, on peut écrire <m>A=\lbrace x\mid x\in\mathbb{N}\text{ et } 1\leq x\leq 5\rbrace</m>.
              </p>
            </statement>
          </task>
          <task>
            <statement>
              <p>
                <m>\{3,6,9,12,15,\ldots,27,30\}</m>
              </p>
            </statement>
            <hint>
              <p>
                Ce sont des multiples de 3.
              </p>
            </hint>
            <answer>
              <p>
                <m>\{x\mid x=3y \text{ et } 1\leq y\leq 10 \text{ et } y\in\mathbb{N}\}</m>
              </p>
            </answer>
          </task>
          <task>
            <statement>
              <p>
                <m>\{1,3,5,7,9,11,\ldots\}</m>
              </p>
            </statement>
            <hint>
              <p>
                Ce sont des nombres impairs.
              </p>
            </hint>
            <answer>
              <p>
                <m>\{x\mid x\mod 2=1 \text{ et } x\in\mathbb{N}\}</m>
              </p>
            </answer>
          </task>
          <task>
            <statement>
              <p>
                <m>\{2,3,5,7,11,13,17,19,23,\ldots\}</m>
              </p>
            </statement>
            <hint>
              <p>
                Ce sont des nombres premiers.
              </p>
            </hint>
            <answer>
              <p>
                <m>\{x\mid x\text{ est un nombre premier positif}\}</m>
              </p>
            </answer>
          </task>
          <task>
            <statement>
              <p>
                <m>\{1,4,9,16,25,36,\ldots,961\}</m>
              </p>
            </statement>
            <hint>
              <p>
                Ce sont des carrés parfaits.
              </p>
            </hint>
            <answer>
              <p>
                <m>\{x\mid x=y^2 \text{ et } 1\leq y\leq 31\text{ et } y\in\mathbb{N}\}</m>
              </p>
            </answer>
          </task>
          <task>
            <statement>
              <p>
                <m>\{1,8,27,64,125,\ldots\}</m>
              </p>
            </statement>
            <hint>
              <p>
                Ce sont des cubes parfaits.
              </p>
            </hint>
            <answer>
              <p>
                <m>\{x\mid x=y^3 \text{ et } y\in\mathbb{N^*}\}</m>
              </p>
            </answer>
          </task>
        </example>
        <p>
          Notes or examples related to computation or technology can go in blocks of the same name.
        </p>
        <technology>
          <title>Sample Use of Sage</title>
          <p>
            This would be a good place to talk about Sage, including a cell or two.
          </p>
<sage>
<input>diff(x^4, x)</input>
<output>4*x^3</output>
</sage>
          <p>
            But you might want to describe how to use some other calculator,
            or maybe some numerical method.
          </p>
        </technology>
        <paragraphs>
          <title>A <tag>paragraphs</tag> with a <tag>project</tag> with an <tag>answer</tag></title>
          <p>
            The solutions to a project
            (and similar)
            once did not migrate to the automatically-generated solutions.
          </p>
          <project>
            <statement>
              <p>
                A simple project, no tasks, just an answer.
              </p>
            </statement>
            <answer>
              <p>
                Here's the answer we are looking for.
              </p>
            </answer>
          </project>
        </paragraphs>
      </subsubsection>
      <exercises xml:id="exercises-subsection-solo" label="exercises-subsection-solo">
        <exercise xml:id="exercise-test-number">
          <statement>
            <p>
              This is an exercise in an
              <q>Exercises</q>
              subdivision at the level of a subsubsection.
              There is no question other than if the numbering is appropriate.
              Here is a self-referential link: Exercise<nbsp /><xref ref="exercise-test-number" />.
            </p>
            <p>
              The subsubsection has no title in the source,
              so one is provided automatically,
              and will adjust according to the language of the document.
            </p>
          </statement>
          <solution>
            <p>
              This solution will migrate to a list of solutions in the backmatter.
              We include a <c>sidebyside</c> as a test.
            </p>
            <sidebyside width="30%">
              <p>
                This is a skinny paragraph which should be just 30% of the width.
              </p>
              <p>
                And another skinny paragraph which should also be just 30% of the width.
              </p>
            </sidebyside>
          </solution>
        </exercise>
        <exercise xml:id="exercise-with-tasks">
          <introduction>
            <p>
              An <tag>exercise</tag> can be structured with parts, called <tag>task</tag>.
              This is the <tag>introduction</tag>.
            </p>
          </introduction>
          <task>
            <p>
              Do this.
            </p>
          </task>
          <task>
            <p>
              And the other thing.
            </p>
          </task>
        </exercise>
      </exercises>
      <reading-questions>
        <introduction>
          <idx>reading questions</idx>
          <p>
            A set of reading questions may have an <tag>introduction</tag>,
            perhaps for preparatory explanation.
          </p>
          <p>
            If a student has logged in to the HTML version,
            then they can answer the reading questions directly in the book.
            Inline math LaTeX can be entered using <c>$</c>...<c>$</c> or <c>\(</c>...<c>\)</c> delimiters,
            and inline AsciiMath using backticks <c>`</c>...<c>`</c> as delimiters.
            Here are some `gratuitous backticks` to check that AsciiMath is only active in the answers to reading questions.
          </p>
        </introduction>
        <exercise xml:id="first-reading">
          <p>
            This is a <term>reading question</term>
            that you might have a student answer prior to a class session,
            based on reading part of the book.
            A quick glance before class can help you tailor class time to the specific needs of your students.
            The perfect reading question will reveal whether the student has read and understood the material,
            and will be difficult to answer if they have not.
            What do you think of that?
          </p>
        </exercise>
        <exercise>
          <p>
            And a second one,
            with a cross-reference to the first, as a check on numbering:
            <xref ref="first-reading" text="type-global" />.
            Reading questions are allowed to have answers,
            but providing answers misses the point of a reading question,
            and the answer knowl interacts poorly with the mechanism used to allow students to answer directly in the book.
            Do you think the schema should ban answers to reading questions?
          </p>
        </exercise>
        <conclusion>
          <p>
            And for symmetry, a <tag>conclusion</tag>.
          </p>
        </conclusion>
      </reading-questions>
      <glossary xml:id="glossary-specialized">
      <idx>glossary</idx>
      <headnote>
      <p>
        A glossary may have a <tag>headnote</tag>,
        perhaps with some explanation.
        This glossary is a specialized division within a section.
        Placement in the back matter is another option,
        see the <xref ref="glossary-backmatter" text="title" />.
      </p>
      </headnote>
      <gi>
      <title>bar</title>
      <p>
        A part of <term>foobar</term>.
        See <xref ref="foobar-defined" text="title" />.
      </p>
      </gi>
      <gi xml:id="foobar-defined">
      <title>foobar</title>
      <p>
        A synonym for the acronym <acro>FUBAR</acro>.
      </p>
      </gi>
      </glossary>
      <solutions xml:id="solutions-subsection" inline="hint solution answer" divisional="hint solution answer" project="hint solution answer">
        <title>Solutions for This Subsection</title>
        <idx><h>solutions</h><h>for a division</h></idx>
        <introduction>
          <p>
            This is an introduction,
            where you might explain that this division of this subsection contains various hints, answers,
            solutions of inline exercises,
            divisional exercises, and/or project-like blocks.
            See the source to see just how this solutions division was built.
          </p>
        </introduction>

        <conclusion>
          <p>
            And a conclusion to this solutions division,
            which may not be readily apparent as distinct from the final division's worth of solutions,
            but since it is not prefixed with a number,
            it may be different enough.
          </p>
        </conclusion>
      </solutions>
    </subsection>
    <subsection>
      <title>Theorem-Like Environments</title>
      <p>
        There are a variety of pre-defined environments in <pretext />.
        All take a title, and must have a statement.
        Some have proofs (theorems,
        corollaries, <etc />), while some do not have proofs
        (conjectures, axioms, principles).
      </p>
      <principle xml:id="principle-principle">
        <title>The Title Principle</title>
        <statement>
          <p>
            It is a fundamental principle that many elements can have a title.
            Try it and see.
            If you get better formatting,
            then it is being recognized.
            If it looks very plain,
            check the documentation and perhaps make a feature request.
          </p>
        </statement>
      </principle>
      <p>
        More precisely, <tag>theorem</tag>,
        <tag>corollary</tag>, <tag>lemma</tag>,
        <tag>algorithm</tag>, <tag>proposition</tag>,
        <tag>claim</tag>, <tag>fact</tag>,
        and <tag>identity</tag>, all behave exactly the same, requiring a statement
        (as a sequence of paragraphs)
        followed by an optional proof,
        and may have an optional title.
        The elements <tag>axiom</tag>, <tag>conjecture</tag>,
        <tag>principle</tag>, <tag>heuristic</tag>, <tag>hypothesis</tag>,
        and <tag>assumption</tag> are functionally the same, barring a proof
        (since they would never have one!).
        Definitions are an exception,
        as it is natural to place <tag>notation</tag> within<mdash />see the source for Definition<nbsp /><xref ref="definition-indefinite-integral" /> for an example.
      </p>
    </subsection>
    <subsection>
      <title>Linking Sage Cells</title>
      <idx><h>Sage cells</h><h>linking</h></idx>
      <p>
        Sage cells share their results on a per-webpage basis,
        or a per-knowl basis, so if you move to a new chapter,
        section, or subsection that happens to be on another webpage,
        your Sage computations are gone and you start fresh.
        But maybe you need some results from elsewhere.
        As an author,
        you can make an exact copy of a cell in another location by placing the code in an external file,
        which is pure text, freed from any need to format for XML processing.
        So, in particular,
        there is no need to escape ampersands and angle brackets,
        nor is there employment of the <c>CDATA</c> mechanism.
        But the real value is that there is just one version to edit,
        and any changes will be reflected in both copies.
        We demonstrate this in the sample book,
        since it has the <c>xinclude</c> mechanism in place.
        In the chapter on groups,
        find the section on Sage and then find the discussion of subgroups,
        and you will find an example of two identical Sage cells produced from one source file.
      </p>
      <p>
        You can also specify certain cells to be auto-evaluated,
        by setting the <attr>auto-evaluate</attr> attribute to <c>yes</c>.
        The resulting cell will not have a button for evaluation
        (so editing it would be pointless).
        See the source of this sample article for the two examples below.
      </p>
      <p>
        2023-08-17: support just now is for the use case of a small portion of code,
        not a huge library of helper routines.
      </p>
      <p>
        Two cells with the default language <c>sage</c>.
      </p>
<sage auto-evaluate="yes">
<input>k = 404</input>
</sage>
<sage>
<input>2*k</input>
</sage>
      <p>
        Two cells with language <c>python</c>.
      </p>
<sage language="python" auto-evaluate="yes">
<input>
k = 4112
print("Assigned an initial value to the variable k")
</input>
</sage>
<sage language="python">
<input>
k = 2*k
print(k)
</input>
</sage>
    </subsection>
    <subsection>
      <title>Hierarchy</title>
      <paragraphs xml:id="hierarchy-structure">
        <title>Structure</title>
        <p>
          This section of this article has subsections and subsubsections.
          In a book you can have chapters enclosing multiple sections.
          There is one finer subdivision,
          it is achieved with the <c>paragraphs</c> element.
        </p>
        <p>
          It is basically a sequence of paragraphs,
          where the first one gets an inline title.
          You are reading the second, and final,
          paragraph of one right now.
          It is useful for organizing very short documents,
          where numbered subdivisions might be overkill.
        </p>
      </paragraphs>
      <paragraphs>
        <title>A Second Paragraphs</title>
        <p>
          This is a second consecutive <c>paragraphs</c> element,
          so should seem related to its title,
          but distinct from the two paragraphs in the grouping with the title
          <q>Structure</q>
          immediately prior.
        </p>
      </paragraphs>
      <assemblage xml:id="assemblage-basics">
        <title>Assemblages: Collections and Summaries</title>
        <p>
          An <tag>assemblage</tag> is a collection,
          or summary, that does not have much structure to it.
          So you are limited to paragraphs and friends (<c>p</c>,
          <c>blockquote</c>,
          <c>pre</c>) and side-by-sides that do not contain captioned items
          (<c>sidebyside</c>,
          <c>sbsgroup</c>).
          The intent is that contents are not numbered,
          so cannot be cross-referenced individually,
          and so also do not become knowls.
          You may place <tag>image</tag>, <tag>tabular</tag>,
          and <tag>program</tag> inside a <tag>sidebyside</tag>,
          in addition to other objects that do not have captions.
          Note that <c>p</c> may by extension contain lists
          (<c>ol</c>,
          <c>ul</c>,
          <c>dl</c>).
          Despite limited structure, the presentation should draw attention to it,
          because the contents should be seen as more important in some way.
          It should be
          <q>highlighted</q>
          in some manner.
          If you need to connect the entire assemblage with material elsewhere,
          you can do that with the usual <c>xref/xml:id</c> mechanism.
              <idx><h>assemblage</h></idx>
        </p>
        <p>
          What have we seen so far in this (disorganized) sample?
          <ul>
            <li>
              <p>
                Theorems, definitions and corollaries. (<xref ref="section-fundamental-theorem" text="type-global" />)
              </p>
            </li>
            <li>
              <p>
                Sage cells, including with R. (<xref ref="section-sage-cells" text="type-global" />)
              </p>
            </li>
            <li>
              <p>
                Lots of document structure, like introductions and conclusions
                (next). (<xref ref="interesting-corollary" text="type-global" />)
              </p>
            </li>
          </ul>
        </p>
        <p>
          A sample table,
          as a <c>tabular</c> inside a <c>sidebyside</c> with no caption, follows.
        </p>
        <tabular>
          <row>
            <cell>A</cell>
            <cell>B</cell>
            <cell>C</cell>
          </row>
          <row>
            <cell>Uno</cell>
            <cell>Dos</cell>
            <cell>Tres</cell>
          </row>
        </tabular>
      </assemblage>
      <assemblage>
        <p>
          This is a small <c>assemblage</c> with no title,
          simply to make sure the surrounding box behaves properly,
          especially for <latex /> output.
        </p>
      </assemblage>
      <assemblage>
        <title>Assemblages containing <m>\mu \forall \tau \mathbb{H} = \emptyset \kappa</m></title>
        <p>
          It is acceptable for an assemblage to contain mathematical content,
          even in its title.
        </p>
      </assemblage>
    </subsection>
    <subsection xml:id="subsection-intro-conclude">
      <title>Introductions and Conclusions</title>
      <introduction>
        <title>An Introductory Introduction</title>
        <p>
          Any subdivision may have a sequence of paragraphs within an <tag>introduction</tag> that precedes subsequent further subdivisions.
          You are reading one now.
          They are always leaves of the document structure,
          so are rendered on some pages that reference the following subdivisions.
        </p>
        <p>
          An introduction or conclusion is an extremely restrictive container with simple presentation.
          A title is optional
          (and probably not advisable).
          Content is meant to be short and unstructured,
          in particular, nothing that can be numbered is allowed.
          If this feels <em>too</em> restrictive,
          then place your content in an initial numbered subdivision and perhaps title it
          <q>Introduction</q>. Or make your entire subdivion unstructured and place whatever you want into it.
        </p>
        <p>
          This ends this introduction to introductions.
        </p>
      </introduction>
      <subsubsection>
        <title>Test One</title>
        <p>
          An intervening subsubsection just after an introduction.
        </p>
      </subsubsection>
      <subsubsection>
        <title>Test Two</title>
        <p>
          An intervening subsection section which contains an <tag>exercises</tag> division which must be at the level of a Subsubsubsection.
        </p>
        <exercise>
          <statement>
            <p>
              An inline exercise to examine any clash with divisional exercises below.
            </p>
          </statement>
          <answer>
            <p>
              An answer so there is something to appear in a <tag>solutions</tag>.
            </p>
          </answer>
        </exercise>
        <reading-questions>
          <title>What Did You Learn?</title>
          <exercise>
            <statement>
              <p>
                A mock exercise to appease validation.
              </p>
            </statement>
            <answer>
              <p>
                An answer so there is something to appear in a <tag>solutions</tag>.
              </p>
            </answer>
          </exercise>
          <exercise>
            <statement>
              <p>
                And a second to help with formatting the division heading.
              </p>
            </statement>
          </exercise>
        </reading-questions>
        <exercises>
          <exercise>
            <statement>
              <p>
                A mock exercise to appease validation.
              </p>
            </statement>
            <answer>
              <p>
                An answer so there is something to appear in a <tag>solutions</tag>.
              </p>
            </answer>
          </exercise>
          <exercise>
            <statement>
              <p>
                And a second to help with formatting the division heading.
              </p>
            </statement>
          </exercise>
        </exercises>
      </subsubsection>
      <subsubsection>
        <title>Test Three</title>
        <p>
          An intervening subsubsection just before a conclusion.
        </p>
      </subsubsection>
      <conclusion>
        <p>
          Entirely analogous to introductions are conclusions.
          Any subdivision may have a sequence of paragraphs within a <tag>conclusion</tag> that follows previous further subdivisions.
          You are reading one now.
          They are always leaves of the document structure,
          so are rendered on some pages that reference the preceding subdivisions.
        </p>
        <p>
          This concludes this conclusion
          (and this subsection and this section).
        </p>
      </conclusion>
    </subsection>
    <subsection xml:id="subsection-paragraph-markup">
      <title>Some Paragraph-Level Markup</title>
      <p>
        Text within a paragraph may be <em>emphasized</em>
            <idx><h>em</h><h>emphasis</h></idx>
            <idx><h>styling words</h><h>em</h></idx>
            <idx><h>styling words</h><h>emphasis</h></idx>
        with <tag>em</tag> or if you want to take it to the next level you can identify the text as an
        <alert>alert</alert>
            <idx>alert</idx>
            <idx><h>styling words</h><h>alert</h></idx>
        with <tag>alert</tag>.
      </p>
      <p>
        Similarly, within a paragraph,
        you can identify edits between versions as <insert>inserted text that has been added</insert><idx><h>styling words</h><h>insert</h></idx> with <tag>insert</tag> or as <delete>deleted text that has been removed</delete><idx><h>styling words</h><h>delete</h></idx> with <tag>delete</tag>.
        Note that these identified edits are slightly different than <stale>stale text that you want to retain,
        but which is no longer relevant</stale>,
            <idx><h>styling words</h><h>stale</h></idx>
        which is accomplished with <tag>stale</tag>.
        The original request for stale text came from an instructor with an online list of student topics for presentations,
        and as students claimed topics they were marked as no longer available for other students.
      </p>
      <p>
        If you need a
        <q>fill-in blank</q>, like this <fillin />, it can be obtained with an empty <tag>fillin</tag> element that defaults to roughly a 10-character width.
        You can use the <attr>characters</attr> attribute to make the rule longer or shorter,
        such as a 40-character blank:
        <fillin characters="40" />.
        The character count is approximate,
        based on typical character widths within a proportional font carrying English language text.
        Adjust to suit,
        or request a language-specific adjustment if it is critical.
      </p>
      <p>
        This paragraph is intended to make a <tag>fillin</tag> appear right at the start of <fillin characters="20" /> the second line in print and then the next paragraph has nothing but a <tag>fillin</tag>.
        Both are for testing purposes.
      </p>
      <p>
        <fillin characters="5" />
      </p>
      <p>
        The following are <tag>fillin</tag> with <attr>rows</attr> and/or <attr>cols</attr> attributes (at least one of which is greater than 1):
        <fillin rows="2" />, <fillin cols="3" />, <fillin rows="2" cols="3" />.
      </p>
      <p>
        Long after we started this mess,
        we added <pretext /> tags to mark up tags and attributes.
        The elements are: <tag>tag</tag>,
        <tag>tage</tag>, <tag>attr</tag>.
        Examples of how these render are (respectively):
        <tag>section</tag>, <tage>hash</tage>, <attr>width</attr>.
        Perhaps this document will make greater use of these tags.
      </p>
      <p>
        We supply two provisional cross-references for testing purposes only:
        <xref provisional="a first incomplete cross-reference" />,
        <xref provisional="a second incomplete cross-reference" />.
      </p>
    </subsection>
    <conclusion>
      <p>
        A conclusion here, which we fill with some numbering tests.
      </p>
      <p>
        This is a cross-reference to one of the outcomes,
        forced to use the <c>type-global</c> form of the text.
        It should describe the outcome as belonging to the <em>section</em>
        (rather than the <em>outcomes</em>),
        since outcomes are one-per-subdivision and are numbered based upon the containing division:
        <xref ref="outcome-structure" text="phrase-global" />.
        For comparison this is the (forced) <c>type-global</c> cross-reference:
        <xref ref="outcome-structure" text="type-global" />.
      </p>
    </conclusion>
    <outcomes xml:id="outcomes-structures">
      <title>Fundamental Structures, Revisited</title>
      <introduction>
        <p>
          This is a <tag>outcomes</tag> element you are reading,
          and this is its introduction.
          This early section has really grown and we have tried to accomplish many things.
          Not all of them are listed here.
        </p>
      </introduction>
      <ol>
        <li>
          Display various
          <q>blocks</q>, fundamental units of the flow.
        </li>
        <li xml:id="outcome-structure">
          More, and this is what the cross-references above are pointing to.
        </li>
        <li>Evermore.</li>
      </ol>
      <conclusion>
        <p>
          This concludes the (incomplete) outcomes for this section,
          so now we can carry-on to the next section.
        </p>
      </conclusion>
    </outcomes>
  </section>