Alan, great e-mail. I am delighted that someone new is looking
critically at the DTDs.
I think at this point all your questions are answered. Like
Robert, I think @processing-role is necessary on <topicref>
elements, so that we do not break rules for specialization.
And at this point, it's time for the DITA TC to take a long and
hard work at LwDITA. Any questions can be answered there.
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)
On 6/4/2017 11:02 PM, Alan Houser
wrote:
Colleagues,
A few questions about the Lightweight DITA DTDs and LwDITA
features --
- The content model and attribute set for <data> is
different in maps and topics (content model: <data> in
<topic> allows #PCDATA; <data> in <map> does
not. And the attributes are different). Is that intentional?
- LwDITA does not provide the DITA filtering attributes? (O.K.
with me; just confirming).
- LwDITA does not provide a generic metadata container attribute
(e.g., @outputclass)?
- Should we provide @processing-role on <topicref>? I'm
thinking of the use case of referencing a "keydef-only" ditamap
(@processing-role = "resource-only").
-Alan
