A Plan for Publishing Journal Articles

  1. Articles are submitted to the journal, running on OJS for example, as XHTML. This could be authored using
  2. The XHTML document is made available to reviewers, who can add notes—using Marginalia—and vote on whether to accept the article in its current form.
  3. If necessary, the XHTML document is revised, submitted as a new version and presented to the reviewers again, until it is acceptable for publication.
  4. The XHTML document is transformed to the NLM Journal Publishing format for storage and submission to external archives.
  5. XSLT transformation of the NLM XML file to semantically structured XHTML, HTML, PDF and citation export formats for reading and re-use.

Added later:

Here's some of the reasoning behind that process... Firstly, the final format for the article has to be NLM's Journal Publishing XML, because it's a very capable standard that can be transformed into all the required output formats mentioned above. The second requirement is that people are able to author articles in whatever application/document format they want. So, the article has to get from Word, OpenDocument, DocBook, MultiMarkdown, LaTeX, etc into the NLM DTD and—at the moment—the way to do that seems to be via XHTML, which all those tools can produce. Ideally, there would be a tool that could process all those formats and produce NLM-formatted XML, but that seems unlikely in the near future. More likely is that all those tools will be able to produce OpenDocument files, which might be better, but I'd say that XHTML, with constrained use of microformats-like markup, can retain just as much of the semantics of the original document as an OpenDocument file, if not more so.

So then, either by asking authors to submit XHTML or by converting their submitted documents to XHTML, the journal has one document which it needs to get reviewed. Instead of emailing it out to a few people and collating their responses manually, the review process can take place centrally, with potentially lots of reviewers (and reviewees) all able to see each other's comments (which may or may not be anonymous). Rinse and repeat until the article is accepted, convert to NLM (and make any manual adjustments if necessary) then publish to the web and/or print as required.

Comments

The HTML "is transformed" to NLM? I'd want to see a little more detail there. That's an up-translation by most standards. Those tend to consume actual human effort.

The HTML to NLM is done at the moment with XSLT and a bit of extra scripting, but you're right, it needs manual fixing too. It shouldn't be that hard though - the NLM DTD uses a fair amount of the same structure as HTML, like for tables.

Posted by: alf on May 7, 2006 2:28 AM [Reply]

I actually think it'd make more sense -- at least longer term -- to use OpenDocument and/or MS's new XML formats as THE format; nevermind lossy conversion into and out of XHTML.

Given that ODF will have real (and very good) citation and metadata support sometime fairly soon, it'd be an obvious choice. At the metadata SC, last week we were just discussing a use case where annotations could be made to external documents. It'd apply to this example.

Posted by: Bruce on May 7, 2006 10:16 AM [Reply]

I actually don't think XHTML would be lossy at all - it should be possible to retain all of the information through this step.

Posted by: alf on May 7, 2006 10:43 AM [Reply]

ODF has the advantage of being a built-in output format for OO and (one day honestly ;) for MS Word...

So does XHTML :-)

Posted by: alf on May 10, 2006 3:56 PM [Reply]

All fields are optional, email address will not be shown; no HTML, URLs are automatically hyperlinked.