Re: [dita-adoption] Agenda: 11-06-2018 DITA Adoption TC Meeting

====================================================
          DITA Adoption Meeting Agenda
                  11-06-2018
                 12:00PM/EST
====================================================
JOIN WEBEX MEETING
https://jana.webex.com/jana/j.php?MTID=m501b8a0841f803565df902f63a4a1245
Meeting number (access code): 621 002 452 Host key: 533367

JOIN BY IPHONE ONE-TAP
tel:+1-650-479-3208,,*01*621002452%23%23*01* Call-in toll number (US/Canada)

JOIN BY PHONE
1-650-479-3208 Call-in toll number (US/Canada)

Can't join the meeting? Contact support here:
https://jana.webex.com/jana/mc

IMPORTANT NOTICE: Please note that this Webex service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. You should inform all meeting attendees prior to recording if you intend to record the meeting.

==============================================
ACTION ITEMS
================================================

1. Sample source wiki
   > https://wiki.oasis-open.org/dita-adoption/ditaSourceSets
   > AI/Stan - Run a query through github.com for additional
     DITA-based sources.
   > AI/Keith - Keep on truckin' with the Strunk Elements of
     Style conversion.

2. Update our listening session planning boilerplate to include:
   > Encouragements to attendees to look at the latest, improved
     versions of specs.
   > Request specifics (perhaps as follow-up) on anything that people
     see as inadequate.
   > Do impromptu polls with the groups -- test how widely a particular point is
     shared across attendees.

3. DITA markup examples in DITA Specs
   > AI/Stan - include this topic in future agendas.
   > IDEA - consider developing a companion DITA example site
     al la HTML5 example sites. Separate from DITA specs.
   > IDEA - develop a topic about how to test/use examples in the
     DITA specs. For example, if the example is a fragment and
     the content model context is not explicit, should the fragment
     be pasted by default into a generic topic <body> for testing?
   > PUZZLE - example placement in the DITA specs? why so frequently
     at the end of the topic? why not progressive in tandem with the
     spec explanation.
   > IDEA - explore what an example set would look like if it were
     focused on features or tasks instead of XML elements. The example
     for <fig> doesn't exercise how someone actually uses <fig> with
     callouts etc..
     - https://github.com/oasis-tcs/dita/blob/DITA-2.0/specification/langRef/base/fig.dita
   > IDEA - test each spec example and identify opportunities for collaboration and
     improvement. Not just throwing rocks.

4. Examples / samples by industry
   > AI/Keith - touch base with Leigh about posible samples/donations from
     medical market.
   > AI/Scott - touch base with Maria Essig and Bill burns about posible
     samples/donations from medical market.
   > AI/Stan - touch base with NANTHealth and Waters about posible
     samples/donations from Boston-area medical market.
   > AI/Stan - set up a wiki page for industry-specific samples.

5. Whitepapers
   a. Keith - "How keys should be implemented" whitepaper.
   b. Stan - DITA badging.
   c. Stan - quantifying obstacles to reuse.

6. DXO backfill

7. AI/Stan - ATC meeting logistics:
   - Update the OASIS meeting calendar/notifications
   - Send an email to the ATC list re: new meeting cadence
     and fall dates.
     > Tuesday, November 6
     > Tuesday, December 4
     > Tuesday, January 8 /* change */
       Tuesday, January 15 ????
     > Tuesday, February 12

dita-adoption message