[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: PLOS blog about relative merits of XML (JATS) andHTML in w

• From: David Lee <dlee@calldei.com>
• To: "<liam@w3.org>" <liam@w3.org>
• Date: Tue, 18 Jun 2013 01:34:07 +0000

Another revenue source for publishers using XML at the core is to be able to create new products without new content.   If content is marked up intelligently and semantically and stored in a searchable document management system then new publications can be produced by "remixing" existing content.
This is very hard to do if the content is stored in print ready format.  


Sent from my iPad (excuse the terseness) 
David A Lee
dlee@calldei.com


On Jun 17, 2013, at 9:25 PM, "Liam R E Quin" <liam@w3.org> wrote:

> On Mon, 2013-06-17 at 22:43 +0100, Peter Flynn wrote:
>> On 06/10/2013 11:04 PM, Sheila M. Morrissey wrote:
>> [...]
>>> Her query If XML is being used as an interchange format only, what
>>> do we gain from moving the XML piece of the workflow any further
>>> upstream from final delivery?
>> 
>> The canonical answer is usually the ability to service multiple delivery
>> formats from a single master.
>> 
>> Plus the preservability of a plaintext self-describing file format (if
>> the document is regarded as worth preserving for posterity).
>> 
>> But publishers don't usually see either of these as a source of revenue.
> 
> Currently a lot of publishers edit in MS Word, convert to InDesign (or
> Quark), make PDF for print, then take the print file and try to turn it
> into an eBook; Amazon will even use OCR if necessary.
> 
> Some other publishers prefer to go to XML "early" (e.g. right after the
> editing in Word, or sometimes pushing it all the way to the authors by
> supplying tools), use an XML-based formatter (e.g. RenderX or Antenna
> House Publisher) to generate print, use the same XML file to generate
> ebooks/epub in multiple formats, have a higher quality product for a
> lower cost, and get to market with the ebook days, weeks or even months
> sooner.
> 
> Liam
> 
> -- 
> Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
> Pictures from old books: http://fromoldbooks.org/
> Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
> 
> 
> _______________________________________________________________________
> 
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
> 
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> 

• References:
  • PLOS blog about relative merits of XML (JATS) and HTML in workflows
    • From: "Sheila M. Morrissey" <Sheila.Morrissey@ithaka.org>
  • Re: PLOS blog about relative merits of XML (JATS) and HTMLin workflows
    • From: Peter Flynn <peter@silmaril.ie>
  • Re: PLOS blog about relative merits of XML (JATS) andHTML in workflows
    • From: Liam R E Quin <liam@w3.org>