I recommend canceling this month as well. Hopefully June will be a bit easierâ
Thanks,
--Scott
From:
Keith Schengili-Roberts <keith.roberts@ixiasoft.com>
Date: Monday, May 6, 2019 at 9:52 AM
To: Scott Hudson <scott.hudson@jeppesen.com>, "Dr. Stanley Doherty" <stan@modularwriting.com>, "dita-adoption@lists.oasis-open.org" <dita-adoption@lists.oasis-open.org>
Subject: Re: [dita-adoption] Agenda: 05-07-2019 DITA Adoption TC Meeting
With Stan and Scott sending regrets for tomorrow's meeting, am thinking it might be worthwhile to postpone things until the next scheduled meeting time for June. Is that okay with everyone
else?
Speaking for myself, have been too busy on work/life projects of late, so sadly I have no updates to add.
Cheers!
Senior DITA Content Strategist
825 Querbes, Suite 200,
MontrÃal, QuÃbec, Canada, H2V 3X1
From: dita-adoption@lists.oasis-open.org <dita-adoption@lists.oasis-open.org> on behalf of Scott Hudson <scott.hudson@jeppesen.com>
Sent: May 3, 2019 2:17:06 PM
To: Dr. Stanley Doherty; dita-adoption@lists.oasis-open.org
Subject: Re: [dita-adoption] Agenda: 05-07-2019 DITA Adoption TC Meeting
For my action item, here's what I recommend to migrate content from DITA to mdita (markdown):
1. In oXygen, run the markdown transform on the ditamap, which converts the DITA to markdown.
For some reason, it outputs all the files with .html extensions, even though the content is in markdown.
Rename the files to have .md extensions
2. Another approach:
Run an XHTML transform on the map to convert the files to XHTML
Install pandoc and run the XHTML to Markdown conversion
Hope this helps!
Best regards,
--Scott
On 5/3/19, 11:54 AM, "dita-adoption@lists.oasis-open.org on behalf of Dr. Stanley Doherty" <dita-adoption@lists.oasis-open.org on behalf of stan@modularwriting.com> wrote:
====================================================
DITA Adoption Meeting Agenda
05-07-2019
12:00PM/EST
====================================================
JOIN WEBEX MEETING
https://janainc.my.webex.com/janainc.my/j.php?MTID=m9aeb6bb0f6fb53925d2cc2cb44ced177
Meeting number (access code): 622 073 393
Host key: 699477
Meeting password: oasis
====================================================
Regrets: Stan
1. Listening session support materials (Stan/Kathy)
> DONE. Kathy and Stan met and concluded that we should not invest in
additional or updated listening session materials until we know
that additional listening sessions are happening.
2. DITA samples development -- progress
- All: Review the Mitchell B-25 sample DITA collection at:
-
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_DITAWriter_pilot-5Ftraining-5Fmitchell-5Fbomber&d=DwIGaQ&c=P3aKjizb3qsxp0SERaL2sw&r=YQWdLfM9mekBOdoMmoBdn9RgyqIHrveGolBbb4_uGWQ&m=e5ZbqV0u2sv5lSQv0fPMIJH2Resei5nIiAMnDoOD4Gw&s=x8AhFsF_bG4JGt-J6d5Q0s-JV-OWKXWGbFKiZF4uzto&e=
Identify enhancements to improve and extend its usefulness.
- All: Consider creating some LwDITA versions of the content?
Word/GoogleDoc can be converted to MDITA and from there to HDITA.
- AI/Scott -- Recommend paths for sample content to get to LwDITA.
Provide different avenues to the same content. Best-practice examples
needed. Especially DITA 1.3 to LwDITA.
- Keith - internal pitch -- how not to bomb with DITA
3. Whitepapers - in progress
- Keith: Continue progress on "How keys should be implemented" whitepaper (Q2).
- Stan: Build out some working content badging samples to support the
writing in the badging whitepaper.
> GitHub:
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_StanDoherty_dita-2Dbadges&d=DwIGaQ&c=P3aKjizb3qsxp0SERaL2sw&r=YQWdLfM9mekBOdoMmoBdn9RgyqIHrveGolBbb4_uGWQ&m=e5ZbqV0u2sv5lSQv0fPMIJH2Resei5nIiAMnDoOD4Gw&s=OihPl_3upHwLt7eJe7rA39T9JYcXSLI3a6AMLUBCjXo&e=
- Stan: Continue progress on the first draft of "DITA Migration
Best Practices for Small Teams".
> GitHub:
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_StanDoherty_dita-2Dmigration-2Dbest-2Dpractices&d=DwIGaQ&c=P3aKjizb3qsxp0SERaL2sw&r=YQWdLfM9mekBOdoMmoBdn9RgyqIHrveGolBbb4_uGWQ&m=e5ZbqV0u2sv5lSQv0fPMIJH2Resei5nIiAMnDoOD4Gw&s=DmbvGVVXurHxwEWJsZYguq7qaFt_2YJS0fGIbLDeSdk&e=
4. Proposed activities (testing, whitepapers, etc.)
- TBD: Explore adding badges to the B-25 content.
> Task-based: Emergencies, landing, other systems
> Role-based: Pilot, navigator, gunner, engineer
- Joe: Touch base with the large truck manufacturer about sample
content -- as appropriate. Keep them in mind. Later next quarter.
- All: Discuss developing a separate whitepaper on DITA 1.3 flagging
best practices. Include revision marking and PDF changebar processing
- All: Explore the role that <set> could play in DITA 2.0.
- Stan: Test scoped keys with DITA-OT 3.2.1 (3.3.1) DONE
- Stan: Test branch filtering with DITA-OT 3.2.1 (3.3.1) DONE
- TBD: DITA Users Guide -- discuss/flesh out --
> How different from the spec? from existing books?
> WebHelp for every element?
> a la DocBook Definitive Guide
> Look at flow in existing books?
> Mashup integrated with the spec content?
5. DITA North America Recap
6. Jan Goller feedback on scoped keys whitepaper
- All: Review Jan's comments.
7. Update to the "Open Source DITA Collections" wiki page (Stan)
>
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.oasis-2Dopen.org_dita-2Dadoption_ditaSourceSets&d=DwIGaQ&c=P3aKjizb3qsxp0SERaL2sw&r=YQWdLfM9mekBOdoMmoBdn9RgyqIHrveGolBbb4_uGWQ&m=e5ZbqV0u2sv5lSQv0fPMIJH2Resei5nIiAMnDoOD4Gw&s=Pz535NhP57cPPHDQKIWQb7fT6G2ob-shM7bEZHXFwhY&e=
> OK to update/supplement based on the testing that I did for CIDM NA?
8. Whitepaper sources and submission process (Stan)
> Is it a requirement to source ATC whitepapers in DITA?
> If so, by what process do we put content into some
whitepaper-ready DITA structure?
> If not, is publishng whitepaper content via OASIS-generated
Word docs sufficient?
9. Upcoming ATC meetings
> Tuesday, June 4
> Tuesday, July 2
> Tuesday, August 6
> Tuesday, September 3
|