Re: [dita-lightweight-dita] Promised rewrite

[Kristen James Eberlein <kris@eberleinconsulting.com>]

You can specialize with LwDITA; it's just that there is no special way to do it.

Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)

On 5/22/2017 10:59 AM, Carlos Evia wrote:

I like it very much. I think we should at to the core goals a list item talking about content sharing and collaboration across formats, shouldn't we?

And should we have a disclaimer about specialization in the second bulleted list?

Carlos

-- 

Carlos Evia, Ph.D.

Director of Professional and Technical Writing

Associate Professor of Technical Communication

Department of English

Center for Human-Computer Interaction

Virginia Tech

Blacksburg, VA 24061-0112

(540)200-8201

On Mon, May 22, 2017 at 10:24 AM, Kristen James Eberlein <kris@eberleinconsulting.com> wrote:

Some comments interspersed ... Please note the paragraph and list highlighted in blue. This is what we need to agree on, flesh out, and ensure that drive though the document,

2 Why Lightweight DITA?

LwDITA is a proposed specification for expressing simplified DITA documents in XML, HTML5, and Markdown.

The core goals of LwDITA are the following:

• Provide a simpler DITA experience
• Provide representations of LwDITA in XML, HTML5, and Markdown that enable individuals to author content in whatever representation is their preference
• Enable the growth of new tools and applications that support LwDITA

LwDITA offers the core features in the DITA standard:

• Semantic tagging
• Topic orientation
• Content reuse
• Conditional publishing
• Specialization

However, LwDITA deliberately limits itself to generic structures that are highly applicable across many industries. This results in a much smaller standard in terms of elements, attributes, and complexity.

This pragmatic design has benefits for both small and large projects, as well as new and existing DITA implementations. The learning curve for LwDITA will be shorter. Implementing LwDITA might involve less change management and so lower costs. The ability for engineers to author in Markdown, marketing writers in HTML5, and technical authors in DITA will enable collaboration across divisional silos.

Of course, LwDITA users who decide that they need a richer set of features and functionality for their content can easily transition to full DITA.

--
Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)

--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php