Re: [jats-list] Rendering expectations for footnote markers in the text flow

["Piez, Wendell A. (Fed) wendell.piez@xxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Hello Gerrit and list,

What Ken says is consistent with what I have also seen.

It might be one of those cases where doing it the easy way sometimes is harder
than doing it the hard way all the time.

Paradoxical, I know! Fortunately we have Schematron and XSLT - and XProc - to
help us either way.

Cheers, Wendell

-----Original Message-----
From: G. Ken Holman g.ken.holman@xxxxxxxxx
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, May 15, 2024 2:28 PM
To: jats-list@xxxxxxxxxxxxxxxxxxxxxx; jats-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [jats-list] Rendering expectations for footnote markers in the
text flow

I've seen this in STS for years, and early on I stopped dropping an inline
citation of the footnote's label at the footnote use.

Doing so is in harmony with what I see a lot of in ISO publications where
footnotes in a table also would not expect to be dropping an inline citation:

<table-wrap-foot>
<fn id="table-fn_201.105_1"><label><sup>a</sup></label><p>The volume...

Such footnotes are simply identified semantically and so are rendered in the
table in a smaller font. No other behaviour would be expected here.

And for footnote groups as well which are rendered as end-notes. No footnote
citation would be expected there as it is simply identified semantically.

So I drew the conclusion that in the body of the document a footnote is simply
identified semantically and so is rendered at the bottom of the page in a
smaller font. So, likewise, no other behaviour would be expected.

So, in no case do I drop a footnote citation derived from <fn>'s <label>.

I think this comparison supports the behaviour, thus requiring the author to
create their own footnote citation in advance of the footnote declaration.

I hope this helps.

. . . . . . Ken

At 2024-05-15 12:17 +0000, Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx
wrote:
>Hi,
>
>In an STS document I stumbled across this use of a footnote in the text
>flow with an immediately preceding xref to it:
>
><xref ref-type="fn" rid="fn_1"><sup>1</sup></xref><fn id="fn_1">
>   <label><sup>1</sup></label>
>   <p>Available from website: <uri>...</uri>.</p> </fn>
>
>In our renderer, there was a duplicated footnote marker in the text
>flow. This is because we treat footnotes outside of fn-groups similarly
>to DocBook's footnote [1]:
>
>>Processing expectations
>>The footnote element usually generates a mark (a superscript symbol or
>>number) at the place in the flow of the document in which it occurs.
>>The body of the footnote is then presented elsewhere, typically at the
>>bottom of the page.
>
>Looking at the STS documentation [2], I'm not so sure any more. In the
>first tagged sample, there is an fn in a paragraph that is preceded by
>an explicit xref that points to the fn and that contains the footnote
>number, 1. (Interestingly, the fn doesn't contain a label -- does this
>mean that the marker superscript 1) will only be rendered in the text
>flow, not in the footnote itself?)
>
>But this STS example seems to corroborate the explicit use of an xref
>for creating the footnote marker in the text flow.
>
>However, in the JATS blue Tag Library documentation [3], the prose and
>the tagged samples "Author notes" and "<article-title>" seem to imply
>that fn elements in the text flow need not be referenced by an xref
>that contains the marker. The prose says:
>
>>... each footnote reference is marked by a number or symbol, and the
>>text of the footnote is prefixed by the same number or symbol to help
>>the reader associate the text with its reference(s)
>
>This seems to imply that a marker be generated in the text flow (or
>taken from the label if it exists), which to me contradicts the STS example.
>
>I could not find best practice recommendations regarding footnotes on
JATS2R.
>
>How do y'all handle this in your content and renderers? Posting this to
>jats-list since this is an overarching issue. If the best practice for
>STS deviates from the best practice for JATS, it should be explicitly
>mentioned on niso-sts.org. But what is the best practice?
>
>Gerrit
>
>[1]
>https://tdg.d/
>ocbook.org%2Ftdg%2F5.2%2Ffootnote&data=05%7C02%7Cwendell.piez%40nist.go
>v%7Ce5af1a3fda044b69298708dc750cc55e%7C2ab5d82fd8fa4797a93e054655c61dec
>%7C0%7C0%7C638513944915343367%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM
>DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=xB
>Cvn1tvqpg%2BLYSYAfg8qoyZN29L%2B0boy46wB%2FFS74I%3D&reserved=0
>[2]
>https://niso-/
>sts.org%2FTagLibrary%2Fniso-sts-TL-1-2-html%2Felement%2Ffn.html&data=05
>%7C02%7Cwendell.piez%40nist.gov%7Ce5af1a3fda044b69298708dc750cc55e%7C2a
>b5d82fd8fa4797a93e054655c61dec%7C0%7C0%7C638513944915352953%7CUnknown%7
>CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC
>I6Mn0%3D%7C0%7C%7C%7C&sdata=b%2B%2B%2B85%2BOHOagVJCy7TNt%2F2NiKsZy54C0X
>8ZNtgfvdFE%3D&reserved=0 [3]
>https://jats/.
>nlm.nih.gov%2Fpublishing%2Ftag-library%2F1.3%2Felement%2Ffn.html&data=0
>5%7C02%7Cwendell.piez%40nist.gov%7Ce5af1a3fda044b69298708dc750cc55e%7C2
>ab5d82fd8fa4797a93e054655c61dec%7C0%7C0%7C638513944915359686%7CUnknown%
>7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXV
>CI6Mn0%3D%7C0%7C%7C%7C&sdata=ILWhxvu5vIoVsje6m5jtAgQ7Kh509vh1LiMs7v3i09
>o%3D&reserved=0
>


--
Contact info, blog, articles, etc. http://www.cranesoftwrights.com/j/ | Check
our site for free XML, XSLT, XSL-FO and UBL developer resources | Streaming
hands-on XSLT/XPath 2 training class @US$125 (5 hours free) | Essays (UBL,
XML, etc.) http://www.linkedin.com/today/author/gkholman |