Re: [jats-list] Preferred pronouns for authors

["Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

If you agree that all proposals brought forth so far are more or less 
kludges, you might be interested in how they address it in TEIland: 
https://github.com/TEIC/TEI/issues/2010
This is not to suggest that JATS do the same, but maybe someone can draw 
inspiration from their discussion.

Gerrit



On 21.09.2020 15:08, Nikos Markantonatos nikos@xxxxxxxxxx wrote:
> Thanks, Martin.
>
> <suffix> would be the preferred encoding only if we consider pronouns to 
> be part of the official/legal name. This is because <suffix> is part of 
> the actual contributor name. However, since I think that this is not the 
> case so far for pronouns, <author-comment> is perhaps a preferable 
> encoding.
>
> Nikos
>
> On 9/21/20 3:12 PM, Latterner, Martin (NIH/NLM/NCBI) [C] 
> latternm@xxxxxxxxxxxxxxxx wrote:
> > Hi!
> > Just to throw another option into the mix: I think I'd just use 
> > <suffix>. Preferred pronouns may or may not be a name part in 
> > legal/official terms. However, just looking at how people use them, 
> > <suffix> seems the most appropriate to me.
> > Martin
> >
> > -----Original Message-----
> > From: Randall, Laura (NIH/NLM/NCBI) [E] laura.randall@xxxxxxx 
> > <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
> > Sent: Monday, September 21, 2020 6:47 AM
> > To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
> > Subject: Re: [jats-list] Preferred pronouns for authors
> >
> > Hi, all.
> > I share Nikos's concerns on the proposed solutions. I like the 
> > <author-comment> solution best, though you'd need to add a <p> for 
> > validity.
> >
> > <contrib contrib-type="author">
> > B B B B B B  <string-name>
> > B B B B B B B B B  <surname>Isobe</surname>
> > B B B B B B B B B  <given-names>M.</given-names>
> > B B B B B B  </string-name>
> > B B B B B B  <author-comment 
> > content-type="pronouns"><p>they/them</p></author-comment>
> > </contrib>
> >
> > Best,
> > Laura
> >
> > ________________________
> > Laura Randall (she/her)
> > laura.randall@xxxxxxx
> > 1-301-435-0467
> > NCBI/NLM/NIH
> >
> > -----Original Message-----
> > From: Nikos Markantonatos nikos@xxxxxxxxxx 
> > <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
> > Sent: Monday, September 21, 2020 4:58 AM
> > To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
> > Subject: Re: [jats-list] Preferred pronouns for authors
> >
> > Hi all.
> >
> > I feel uneasy on most suggestions made so far for the contributor 
> > pronouns issue:
> >
> > 1) The name-alternatives proposal implies that the pronouns are 
> > another alternative name for the contributor, which is far from being 
> > true
> >
> > 2) The named-content solution suggests that the pronouns are part of 
> > the contributor's actual name, which is semantically not true
> >
> > 3) The role solution is certainly preferable than the other two, but 
> > it is still a semantic stretch, suggesting that pronouns are a 
> > contributor role. According to the JATS documentation, role is "title 
> > or role of a contributor to a work", which is far from what pronouns are.
> >
> > At Atypon we were presented with this problem from a client two months 
> > ago and we opted for encoding this as an author-comment, which is a 
> > child of contrib (like role) is repeatable, takes on @content-type 
> > attribute to designate its semantic use, takes on @xml:lang attribute 
> > to allow for multiple languages and according to the JATS 
> > documentation "the <author-comment> element can also act as an escape 
> > mechanism, to take the content of any contributor-related elements not 
> > anticipated by the Suite."
> >
> > So here's another proposal for these pronouns:
> >
> > <contrib contrib-type="author">
> > B B B B B B  <string-name>
> > B B B B B B B B B  <surname>Isobe</surname>
> > B B B B B B B B B  <given-names>M.</given-names>
> > B B B B B B  </string-name>
> > B B B B B B  <author-comment content-type="pronouns">they/them</author-comment>
> > </contrib>
> >
> > Nikos
> >
> >
> > On 9/20/20 2:30 AM, Lizzi, Vincent vincent.lizzi@xxxxxxxxxxxxxxxxxxxx 
> > wrote:
> > > Hi Mark, Tommie, and Gerrit,
> > >
> > > I think that the role element could be used to hold authors' personal
> > > pronouns with a content-type attribute value to semantically identify
> > > the text as pronouns.
> > >
> > > <contrib contrib-type="author">
> > >
> > > B  B B B  <name>
> > >
> > > B  B B B B B B B  <surname>Isobe</surname>
> > >
> > > B  B B B B B B B  <given-names>M.</given-names>
> > >
> > > B  B B B  </name>
> > >
> > > B  B B B  <role content-type="pronouns">they/them</role>
> > >
> > > </contrib>
> > >
> > > If your desired display format is to have the personal pronouns
> > > displayed after the author's name, e.g. "M. Isobe /(they/them)/", and
> > > your rendering displays the <role> element immediately following the
> > > contributor name (as some renderings do) tagging personal pronouns in
> > > <role> like this might "just work". The same display could be also be
> > > achieved with the tagged example above and styling applied by the
> > > rendering (perhaps with CSS).
> > >
> > > <role content-type="pronouns"><italic>(they/them)</italic></role>
> > >
> > > The <role> element also has the advantage of being able to be repeated
> > > with different xml:lang attribute values in case personal pronouns
> > > need to be presented in more than one language.
> > >
> > > Best,
> > >
> > > Vincent
> > >
> > > _____________________________________________
> > >
> > > *Vincent M. Lizzi*
> > >
> > > Head of Information Standards | Taylor & Francis Group
> > >
> > > vincent.lizzi@xxxxxxxxxxxxxxxxxxxx
> > > <mailto:vincent.lizzi@xxxxxxxxxxxxxxxxxxxx>
> > >
> > >
> > > Information Classification: General
> > >
> > > *From:* Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx
> > > <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
> > > *Sent:* Friday, September 18, 2020 4:33 PM
> > > *To:* jats-list@xxxxxxxxxxxxxxxxxxxxxx
> > > *Cc:* Tommie Usdin <btusdin@xxxxxxxxxxxxxxxx>
> > > *Subject:* Re: [jats-list] Preferred pronouns for authors
> > >
> > > Hi Tommie and Mark,
> > >
> > > Both approaches seem sensible to me. Maybe use @content-type instead
> > > of @specific-use on string-name in Mark's variant.
> > >
> > > The JATS standing committee might consider adding @pronouns to name
> > > and string-name, should someone file a request for that. An attribute,
> > > on the other hand, has the disadvantage that it cannot hold
> > > translations so well. On the other hand, I haven't seen anyone supply
> > > translations to their pronouns.
> > >
> > > In any case, the recommended practice(s) within the existing
> > > vocabulary can be included in the tag library documentation, or it can
> > > be dealt with on the JATS4R level 
> > > (https://jats4r.org/authors-and-affiliations).
> > >
> > > Gerrit
> > >
> > > On 18.09.2020 22:06, B Tommie Usdin btusdin@xxxxxxxxxxxxxxxx
> > > <mailto:btusdin@xxxxxxxxxxxxxxxx> wrote:
> > > B  > Hi Mark --
> > > B  >
> > > B  > If you are using Green (archiving) you could use <named-content>
> > > inside <string-name>:
> > > B  >
> > > B  > <contrib contrib-type="author">
> > > B  > <string-name><given-names>>m</given-names> <surname>Isobe</surname>
> > > > <named-content content-type="pronouns">they/them</named-content>
> > > B  > </string-name></contrib>
> > > B  >
> > > B  > That's a little awkward, but perhaps less so than a
> > > name-alternative that contains only the pronouns.
> > > B  >
> > > B  > -- Tommie
> > > B  >
> > > B  >
> > > B  >> On Sep 18, 2020, at 3:55 PM, Mark Doyle doyle@xxxxxxx
> > > <mailto:doyle@xxxxxxx> <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx
> > > <mailto:jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>> wrote:
> > > B  >>
> > > B  >> Hi all,
> > > B  >>
> > > B  >> Our editors would like to allow authors to specify preferred
> > > pronouns in their manuscripts. Although the initial goal is to provide
> > > this in a footnote for just the corresponding author, I'd like to tag
> > > this in a more general way that would allow any author to add this to
> > > their name. So far the best option I have been able to work out is to
> > > slightly misuse the <name-alternatives> tagging:
> > > B  >>
> > > B  >> <contrib contrib-type="author">
> > > B  >> <name-alternatives>
> > > B  >> <name>
> > > B  >> <surname>Isobe</surname>
> > > B  >> <given-names>M.</given-names>
> > > B  >> </name>
> > > B  >> <string-name
> > > specific-use="preferred-pronouns">they/them</string-name>
> > > B  >> </name-alternatives>
> > > B  >> </contrib>
> > > B  >>
> > > B  >> Does anyone have a better suggestion for how to handle this?
> > > B  >>
> > > B  >> Best,
> > > B  >> Mark
> > > B  >>
> > > B  >> Mark Doyle
> > > B  >> American Physical Society
> > > B  >> JATS-List info and archive
> > > B  >> EasyUnsubscribe (by email)
> > > B  >
> > > B  >