There was a bit of conversation back
in February (Eliot and Erik were contributors) about a generic <text>
element. Presumably, <text> is allowed everywhere that PCDATA
is allowed, and its content model is (PCDATA | text)*.
Eliot's message (http://lists.oasis-open.org/archives/dita/200702/msg00064.html)
comes up with a justification for a base <text> element. That
was in the context of avoiding mixed content in conjunction with <data>.
That's the part that is linked to from Proposal #12020 (http://wiki.oasis-open.org/dita/DITA_Specification_1.2_Requirements).
But lately I've seen other uses for
a <text> element, if it existed. Conref of snippets of text
where <ph> is not allowed (such as in <keyword> or <term>
or <filepath>) is something that has popped up on dita-users more
than once, and something I've needed in my day job. Proposal #12035
(collation overrides) could probably benefit from it too.
Is this latter use something that proposal
#12020 is intended to cover?
--
Deborah Pickett
Information Architect, Moldflow Corporation, Melbourne
