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

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

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)