Re: [jats-list] How/When do you produce a JATS-XML version of you publication within your publication workflow

["Beck, Jeff (NIH/NLM/NCBI) [E]" <beck@xxxxxxxxxxxxxxxx>]

All content that comes to PMC goes through a conversion to (currently)
NISO JATS 1.0 XML tagged according to the PMC XML Tagging Style.

PMC does not require content be submitted in NLM or JATS, but there is a
requirement that whichever article model is used for the source it is rich
enough to support a conversion to JATS and it is used consistently.

I could imagine an application of XHTML that was enriched enough with
class attribute values to carry the information needed to support a
conversion to JATS, but the content would have to be tightly controlled by
a validation layer well beyond DTD validation of XHTML on both the sending
and receiving ends. I can IMAGINE it, but I've not yet seen it in
practice, and I hope no one feels inspired to do try this.

If you or anyone has further questions about PMC, let's take them off this
list and onto the PMC list. You can direct them to pmc@xxxxxxxxxxxxxxxxx

Jeff

On 10/23/12 12:46 PM, "Kelly, Laura (NIH/NLM/NCBI) [E]"
<kelly@xxxxxxxxxxxxxxxx> wrote:

>Cute...but no. :)
>
>________________________________________
>From: eaton.alf@xxxxxxxxx [eaton.alf@xxxxxxxxx] On Behalf Of Alf Eaton
>[lists@xxxxxxxxxx]
>Sent: Tuesday, October 23, 2012 12:44 PM
>To: jats-list@xxxxxxxxxxxxxxxxxxxxxx
>Subject: Re: [jats-list] How/When do you produce a JATS-XML version of
>you publication within your publication workflow
>
>On 23 October 2012 17:25, Kelly, Laura (NIH/NLM/NCBI) [E]
><kelly@xxxxxxxxxxxxxxxx> wrote:
>>>A big question, though, is whether PubMed Central would be willing to
>>>archive content when the body of the document is in a format other
>>>than JATS XML (possibly in a separate, accompanying file).
>>
>> No, we aren't.
>>
>> There have been cases where we've accepted metadata plus PDF for
>>filling in back content of data that has committed to sending us
>>full-text XML for current articles, but we won't accept non-XML or
>>non-SGML (we do accept non-JATS XML and even SGML) content for current
>>data.
>
>XHTML?