Re: [dita-lightweight-dita] Thoughts on a survey

I don't think a "comprehensive list" is even possible, so I don't think we should worry about completeness. If we took 4 from each domain area that would already really help confirm our focus.  

I suggest each sub-sub-comittee suggest the top ones they were holding up as a reference. If those are off the mark then we should know. 

On 30 Jun 2016 03:07, "Michael Priestley" <> wrote:I was concerned about size/effort here
- each of the authoring roles probably have a dozen or so potential content
or deliverable types associated with them. I don't have a list handy of
what they would be.

We've got some info on type of content
as part of the authoring role  - like "policy and procedure author",
"embedded assistance author" - and there's also the question
about source and delivery formats later on.

If you'd prefer to ask a different way
(or have more questions you want added), take a swing!

Michael Priestley, Senior Technical Staff Member (STSM)
Enterprise Content Technology Strategist


From:      
 Noz Urbina <>
To:      
 Rahel Anne Bailie <>
Cc:      
 Michael Priestley/Toronto/IBM@IBMCA,

Date:      
 06/28/2016 01:45 PM
Subject:    
   Re: [dita-lightweight-dita]
Thoughts on a survey
Sent by:    
   <>

Nothing in here about deliverable types? e.g. are you
making brochures, datasheets, intranet content, product descriptions, catalogs,
white papers, app content, augmented reality, etc...?

On 28 June 2016 at 18:34, Rahel Anne Bailie <>
wrote:

I reviewed the survey and cleaned it up a bit. Here's what
I came up with:

The Lightweight DITA committee
wants to understand more about how DITA is, and could be, used inside of
organisations to manage their content more efficiently and get more benefit
from their content.
 
Using DITA allows users to
[fill in here with description of lightweight DITA]
 
1.        Which
of the following  roles are creating DITA today in your organization?
Choose as many options as apply. If possible, point us to an example by
providing a URL for each type of content you now produce using DITA.
 
[will need to have clearly-indicated
field for URLs or comments]
Content designers
Content developers
Content editors
Customer support staff
Embedded assistance authors
Help/UA authors
Marketing communicators
Policy and procedure authors
Product documentation authors
Sales people
Trainers - Non-technical
Trainers - technical 
Software Designers
Software Developers
Support staff (Pas)
Subject matter experts - non-technical
(eg marketing)
Subject matter experts - technical
Other (specify)

 
2.        In
which content areas are you considering Lightweight DITA? Choose as many
options as apply. If possible, point us to an example by providing a URL
for each type of content you would like to produce using DITA.
 
[will need to have clearly-indicated
field for URLs or comments]
Content designers
Content developers
Content editors
Customer support staff
Embedded assistance authors
Help/UA authors
Marketing communicators
Policy and procedure authors
Product documentation authors
Sales people
Trainers - Non-technical
Trainers - technical 
Software Designers
Software Developers
Support staff (Pas)
Subject matter experts - non-technical
(eg marketing)
Subject matter experts - technical
Other (specify)

 
 
3.        What
authoring tools do you use to write your content in Lightweight DITA?
Help Authoring Tool (if so,
which one)
HTML editor
JSON
Markdown
Microsoft Word
XML editor
Other (specify)

 
4.        What
delivery formats are important for your use of LW DITA?
ePub
HTML
JSON
Microsoft Word
PDF
XML
Other (specify)

 
6 - Lightweight DITA has the
following "block-level" elements [plain English definition].
Are there are elements that you would consider important to be missing
from this list? 
Figure [fig]
Footnote [fn]
List - Definition [dl]
List - Ordered (numbered [ol]
List - Unordered (bulleted)
[ul]
Multimedia - Audio [audio]
Multimedia - Video [video]
Note [note]
Paragraph [p]
Prerequisite statement [pre]
Table - Simple [simpletable]

 
[Add any missing elements.]
 
7.        Some
organisations may want to specialize (customise) Lightweight DITA for their
specific content needs. If you plan to specialize, which of the following
capabilities are must-haves?
Being able to have containers
within containers? (Nested div structures for deep containment specializations)
The ability to choose which
attributes you add to content? (Base attributes for arbitrary attribute
definition)
The ability to re-use a central
specialization (Multiple-level specialization - the ability to specialize
off other specializations, not just topic) 

 
8.        Which
of the following benefits/features of LW DITA matter to you?
Simpler XML authoring
HTML5 authoring
Markdown authoring
Easier specialization
Easier tools development
Cross-silo content sharing
Cross-silo tool sharing
Other (specify)

 
9.        If
we have questions or want more information about your answer, could we
contact you to followup? If so, please provide an email address.

-- 
Noz 

Content Strategist, www.urbinaconsulting.com
Co-Author of "Content Strategy: Connecting the dots
between business, brand and benefits", www.thecontentstrategybook.com
Landline +34
961 051 460
Mobile +34
625 467 866