dita — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
RE: [dita]
Hi Jeff, Eliot,
If <ph> is allowed as the child of every element that allows PCDATA, that would of course work. But I suspect that there are far-reaching consequences of opening up the content model of some elements that currently allow text but not <ph>. <ph> can contain inline images, for instance, which might not be desirable. Do we allow <ph> inside <data>? That brings in a lot of other markup too. This could be avoided if a lightweight element like <text> were used instead. Since <text> can contain no child elements other than more <text> (and the usual bits like <data>), there's no possibility of escape. But I don't feel strongly about the particulars of implementation.
It would be interesting to see if the constraints proposal could help here.
I leave open the question of whether it is desirable or useful to let <text> be specialized further.
--
Deborah Pickett
Information Architect, Moldflow Corporation, Melbourne
[email protected]
| "Ogden, Jeff"
<[email protected]>
16/08/2007 01:18 AM |
|
Sounds as if <ph> should be a specialization of <text>. We are probably trapped by the past, however.
I wonder of <text> should be a specialization of anything or just a new addition to the base element set for topics and maps.
-Jeff
From: Eliot Kimber [mailto:[email protected]]
Sent: Wednesday, August 15, 2007 8:55 AM
To: [email protected]
Subject: RE: [dita] <text> element (#12020)
“text” is a specialization of phrase that serves two purposes:
1. Allows content model constraints (e.g., (data, text) rather than (data | ph))
2. Makes the semantic clear (i.e., just a container of PCDATA with no other meaning or presentation expectation
Cheers,
E.
----
W. Eliot Kimber
Senior Solutions Architect
Really Strategies, Inc.
512 554 9368
From: Ogden, Jeff [mailto:[email protected]]
Sent: Wednesday, August 15, 2007 7:49 AM
To: [email protected]; [email protected]
Subject: RE: [dita] <text> element (#12020)
What is the difference between <ph> and <text>? Are both needed?
-Jeff
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]