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: Agenda: DITA Adoption TC Meeting - 12-10-2019


==================================================== 
          DITA Adoption Meeting Agenda 
                  12-10-2019 
                 12:00PM/EST
==================================================== 
JOIN WEBEX MEETING

https://janainc.my.webex.com/janainc.my/j.php?MTID=m978d0fb491508acc07c17b46bab683f5

Meeting number (access code): 626 534 289
Meeting password: oasis
Host key: 171563

Phone: +1-510-338-9438 USA Toll
 
=================================================
1. 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. 
   AI/Kathy - Touch base with Sabine and Brianna about user community pain points
      that came up in the CIDM DITA basics courses.
   AI/Scott - Contact Eliot Kimber re: glossary best practices. Would
      he have time to help?
   AI/Scott - Correlate the ADDIE process model to UDG roles. Capture on the wiki.
	  

2. Whitepapers:
   a. Source format: The ATC resolved to source whitepapers in DITA.
   b. Publication templates: The ATC resolved to use the same formatting
      and transforms as the TC. 
      AI/Scott - provide  demo of the TC stylesheet/transform at the 
         next ATC meeting.
   c. 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
   c. Keith: Continue progress on "How keys should be implemented" 
      whitepaper (Q3).
   d. Keith: Roll the "Future of DITA" presentation into a Spring 2020 
      whitepaper.

3. DITA samples development
   a. DITA collections
      AI/Stan - Complete the CIDM article on sample 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. Scot: 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	 

4. Looking ahead: What is the future of DITA/DITA 2.0 (Keith)?
    a. What do I need to know to get ready for 2.0? 
    b. What should I prep? 
    c. What would a typical user/group see as changes?
    d. Review in the spring as a possible whitepaper.


5. Opportunities for writing:
   a. All: Discuss developing a separate whitepaper on DITA 1.3 flagging 
      best practices. Include revision marking and PDF changebar 
	  processing.
   b. 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? 
	  
	  
6. 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)
  
7. 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]