[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: LW-DITA Target Users??
Hi --
Resetting expectations about OASIS LW-DITA with the DITA community at large is necessary. As I mentioned in the TC call yesterday, the target audience for LW-DITA needs to be clarified by the TC.
a) DITA XML authors wanting a simpler,
and yet interoperable, version of DITA.
b) Non-DITA XML content developers who are:
- Committed to using their current authoring
tools (MS Word, Confluence, Markdown)
- Interested in collaborating with the XML
DITA content developers
- Interested in leveraging the power of
DITA-based publishing and content management
Whether the target audience is a) or b), I would recommend being explicit about which interoperable lightweight markup formats OASIS LW-DITA will AND WILL NOT not support.
FWIW ... my company and others in the Boston area have been following the conference presentations on LW-DITA and hoping that it would allow the following content developers (in priority order) to participate in the fancy DITA pipelines that we have built:
a. MS Word (OfficeOpen XML)
b. Wiki (Confluence)
c. Markdown - we have that working now
d. HTML5 - not interested, not an authoring format
Without an interoperability story that involves lightweight editors and formats, the ability of silo-bound XML DITA to shape corporate standards and IA will be limited. I'd love to see XML DITA get out of its silo and had been hoping that LW-DITA was the ticket.
Selfishly -- if the goals for OASIS LW-DITA are not aligned with the business needs (a.k.a. pain points) of my organization, I'd rather know as soon as possible in order to ramp up my investment in alternate solutions.
Between the regional listening sessions and DITA Europe happening this fall, the DITA TC and the LW-DITA SC have opportunities to validate the interests and priorities that the DITA community in general might have for LW-DITA. Perhaps a sanity check is in order.
Anyway ... I support the effort to clarify the goals of the LW-DITA SC and wanted to offer some of my thoughts . . .
Stan Doherty
10-19-2016
=================================================
Subject: [dita-lightweight-dita] Re: [dita] The (many) drivers for Lightweight DITA
Date: Tue, 18 Oct 2016 20:30:53 -0400
From: Carlos Evia <cevia@vt.edu>
To: Kristen James Eberlein <kris@eberleinconsulting.com>, dita-lightweight-dita@lists.oasis-open.org
CC: DITA Technical Committee <dita@lists.oasis-open.org>
Kris and all,
I think the LwDITA SC is already working on all of these identified drivers. Of course, some are (way) more advanced than others.
Would it help if I join the main TC call 11/01 and update on our work and plans? I can have my students work on the projects (surprise: they will be working on LwDITA topics that day) while I join the call.
Best,
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 Tue, Oct 18, 2016 at 6:18 PM, Kristen James Eberlein <kris@eberleinconsulting.com> wrote:
And a critical addition:
Expanding DITA into new markets: Web developments and ones that we don't know of yet
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
On 10/18/2016 5:57 PM, Kristen James Eberlein wrote:
>
> We mentioned the following drivers on the DITA TC call today:
>
> Desire for a subset of full DITA that is less complex, simpler to author, and cheaper/easier to build tools to support
> Easier specialization
> Tooling to make easier specialization possible
> Ability to have HTML and Markdown versions to enable contribution from authors who want to author in that format
> Commitment to interoperability; Lightweight DITA must be able to be absorbed by full DITA. (The reverse is not the case.)
> Current plans for Lightweight DITA to have elements and attributes that are not available in DITA 1.3, such as <video>, <audio>, @specmodel and more
>
> Am I missing any of the key points that were raised? I think I am ...
>
> I'd encourage DITA TC voting members to think about the following:
>
> How would you rank these different drivers? Are some more important to you than others?
> Do you think that Lightweight DITA might be delivered in phases? If so, what would you want to see first?
> Do you think that some of these drivers affect each other? Or be in conflict with each other? If so, how can that be mitigated?
>
> How can we best promote discussion on the DITA TC about Lightweight DITA and where the subcommittee is currently at?
>
> Regular item on the agenda
> Survey
> Other thoughts?
>
> For folks who were on today's call but silent, I'd be happy to have calls with you.
>
> Cc'd to the Lightweight DITA subcommittee.
> --
> 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
--------------------------------------------------------------------- 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]