[Home] [By Thread] [By Date] [Recent Entries]
hello
again - there's a benefit in wrapping the pcdata if you're trying to
enforce sequencing requirements while authoring the document; in
particular, the sequencing of the <n> and <img> elements, which
seems to be what you're going for in the original model. otherwise,
as Bjoern points out, xml will restrict you to the rules of mixed content, under
which you'll lose control of that sequencing.
From: Rita Shen [mailto:shaledova@g...] Sent: Tuesday, June 26, 2007 9:44 PM To: Kekesi, Sandor (LNG-EWR) Cc: xml-dev@l... Subject: Re: Problem with Entity parameter Hi, Sandor,
I am actrually still a bit confused by the use of PCDATA.
If I have the segment in a XML like:
<graph>it is a graph<n>sky</n>you can see it
on<img>a link</img>nice</graph>
so by using a element container for the PCDATA, it is like:
<graph><text>it is a
graph</text><n>sky</n><text>you can see it
on</text><img>a
link</img><text>nice</text></graph>
Is it right? So compared with the first solution (<!ELEMENT Graph
(#PCDATA|n|img)*>), the benifit for your solution is that in the
XML, I can have any kind of combinations among the children elements by wrapping
the text by a pair of tags (<text> and <\text>), right?
Thank you, Rita
On 6/27/07, Kekesi,
Sandor (LNG-EWR) <Sandor.G.Kekesi@l...>
wrote:
-- -------------------------------------------------------- If you give a man a fish, you feed him for a day, If you teach him to fish, you feed him for a lifetime
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |

Cart



