Dear Eliot, (Sorry, I was out yesterday.) At 07:08 PM 9/29/2010, you wrote:
Yes, this is not the venue to argue implementation approaches. Just pointing out that I would not bank on much future direct authoring of NLM.
Even given that that's arguable (over beer, preferably), oXygen's Authoring features are really nice for all kinds of things besides authoring directly -- I'm thinking of editorial and sub-editorial tasks, validation against house rules and house style, stuff like that. So, sure, journal article authors may persist in using word processors for a long time to come (I even have a thesis for a conference paper waiting in the wings on why that is) -- and yet support for NLM authoring could still be a strategic asset for oXygen. So to me, the question isn't so much how useful an NLM/JATS framework for oXygen would be, but how to motivate the work. I (and Mulberry) have other stuff in our kit besides CSS that could be useful for this, if anyone's interested. Just no time to do anything with it. :-) Cheers, Wendell ====================================================================== Wendell Piez mailto:wapiez@mulberrytech.com Mulberry Technologies, Inc. http://www.mulberrytech.com 17 West Jefferson Street Direct Phone: 301/315-9635 Suite 207 Phone: 301/315-9631 Rockville, MD 20850 Fax: 301/315-8285 ---------------------------------------------------------------------- Mulberry Technologies: A Consultancy Specializing in SGML and XML ======================================================================