Re: div and p

Martin Holmes <[email protected]>
Newsgroups gmane.text.tei.general
Message-ID <[email protected]>
On 2017-01-12 07:45 AM, James Cummings wrote:

> In Marjorie's case I think the problem is not that her extra concluding
> paragraph isn't a new division or some section, but that she doesn't
> want it signalled with a heading.  With Paul's examples I would choose
> solution 1 or 4 depending on whether I thought they were a concluding
> subdivision (sans heading) or a separate section (sans heading).

This is a requirement imposed by this Schematron rule in the jTEI schema:

<constraintSpec ident="jtei.sch-div-head" scheme="isoschematron">
               <constraint>
                 <sch:rule context="tei:div[not(@type = 
('editorialIntroduction', 'bibliography', 'abstract', 
'acknowledgements'))]">
                   <sch:assert test="tei:head">
                     A <sch:name/> must contain a head.
                   </sch:assert>
                 </sch:rule>
               </constraint>
             </constraintSpec>

As you can see, we require a head element for any div which doesn't fall 
into a number of specific categories. Those types of div perform 
specific roles in the article structure. Our assumption when creating 
the schema was that the body of an academic article would conform to the 
relatively conventional structure that Michael outlined, and all the 
articles so far have, but there's no reason why we shouldn't be able to 
change it. There are implications for processing into ODT and PDF, as 
well as ingestion into the revues.org system.

Marjorie, could you raise a ticket for this on GitHub:

<https://github.com/TEIC/TEI/issues>

with [jTEI] in the title, and if possible provide us with a simple 
outline of the structure you need?

Since it'll take time to add the required support to the processing 
pathways, is there a way you can get around this temporarily that won't 
be too annoying?

Cheers,
Martin
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.