OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [dita] Name for the TechComm/Technical Content spec

I second that.


Bill Burns

Content Architect | Healthwise

bburns@healthwise.org | www.healthwise.org

208.331.6917 (office)  |  208.345.1897 (fax)




From: dita@lists.oasis-open.org <dita@lists.oasis-open.org> On Behalf Of Magliery Tom
Sent: Tuesday, May 21, 2019 1:35 PM
To: Carlos Evia <cevia@vt.edu>
Cc: Scott Hudson <scott.hudson@jeppesen.com>; Debra Bissantz <dbissantz@vasont.com>; Kristen James Eberlein <kris@eberleinconsulting.com>; DITA TC <dita@lists.oasis-open.org>
Subject: Re: [dita] Name for the TechComm/Technical Content spec


*** External email: use caution ***

I find Carlos's points compelling. I vote for Technical Content.





On Tue, May 21, 2019 at 8:46 AM Carlos Evia <cevia@vt.edu> wrote:

Dear people,


I vote for Technical Content. For two reasons:

1- If we call it DITA for Technical Communication, that implies that without this package/section of the spec, DITA cannot or should not be used for technical communication. In reality, a simple DITA topic and even a LwDITA topic can do a lot for technical communication.

2- Technical communication, in industry and academia globally, means more than documentation or procedural content. 

So... I think technical communication and technical content are not the same, and DITA can work for both with or without this section of the spec. 






Carlos Evia, Ph.D.

Associate Professor of Communication

Virginia Tech

Blacksburg, VA 24061-0112





On Tue, May 21, 2019 at 11:33 AM Scott Hudson <scott.hudson@jeppesen.com> wrote:

"DITA for Technical Communication Version 2.0" works for me too.



ïOn 5/21/19, 8:24 AM, "dita@lists.oasis-open.org on behalf of Debra Bissantz" <dita@lists.oasis-open.org on behalf of dbissantz@vasont.com> wrote:

    I like "DITA for Technical Communication Version 2.0."

    Abbreviation suggestion: DITA_TC-v2.0

    Deb Bissantz | Applications Engineer
    Vasont Systems
    A TransPerfect Company
    t +1 717.793.3883
    Skype â live:dbissantz

    -----Original Message-----
    From: dita@lists.oasis-open.org [mailto:dita@lists.oasis-open.org] On Behalf Of Kristen James Eberlein
    Sent: Sunday, May 19, 2019 10:47 AM
    To: DITA TC <dita@lists.oasis-open.org>
    Subject: [dita] Name for the TechComm/Technical Content spec

    Guys, we need to decide on a name for the spec that contains CTR etc.

    I think that we've considered both "DITA for Technical Content Version 2.0" and "DITA for Technical Communication Version 2.0."

    We need to hammer this out, so that I can go ahead and request a template for OASIS. We should also decide on the work product abbreviation, which is used in the URLs and the citation format.

    Below is what is in place for DITA 2.0:

    URL (latest version):

    Work product abbreviation: DITA-v2.0


    Kristen James Eberlein
    Chair, OASIS DITA Technical Committee
    Principal consultant, Eberlein Consulting www.eberleinconsulting.com
    +1 919 622-1501; 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:

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]