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

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-adoption message

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


Subject: Re: [dita-adoption] Action Items: 12-10-2019 Adoption TC Meeting


Hi -- I see that the DITA TC OASIS stylesheets are on the agenda. I'll try to attend in case there are any questions that I can help answer.

I hope folks are enjoying the various holidays and end-of-the-year time.

Best,
Kris

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

On 12/29/2019 12:11 PM, Dr. Stanley Doherty wrote:
====================================================
                  ACTION ITEMS
           OASIS DITA Adoption Meeting
                   12-10-2019
====================================================
Attendees: Keith, Joe, Stan, Scott, Gershon

Next meeting: Tuesday, January 7 at 12:00PM/EST
=================================================
1. https://dita.xml.org/ futures
    > Carol Geyer (Oasis) gets complaints about the site being out of date or
      dysfunctional. She is asking us what we plan to do about it long-term.
    AI/Keith - check it out.
    AI/Stan - forward emails.
2. DEMO - Scott - OASIS DITA TC stylesheets publishing plug-in and process.
    AI/Stan - QA and document it (DITA-OT)
    AI/Scott - Oxygen steps
    AI/Keith - Follow-up

3. DITA User's Guide
    Discussed audiences and skills for the UDG. Posted notes to the wiki site at:
    - https://wiki.oasis-open.org/dita-adoption/DITA_User_Guide
    The DITA Adoption TC is in the process of creating a DITA User Guide. This
    guide is designed to address the following audiences:
    * Technical writers: some brand new to DITA and XML, some familiar with
      structured authoring
    * Technical editors: some brand new to DITA and XML, some familiar with
      structured authoring
    * Senior writers/ISD: some brand new to DITA and XML, some familiar with
      structured authoring. Stubbing out the information design and maps.
      Probably many have deep product knowledge.
    * Conversion specialists: familiar with scripting and tools, XML, but might
      not know DITA inheritance/hierarchy/specialization/content models
    * Publishing specialists: familiar with style requirements, but might not
      know the DITA-OT or structures.
    AI/Stan - touch base with Jacqui about revisiting the ATC whitepaper on DITA
       roles and correlating that to UDG audiences. OPEN
    AI/Kathy - Touch base with Sabine and Brianna about user community pain points
       that came up in the CIDM DITA basics courses. OPEN
    AI/Scott - Contact Eliot Kimber re: glossary best practices. Would
       he have time to help? OPEN
    AI/Scott - Correlate the ADDIE process model to UDG roles. Capture on the wiki.
    AI/All - review and contribute -> Roles, process/tasks in each stage of development
    - Tailor the UG to address the constituent tasks
4. Whitepapers:
    a. Review Stan's June 30 email about a DITA conversion
       checklist.
       https://wiki.oasis-open.org/dita-adoption/ditaconversionchecklist#preview
       > Whitepaper check-in a few months
    b. Keith: Continue progress on "How keys should be implemented"
       whitepaper (Q3).
    c. Keith: Roll the "Future of DITA" presentation into a Spring 2020
       whitepaper.
    d. Looking ahead: What is the future of DITA/DITA 2.0 (Keith)?
       > What do I need to know to get ready for 2.0?
       > What should I prep?
       > What would a typical user/group see as changes?
       > Review in the spring as a possible whitepaper.

5. DITA migration financials: In his May 2019 email to the Adoption
    TC, Jang Graat suggested "If we would get 1 article about a -
    financially - successful DITA implementation (without any
    technical details whatsoever) into the Financial Times, it would
    have more impact on DITA adoption than writing 20 white papers
    or having 20 listening sessions (which should have been organised
    by the DITA TC and not the DITA Adoption TC if you ask me).

    I would applaud an initiative that would take the whole DITA Adoption
    group out of OASIS altogether, and I might actually join such a group.
    See it as a fanclub for OASIS (not the band) and advertise it as such.
    As it is, nobody in their right mind is gong to join OASIS just to be
    part of the adoption group, so we will be confined to the geeks who
    are already convinced about DITA and who cannot think outside of the
    DITA box to figure out what would really make a difference to DITA
    newbies."
    Is this something for which we can recruit some fresh members?
    > Migration clients - did measure investments (both tools and skills)
    > Gershon - saw ROI ahead of projections
    > Contributors:
      - Localization overhead (hit ROI much more quickly)
      - Reuse % (hit ROI much more quickly) + team productivity
      - Instructional design and writing teams collaborated - driven
        financially to reduce overhead, + single sourcing brought big ROI
    > Tasks coud be written by either team (training or ID)
      - Stretch goal - feature designers (PMs, Product Owners) could
        draft descriptions and use a concept topics
      - SMEs contributing as casual contributors = goals
    AI/Stan - move up in the agenda as a whitepaper in progress
    AI/Gershon - drive the discussion/development
    AI/All - recruit helpers/supporters/MBAs/accountants
    AI/Keith - work up some of the financial info that he has (costs just on L10N ROI)
             - Tagging the input so the TMS is DITA-aware BEFORE the DITA switch-over
               produced great results, clean slate
    AI/Gershon - write up the TM updates/setup -
    AI/wiki eventually

6. DITA samples development
    a. DITA collections
       The CIDM article on sample DITA collections is at:
       > https://www.infomanagementcenter.com/dita-collections/
    b. Keith:  Spent some more time on the Mitchell airplane manual,
       making the tables accessible. Everything is on my local
       system at this point.
    c. Scott: Run the MDITA transform when Keith posts the finished
       B-25 sample work.
    d. Stan: Build out some working content badging samples
       to support the writing in the badging whitepaper (Q3).
       > GitHub: https://github.com/StanDoherty/dita-badges	

7. Call for participation - opportunities for writing:
    a. All: Discuss developing a separate whitepaper on DITA 1.3 flagging
       best practices. Include revision marking and PDF changebar
       processing.
	
8. Parking lot items
    a. Review Scott's May 3 email on DITA/LwDITA 1.0 migration strategy.
       > How do we anticipate LwDITA evolutions?
	  > May need to update as the spec evolves.
       > Keep as an email for now; revisit late this year. 	
	  > Eventually turn it into a procedure.
	  > Wiki - migration
    b. All: Consider creating some LwDITA versions of the content?
       Word/GoogleDoc can be converted to MDITA and from there to HDITA.
	  > Whitepaper - another output type
    c. LwDITA and HTML5 alignment (XDITA)

9. DITA NA planning
    - Scott -- metrics dashboard
    - Stan - conref push
    - Gershon - next-gen publishing map (pub map)
10. Upcoming ATC meetings
     > Tuesday, January 7
     > Tuesday, February 4
     > Tuesday, March 3
     > Tuesday, April 7


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