The public identifier changed to XDITA because readers were understanding LwDITA as XML only.
He subcommittee has a more robust set of sample files in the GitHub repository and I plan to improve them as the TC and public review this draft of the note.
Carlos
On Sat, Jun 10, 2017 at 7:55 AM Kristen James Eberlein <> wrote:
Why the shift from "-//OASIS//DTD LW DITA Topic//EN" to
"-//OASIS//DTD XDITA Topic//EN"? In this context -- public
identifiers for XML files -- there would be no confusion re
other Lightweight DITA formats. I'd prefer "-//OASIS//DTD
LIGHTWEIGHT DITA Topic//EN".
The plugin.xml file needs to be updated. I'm not sure who
should be listed as the support person. The dita-comment list? ?
For public consumption, I'd remove the docs directory --
unless we add something something there that is geared for
public consumption, for example, directions on how to install
the plugin and work with the sample files, or info about how the
DTDs were coded.
I'd like to see a more robust set of sample files; currently
there is a DITA map and two topics. One topic --
programming-bulbs.dita - is solid, while topic-test.dita was
clearly only intended to be used while developing the DTDs. The
map references the two topics and defines a key, although the
key has no @href or variable text.
--
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--
--
Carlos Evia, Ph.D.
Director of Professional and Technical Writing
Associate Professor of Technical Communication
Department of English
Center for Human-Computer Interaction
Virginia Tech
Blacksburg, VA 24061-0112
(540)200-8201
