AGENDA: 08-06-2019 DITA Adoption TC Meeting

["Dr. Stanley Doherty" <stan@modularwriting.com>]

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

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

Meeting number (access code): 626 894 281 
Host key: 699477 
Meeting password: oasis

JOIN BY PHONE
+1-510-338-9438 USA Toll
 
=================================================
1. Document reviews:
   a. Review Stan's June 30 email about a DITA conversion
      checklist. 
      https://wiki.oasis-open.org/dita-adoption/ditaconversionchecklist#preview
   
2. DITA samples development
   a. Keith: Finish up the B-25 sample work.
      - Added the <desc> and <alt> elements + accompanying text. 233 images.
	  - Left: Make the tables accessible (1.3 markup).
   b. Keith: Contact Chet about moving the B-25 content from the 
      DITAWriter repo to the OASIS repo.
	  > No problem - make the request, transfer, describe, ACL (ATC).
	  > Model this for other projects.
	  > Approved. 
   c. Scott: Re-run the MDITA transform for the B-25 content.
      > Reran on 6-5; will rerun.
	  > Easier to run it before the move to the OASIS repo. 
   d. Keith: Work up a internal pitch -- "how not to bomb with DITA".
      > Blog draft form

3. DITA User's Guide
   1. Keith: Apply the proposed DITAUsers' Guide template for DITA 
      commands to the <strong>/<em> DIA 2.0 proposal.
	  
   2. Discuss: 
      a. How would this guide be different from the spec? from 
	     existing books?
		 - Working examples - how does something work? 
      b. WebHelp for every element (a la DocBook Definitive Guide)
	  c. Look at flow in existing books?
      d. Mashup integrated with the spec content?  	  
	  e. ADD - wiki page for DUG.
	     > Come up with DITA 2.0 examples first.
		 > DITA 1.3 examples with issues.
		 > GOAL: List candidates for features examples.

4. Opportunities for writing:
   1. Stan: Consider working up a CIDM article on DITA sample doc sets.
      > In progress.
   2. All: Discuss developing a separate whitepaper on DITA 1.3 flagging 
      best practices. Include revision marking and PDF changebar 
	  processing.
   3. All: Explore the role that <set> could play in DITA 2.0.

5. Whitepapers :
   1. Discuss: Whitepaper submission process.
      a. Is it a requirement to source ATC whitepapers in DITA?
	  b. If so, by what process do we put content into some 
         whitepaper-ready DITA structure?
      c. If not, is publishing whitepaper content via OASIS-generated
         Word docs sufficient?
   2. Keith: Continue progress on "How keys should be implemented" 
      whitepaper (Q3).
   3. Stan: Build out some working content badging samples to support the 
      writing in the badging whitepaper (Q3).
      > GitHub: https://github.com/StanDoherty/dita-badges	 
	  
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
  
  
7. Upcoming ATC meetings
   > Tuesday, September 3
   > Tuesday, October 1 
   > Tuesday, November 5