[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Agenda: DITA Adoption TC Meeting - 03-03-2020
====================================================
DITA Adoption Meeting Agenda
03-03-2020
12:00PM/EST
====================================================
JOIN ZOOM MEETING
https://oracle.zoom.us/my/stan.doherty
- Computer access: https://oracle.zoom.us/my/stan.doherty
- Phone access: 669-900-6833 (try one, then the other)
646-558-8656
- Meeting-ID: 605 085 6159#
=================================================
TEAM ACTION ITEMS
- AI/TEAM - Review the updated PDF for Stan's draft of the How-to
doc on installing the TC stylesheets on DITA-OT.
- AI/TEAM: Review and update the list of vendor-related issues
to discuss with the relevant vendors at DITA conferences.
Coordinate with TC.
> https://wiki.oasis-open.org/dita-adoption/ATC-conference-planning
- AI/TEAM - Review the roles that Scott posted to our wiki. Identify and add
specific tasks that each of these roles would perform in a general
DITA workflow.
> https://wiki.oasis-open.org/dita-adoption/DITA_User_Guide
- AI/TEAM - Prep for a discussion of group document review options.
INDIVIDUAL ACTION ITEMS
- AI/Keith: Prep the discussion for next meeting on Adoption Subcommittees.
- AI/Keith-Stan: Write up a how-to about submitting content to xml.dita.org.
Encourage awareness and engagement.
- AI/Kris - send contact info about P. to Keith.
- AI/Stan - Respond to Alan Houser -- we are supportive, but not able
to commit to the panel at present.
- AI/Kathy - Touch base with Sabine and Brianna about user community pain points
that came up in the CIDM DITA basics courses.
- AI/Stan - Regenerate the How-to doc using the TC stylesheet.
- AI/Stan - Post the updated PDF to Kavi and snd an email to the list.
- AI/Stan - Forward feedback from Scott McGrath re: OASIS policies
regarding use an open OASIS standard on a piece of proprietary
layered software.
- AI/Stan - forward to the ATC links to Keith's Boston DITA Users
Group presentation on DITA futures.
- AI/Gershon - prep updates/discussion of DITA migration financials
- AI/Stan - Update the agenda for the next ATC meeting to reflect:
1. Review of roles/tasks for the DITA Users Guide (Scott).
2. Adoption Subcommittees - futures (Keith).
3. DITA migration financials (Gershon).
4. TC stylesheets and ATC whitepapers.
5. Document review options.
6. Whitepaper updates.
1. DITA User's Guide (Scott)
>>> Review the roles/tasks for DUG.
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. OPEN
AI/Kathy - Touch base with Sabine and Brianna about user community pain points
that came up in the CIDM DITA basics courses. OPEN
AI/Scott - Contact Eliot Kimber re: glossary best practices. Would
he have time to help? OPEN
AI/TEAM - Review the roles that Scott posted to our wiki. Identify and add
specific tasks that each of these roles would perform in a general
DITA workflow.
> https://wiki.oasis-open.org/dita-adoption/DITA_User_Guide
AI/Stan - Touch base with Alan Houser about his request for ATC members
to participate in a panel discussion about DITA workflows. Does that
correlate to this workflow work?
2. Adoption SC futures (Keith)
- DITA Adoption Focus Area Subcommittee
- DITA Adoption Help Subcommittee
- DITA Adoption Asia Subcommittee
3. DITA migration financials (Gershon)
> Migration clients - did measure investments (both tools and skills)
> Gershon - saw ROI ahead of projections
> Contributors:
- Localization overhead (hit ROI much more quickly)
- Reuse % (hit ROI much more quickly) + team productivity
- Instructional design and writing teams collaborated - driven
financially to reduce overhead, + single sourcing brought big ROI
> Tasks coud be written by either team (training or ID)
- Stretch goal - feature designers (PMs, Product Owners) could
draft descriptions and use a concept topics
- SMEs contributing as casual contributors = goals
AI/Gershon and Keith - get together offline to shape this
project.
AI/Gershon - drive the discussion/development
AI/All - recruit helpers/supporters/MBAs/accountants
AI/Keith - work up some of the financial info that he has (costs just on L10N ROI)
- Tagging the input so the TMS is DITA-aware BEFORE the DITA switch-over
produced great results, clean slate
AI/Gershon - write up the TM updates/setup -
AI/wiki eventually
4. Whitepaper authoring / stylesheets:
> PDF: https://www.oasis-open.org/apps/org/workgroup/dita-adoption/download.php/66664/bookmap_atc_install-tc-stylesheets.pdf
> Sources: https://www.oasis-open.org/apps/org/workgroup/dita-adoption/download.php/66663/atc_install-tc-stylesheets_02.zip
AI/Stan - Touch base with Scott McGrath about OASIS policies regarding
documenting how to use an open OASIS standard on a piuece of
proprietary layered software. To be specific:
> Can we document how to use Oxygen to generate whitepapers?
> Would we need to document the same for XMetaL and Framemaker/DITA?
AI/TEAM - Identify vendor-related issues to discuss with the relevant
vendors at DITA North America, e.g. willingness to get a trial license
for editors or processors.
5. Document review options (discussion)
6. Whitepaper updates
a. 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
b. Keith: Continue progress on "How keys should be implemented"
whitepaper (Q3).
c. Keith: Roll the "Future of DITA" presentation into a Spring 2020
whitepaper.
AI/Stan - forward to the ATC links to Keith's Boston DITA Users
Group presentation on DITA furures.
d. Looking ahead: What is the future of DITA/DITA 2.0 (Keith)?
> What do I need to know to get ready for 2.0?
> What should I prep?
> What would a typical user/group see as changes?
> Review in the spring as a possible whitepaper.
e. Stan: Complete the conversion of the badging whitepaper
files in Markdown to DITA 1.3.
7. https://dita.xml.org/ futures
> Carol Geyer (Oasis) gets complaints about the site being out of date or
dysfunctional. She is asking us what we plan to do about it long-term.
AI/Keith - review the emails forwarded by Stan and check it out.
8. DITA 2.0 / LwDITA adoption planning
AI/Gershon (I believe) - brainstorm about topics that should be
included in an Adoption whitepaper about "What do I need to do
to get ready for DITA 2.0?"
AI/Stan - Touch base with Zoe about her current outline for the
DITA TC Migration Guide.
AI/TEAM - Develop a list of questions for vendors about their
plans for adopting/supporting DITA 2.0 and LwDITA in 2021.
AI/Scott - Engage the LwDITA SC about their current plans for
developing or supporting a LwDITA Migration Guide.
> Is there some automation involved with migrating
DITA 1.3 content to LwDITA?
9. DITA samples development
a. DITA collections
The CIDM article on sample DITA collections is at:
> https://www.infomanagementcenter.com/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. Scott: 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
10. Call for participation - opportunities for writing:
a. All: Discuss developing a separate whitepaper on DITA 1.3 flagging
best practices. Include revision marking and PDF changebar
processing.
11. 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)
12. DITA NA planning
- Scott -- metrics dashboard
- Stan - conref push
- Gershon - next-gen publishing map (pub map)
13. Upcoming ATC meetings
> Tuesday, April 7
> Tuesday, May 5
> Tuesday, June 2
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]