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: Breaking 'Technical Content' specializations into two groups

I like this approach, primarily because it corrals the technology specializations. Is there a more descriptive term for the more general modules? âUtilityâ seems ambiguous. or perhaps thatâs the point.


Bill Burns

Content Architect | Healthwise

bburns@healthwise.org | www.healthwise.org

208.331.6917 (office)  |  208.345.1897 (fax)


Healthwise helps people make better health decisions.


From: dita@lists.oasis-open.org <dita@lists.oasis-open.org> On Behalf Of Chris Nitchie
Sent: Tuesday, July 10, 2018 10:15 AM
To: dita@lists.oasis-open.org
Subject: [dita] Breaking 'Technical Content' specializations into two groups


*** External email: use caution ***

As I mentioned on the call today, Iâm suggesting that we break out the general-purpose modules currently labeled âTechnical Contentâ from the more industry-specific domains also included in that package. Hereâs how Iâd organize it:


General-purpose âutilityâ modules, not particularly bound to any industry, vertical, or classification:

  • Concept
  • Reference
  • Task/General Task/taskreq domain
  • Glossary-related domains
  • Bookmap (and/or the new DITA 2.0 bookmap)
  • Abbreviation domain
  • Release management domain
  • Troubleshooting domain
  • SVG Domain


More specific, technology-related specializations:


  • Equation domain
  • Markup and XML Mention domains
  • MathML domain
  • Programming domain
  • Software domain
  • UI Domain



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