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: Action Items: 07-13-2021 DITA Adoption TC Meeting


Attendees: Stan, Kathy, Keith, Gershon, Kris, Jonathan, Kathryn, Peijong, Scott (ZOOM connection problem)

AI/Stan: Forward the ACM SIGDOC feedback to the entire DITA Adoption list. Encourage inactive ATC members to attend future meetings if they want to be involved in its future. 

AI/Kathy - cross-post the invitation to re-engage with the ATC in the CIDM newsletter. 

1. ACM SIGDOC discussion
  a. ACM offers a real opportunity to get DITA more
     integrated with the undergraduate curriculum. 

  b. A move to ACM would necessarily move some of 
     our focus away from DITA advocacy.

  c. Engaging with academia is good for researchers 
     and academicians, but not necessarily with our
     current audience of DITA practitioners.

  d. If ATC moves to ACM SIGDOC (or anywhere else), 
     some number of ATC functions could move to a 
     subcommittee under the DITA TC. Details on 
     maintenance of existing ATC content would be TBD.

  e. Some Âhandles for the ACM group might be:
     - Structured Information
     - Structured Documentation
     - Structured Authoring 
     - Structured Information and Content. Management

     AI/Stan - Organize a break-out meeting to chat
     about a concrete proposal to bring back to ACM
     SIGDOC. 
     Attendees = Keith, Stan, Gershon, and Kris. 

     AI/Stan - Set up a meeting with Dan (et al.) in
     ACM SIGDOC to float our proposal.

2. DITA 2.0 tech paper planning

   a. Troubleshooting: May not be ideal because the TC
      is updating diagnostics and best practices
      information.

   b. Indefinitely nesting <step> structures may be
      very attractive:
      - Without the enforcement of the current 
       steps/substeps grammar, what should 
       practitioners consider to be best practices? 

      AI/Jonathan-Peijong-Kathryn: Develop an outline
      for a <step>s tech papaer before the next ATC 
      meeting. 

      AI/Jonathan-Peijong-Kathryn: Ping Stan to put 
      the outline on the ATC agenda whenever it is
      ready.

   c. The new hazard domain may be cool  documenting
      how it intersects with the ISO standards

   d. Emphasis domain - Keith has interest.

   e. Glossary updates - Scott  interested?

   f. DITA spec topics on authoring shells - move to a
      tech paper?


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