Re: [jats-list] Identifying the typesetter for an article

["Tommie Usdin btusdin@xxxxxxxxxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Hi Vincent b

You ask:

>> Considering that two JATS users have identified a similar need would it
worth documenting and possibly adding to the examples in the Tag Library
(possibly under <custom-meta> and <event>)? Or would it be better to submit a
comment to propose a specific element to hold this information to be added in
a future version of JATS?

I have two thoughts:

1. This seems to me to be internal tracking information, not the sort of
content that is interchanged. So I am not sure it is within the scope of JATS.

2. Having said that, if you want to take it to the JATS Standing Committee I
think you should present the functional requirement (storing information about
typesetters/vendors) with a discussion that mentions all of these options. A
suggestion to the Standing Committee does not need to include a specific
solution as long as it is clear and includes examples.

b Tommie


> On Sep 12, 2019, at 2:21 PM, Lizzi, Vincent
vincent.lizzi@xxxxxxxxxxxxxxxxxxxx <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
wrote:
>
> Hi Julie and Tommie,
>
>
>
> I have a similar requirement to be able to identify the typesetter that
encoded the XML for an article. I also need to be able to identify subsequent
changes to the XML, for example transformations of the XML from an outside
source or from an earlier version of NLM/JATS to the current version of JATS.
This information is useful for our digital production teams to have readily
available in the metadata of the article XML. The custom-meta elements can
hold arbitrary information in key value pairs, which seemed like a good option
at first but is insufficient for our use cases. In our implementation of JATS
1.0 we used the DTD customization layer to add a custom element, which could
repeat and had attributes to hold the metadata. Currently we are upgrading to
JATS 1.2 and do not want to add custom elements so we are planning to use the
new <event> element. Here are a few examples. These are not final yet but
Ibm happy to share and get feedback.
>
>
>
> Typesetter / Prepress Vendor:
>
>
>
>             <pub-history>
>
>                 <event event-type="tagger">
>
>                     <event-desc>Perfect Typesetting</event-desc>
>
>                 </event>
>
>             </pub-history>
>
>
>
> (we used btaggerb in the attribute value but btypesetterb would be
equally good)
>
>
>
> XML Conversion:
>
>
>
>             <pub-history>
>
>                 <event event-type="provenance">
>
>                     <event-desc>Received from XYZ in NLM 2.2 format and
converted to JATS 1.2</event-desc>
>
>                     <date>
>
>                         <day>12</day>
>
>                         <month>9</month>
>
>                         <year>2019</year>
>
>                    </date>
>
>                 </event>
>
>             </pub-history>
>
>
>
> Typesetter / Prepress Vendor followed by XML conversion:
>
>
>
>             <pub-history>
>
>                 <event event-type="tagger">
>
>                     <event-desc>Perfect Typesetting</event-desc>
>
>                 </event>
>
>                 <event event-type="provenance">
>
>                     <event-desc>Converted from TF JATS 1.0 to JATS
1.2</event-desc>
>
>                     <date>
>
>                         <day>12</day>
>
>                         <month>9</month>
>
>                         <year>2019</year>
>
>                     </date>
>
>                 </event>
>
>             </pub-history>
>
>
>
>
>
> Ibd be happy to get feedback on this use of <event> or other options.
Considering that two JATS users have identified a similar need would it worth
documenting and possibly adding to the examples in the Tag Library (possibly
under <custom-meta> and <event>)? Or would it be better to submit a comment to
propose a specific element to hold this information to be added in a future
version of JATS?
>
>
>
> Thanks,
>
> Vincent
>
>
>
>
>
> Vincent M. Lizzi - Digital Production Manager
>
> Taylor & Francis Group
>
> 530 Walnut St., Suite 850, Philadelphia, PA 19106
>
> E-Mail: vincent.lizzi@xxxxxxxxxxxxxxxxxxxx
>
> Phone: 215-606-4221
>
> Fax: 215-207-0047
>
> Web: http://www.tandfonline.com/
>
>
>
> Taylor & Francis is a trading name of Informa UK Limited,
>
> registered in England under no. 1072954
>
>
>
> "Everything should be made as simple as possible, but not simpler."
>
>
>
>
>
>
>
>
>
>
>
> Information Classification: General
> From: Tommie Usdin btusdin@xxxxxxxxxxxxxxxx
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, September 12, 2019 1:15 PM
> To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [jats-list] Identifying the typesetter for an article
>
>
>
> Hi Julie b
>
> This is exactly the sort of information <custom-meta> was created to handle.
That is, it is metadata, it is important to one user but not generally
interchanged, and you want it to reside in the XML document.
>
> It seems to me that the relative costs of a slightly bulky encoding are far
less than the long-term costs of tag abuse to the value of your XML. And
frankly, the custom-meta version is not all that bulky:
>
> <custom-meta-group>
> <custom-meta>
> <meta-name>typesetter </meta-name>
> <meta-value>Typesetter here</meta-value>
> </custom-meta>
>
> b Tommie
>
> > On Sep 12, 2019, at 1:03 PM, Julie Blair julie.blair@xxxxxxxxxxx
<jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> >
> > We are using JATS Publishing v1.1d1.
> >
> > Webd like to identify the particular typesetter that encoded the XML for
an article. Unfortunately a tag for this doesnbt exist (that I know of) so
Ibm looking for alternatives.
> >
> > Ideas so far:
> >
> > Assign the typesetter an <article-id> - while easy to do, this is obvious
tag abuse.
> > <article-id pub-id-type="other">Typesetter here</article-id>
> >
> > Use of <custom-meta> - drawback of verboseness
> >
> > <uri specific-use=btypesetter-idb>Typesetter here</uri> - would this
be considered tag abuse?
> >
> > Is anyone using other structures to identify a particular typesetter?
> >
> > Thanks,
> > Julie
> >
> > ----
> > Julie Blair
> > XML Architect
> > SAGE Publishing
> > 2455 Teller Road
> > Thousand Oaks, CA 91320
> > USA
> >
> > www.sagepublishing.com
> >
> > Los Angeles | London | New Delhi
> > Singapore | Washington DC | Melbourne
> >
> > JATS-List info and archive
> > EasyUnsubscribe (by email)
>
> JATS-List info and archive
> EasyUnsubscribe (by email)