Subject: Re: [jats-list] Media reference From: Mike Eden <meden@xxxxxxxxxxxxx> Date: Mon, 11 Feb 2013 16:47:03 +0000 |
Jeff, thank you for this. Wish I had read before replying to Rebecca. I think using <fig> in this case would probably be preferable and the concept of an audible figure sort of works. Thanks Mike Eden ----- Original Message ----- From: "Beck, Jeff (NIH/NLM/NCBI) [E]" [beck@xxxxxxxxxxxxxxxx] Sent: 11/02/2013 16:23 GMT To: "jats-list@xxxxxxxxxxxxxxxxxxxxxx" <jats-list@xxxxxxxxxxxxxxxxxxxxxx> Subject: Re: [jats-list] Media reference Hi Mike, I'm not sure if this is a case where we don't have enough elements to correctly cover your situation, or we have too many elements already and you have a new application that makes us a little uncomfortable to extend one of the existing ones. In JATS we have four elements that handle general article-level objects of interest: figure, table-wrap, boxed-text, and supplementary-material. They are all used to hold some named thing and the text that is associated with it. The models are the same or very similar: There is some name of the thing (<label>), and associated <caption> with a <title> and text (para-level elements). There is the thing of interest - usually <graphic> or <media> in <fig>, <table> in <table-wrap>, section-level content in <boxed-text>, and generally <media> in <supplementary-material>. But what's in it doesn't define what it is. We see figures with just text or lists, tables with graphics or just lists, and nearly anything in <boxed-text>. I suppose if we were starting fresh, we'd make an <article-level-object> element with this model and type them as figure, table, audio object, etc. But much of JATS is based on existing tagging practice, and we inherited these named article-level objects. But <graphic> can exist in body text. This is important to remember when you think about the difference between a figure and simply an image. Perhaps we need a <media-object> element added to the list of existing article level objects of interesting things that would do the same thing for <media> that <fig> does for <graphic>, but the model will wind up being the same, I would imagine. I'd say for your sound file, make the decision the same way you would decide between tagging a full-blown figure and a <graphic> in the flow of the body text. If you want to name it (Audio 1), or give it a title, or caption, then tag it as a <fig> with a @fig-type="audio" or some other indicator. <fig fig-type="audio" id="azr24a"> <label>Audio 1</label> <caption> <title>Speech speech!</title> <p>text about the speech</p> </caption> <media .../> </fig> I apologize for all of the philosophizing at the beginning of the message. Jeff On 2/11/13 8:36 AM, "Mike Eden" <meden@xxxxxxxxxxxxx> wrote: >Hi >I'm having trouble deciding how to code a media sound file that is not >supplementary material. This is for an online only title that has >reference to sound file (speech). <xref> attribute ref-type does not >include "media" or anything similar. "other" seems to be a bit loose. >Also > >it is strange that there is no over arching grouping element for this >kind > >of stand alone media. Do other users of JATS code these within <fig> (and >consider it an "audible" figure)? If so then presumably one could use >fig-type="sound-file" or fig-type="media". >I'd very much appreciate thoughts on this. > > >Mike Eden > >Operations Manager >Content Services >Cambridge University Press >Cambridge CB2 8RU >U.K. >+44 (0)1223 326435
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [jats-list] Media reference, Beck, Jeff (NIH/NLM/ | Thread | [jats-list] <*-group> elements, Kevin Hawkins |
RE: [jats-list] Media reference, Mike Eden | Date | [jats-list] <*-group> elements, Kevin Hawkins |
Month |