Lightweight DITA SC

 View Only
  • 1.  Write-the-Docs assessment of strategic Markdown directions

    Posted 03-15-2016 22:02
    The title is click bait, but the article is a reasoned review of Markdown's potential faults and what the author feels is the strategic design imperative for semantic markup (possible considerations for direction for MDITA): http://ericholscher.com/blog/2016/mar/15/dont-use-markdown-for-technical-docs/ -- Don R. Day Founding Chair, OASIS DITA Technical Committee LinkedIn: donrday    Twitter: @donrday About.me: Don R. Day    Skype: don.r.day Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information? --T.S. Eliot 0 viruses found. www.avast.com


  • 2.  Re: [dita-lightweight-dita] Write-the-Docs assessment of strategic Markdown directions

    Posted 03-15-2016 22:50
    And a revealing public discussion about Eric's article, in that many pros and cons (and alternative concepts) are mentioned. For the markup geek in all of us... https://news.ycombinator.com/item?id=11292280 On 3/15/2016 5:01 PM, Don Day wrote: The title is click bait, but the article is a reasoned review of Markdown's potential faults and what the author feels is the strategic design imperative for semantic markup (possible considerations for direction for MDITA): http://ericholscher.com/blog/2016/mar/15/dont-use-markdown-for-technical-docs/ -- Don R. Day Founding Chair, OASIS DITA Technical Committee LinkedIn: donrday    Twitter: @donrday About.me: Don R. Day    Skype: don.r.day Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information? --T.S. Eliot 0 viruses found. www.avast.com -- Don R. Day Founding Chair, OASIS DITA Technical Committee LinkedIn: donrday    Twitter: @donrday About.me: Don R. Day    Skype: don.r.day Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information? --T.S. Eliot 0 viruses found. www.avast.com


  • 3.  RE: [dita-lightweight-dita] Write-the-Docs assessment of strategic Markdown directions

    Posted 03-15-2016 23:17
      |   view attached
    There is not a tool mentioned within 37 feet of that page (the discussion thread) that you would find 80% of our tech-writing customers willing or able to use to write their technical documentation. And by "our" in this case I mean XMetaL, no matter what Mark Baker may think about XML. A good tool will compensate for any sucky language.   mag       From: dita-lightweight-dita@lists.oasis-open.org [mailto:dita-lightweight-dita@lists.oasis-open.org] On Behalf Of Don Day Sent: Tuesday, March 15, 2016 3:50 PM To: dita-lightweight-dita@lists.oasis-open.org Subject: Re: [dita-lightweight-dita] Write-the-Docs assessment of strategic Markdown directions   And a revealing public discussion about Eric's article, in that many pros and cons (and alternative concepts) are mentioned. For the markup geek in all of us... https://news.ycombinator.com/item?id=11292280 On 3/15/2016 5:01 PM, Don Day wrote: The title is click bait, but the article is a reasoned review of Markdown's potential faults and what the author feels is the strategic design imperative for semantic markup (possible considerations for direction for MDITA): http://ericholscher.com/blog/2016/mar/15/dont-use-markdown-for-technical-docs/ -- Don R. Day Founding Chair, OASIS DITA Technical Committee LinkedIn: donrday    Twitter: @donrday About.me: Don R. Day    Skype: don.r.day "Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?" --T.S. Eliot   0 viruses found. www.avast.com   -- Don R. Day Founding Chair, OASIS DITA Technical Committee LinkedIn: donrday    Twitter: @donrday About.me: Don R. Day    Skype: don.r.day "Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?" --T.S. Eliot   0 viruses found. www.avast.com