[jats-list] Encoding QR data in JATS/NISO-STS

Subject: [jats-list] Encoding QR data in JATS/NISO-STS
From: "G. Ken Holman g.ken.holman@xxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 23 Feb 2024 15:46:56 -0000
Hey, folks! I hope everyone on the list is well.

In our publishing flow I described at JATSCon:

https://www.ncbi.nlm.nih.gov/books/NBK591971/#_d1e181_

... we convert authored JATS or NISO-STS and massage it into a version of JATS or NISO-STS for downstream use, including our own publishing of PDF and HTML. Our clients then make the massaged XML available to their clients if needed.

A client has asked for a QR code on the cover sheet, and I cannot find explicit guidelines for this in the library documentation.

As I have implemented it today, I ask the authors to put a placebo in place in the metadata that I fill with the QR image data for downstream publishing and distribution. And it works just fine. But I would appreciate a design review, please, on the use of JATS/NISO-STS.

So this from the author:

<self-uri content-type="qr" xlink:href="...some-uri..."/>

... becomes this downstream:

  <self-uri content-type="qr" xlink:href="...some-uri..."
>data:image/png;base64,iVBORw0oA...qr-image-for-some-uri...AAhEUgAA</self-uri>

If there is more than one, then specific-use= can direct me regarding where the QR code goes in the cover sheet:

  <self-uri content-type="qr" specific-use="commenting"
            xlink:href="...some-uri..."/>

  <self-uri content-type="qr" specific-use="purchase"
            xlink:href="...some-other-uri..."/>

... and I will populate both with QR image data in the creation of the downstream NISO-STS. Recipients have the image data at hand if they want it, and they have the URI at hand regardless. I think this covers the bases, but I haven't seen element content with image data before.

Have others approached the encoding of QR code data in JATS before?

If so, how have you done it?

If not, would you accept the way I have implemented it?

Thank you for your thoughts!

. . . . . . . Ken

--
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 |

Current Thread