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: REMINDER: Adoption TC Meeting Today at 12:00PM/EST


==================================================== 
          DITA Adoption Meeting Agenda 
                  07-09-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 Scott's May 3 email on DITA/LwDITA migration strategy.
   b. Review Stan's June 30 email about a DITA conversion
      checklist. 
   
2. DITA samples development
   a. Keith: Finish up the B-25 sample work.
   b. Keith: Contact Chet about moving the B-25 content from the 
      DITAWriter repo to the OASIS repo.
   c. Scott: Re-run the MDITA transform for the B-25 content.	  
   d. Stan: Update the wiki on sample documentation sets based on 
      research completed for the April 2019 CIDM conference.
	  > https://wiki.oasis-open.org/dita-adoption/ditaSourceSets
   e. All: Consider creating some LwDITA versions of the content? 
      Word/GoogleDoc can be converted to MDITA and from there to HDITA. 
   f. Keith: Work up a internal pitch -- "how not to bomb with DITA".

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 woud this guide be different from the spec? from 
	     existing books?
      b. WebHelp for every element (a la DocBook Definitive Guide)
	  c. Look at flow in existing books?
      d. Mashup integrated with the spec content?  	  

4. Opportunities for writing:
   1. Stan: Consider working up a CIDM article on DITA sample doc sets.
   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. Stan: Replay to Jan Gollner re: his issues with scoped keys 
      in our whitepaper.
   2. 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?
   3. Keith: Continue progress on "How keys should be implemented" 
      whitepaper (Q2).
   4. Stan: Build out some working content badging samples to support the 
      writing in the badging whitepaper.
      > GitHub: https://github.com/StanDoherty/dita-badges	 
	  
6. Parking lot items
  
7. Upcoming ATC meetings
   > Tuesday, August 6   
   > Tuesday, September 3
   > Tuesday, October 1 
   > Tuesday, November 5    
	  


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