dita-lightweight-dita — archive

[Jan Benedictus <team@fontoxml.com>]

Hi Mark, Thanks for your reply there. Just to clarify how I got to my question: I assumed -like you are stating-  that the standard does not favour the kind of system to store in. But it struck me that the text is explicitly mentioning that " LwDITA adds Markdown and HTML * for authoring*  ", which may be understood that it does not allow (of favour) to store in topics in either .md or .html ? Jan Jan Benedictus - CEO t   +31 70 3191923 ·    m   +31 6 144 82 303 e   team@fontoXML.com ·    w   FontoXML.com s   LinkedIn ·    s   Twitter 2017-02-08 5:37 GMT+01:00 Mark Giffin < mark@markgiffin.com > : Hi Jan, Thanks for the comments! I had one response below. On 2/7/2017 3:20 AM, FontoXML - Jan Benedictus wrote: 2.2 Support for non-XML formats "LwDITA adds support for structured authoring in HTML5 and Markdown" --> My question: Only in authoring or also in storage (and publishing for that matter?). Question also relates to 4.2.x The subcommittee has not discussed storage of lwdita topics, that I can recall. I assume it is completely open to any way someone might want to store the topics: in a source control system like GitHub, Subversion, Perforce, etc.; or in a CCMS or just about anything else. The standard will not cover this. The same goes for publishing. Because lwdita will be based on full DITA, it should be easy to use lwdita topics and maps in existing DITA publishing tooling. There is already a Markdown plugin that enables you to use md topics with the DITA Open Toolkit. In some cases you might have to do some conversion of lwdita to get it into XML format to access existing tooling, but it should be easy to do that. You should also be able to do things like publish your MDITA topics with a static site generator like Jekyll, without much trouble. The standard will not cover this. Mark Giffin Mark Giffin Consulting, Inc. http://markgiffin.com/