Next in thread →
Next in month →
Re: [xml-dev] Problem with Entity parameter
Ok, I see. I thought the model (#PCDATA|n|img)* is equal to (#PCDATA)* or (n)* or (img)*. But it should be seen as (#PCDATA|n|img)(#PCDATA|n|img)... or nothing.
I hope I am right this time:-)
Thanks for the help,
Rita
On 6/27/07, Kekesi, Sandor (LNG-EWR) <[email protected]> wrote:
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?
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:[email protected]]
Sent: Tuesday, June 26, 2007 9:44 PM
To: Kekesi, Sandor (LNG-EWR)
Cc: [email protected]
Subject: Re: [xml-dev] 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,RitaOn 6/27/07, Kekesi, Sandor (LNG-EWR) < [email protected]> wrote:hi Rita - you could try creating an element container for the pcdata, for example:<!ELEMENT text (#PCDATA)>then your graph element might look something like this:<!ELEMENT graph ( text*, (n,text*)?, (img, text))>hope this helps.later,-s-
From: Rita Shen [mailto:[email protected]]
Sent: Monday, June 25, 2007 3:31 AM
To: Bjoern Hoehrmann
Cc: [email protected]
Subject: Re: [xml-dev] Problem with Entity parameter
Hi, Bjoern,Thanks for your reply! What shuld I do if I want to limit the exact accurrance for each sub-element in the element Gragh? I mean I want to have:0 or more "PCDATA" and "n" but 1 or more "img" in it.Cheers,syt
<!ELEMENT Graph (#PCDATA|n|img)*>
On 6/25/07, Bjoern Hoehrmann <[email protected] > wrote:* Rita Shen wrote:
>I got a problem with converting SGML DTD to XML DTD. In the converted XML
>DTD, I have the below entity definition:
>
><!ENTITY % MyText "#PCDATA">
>
>In the element Graph,
>
><!ELEMENT Graph ((%MyText;)*, (n, (%MyText;)*)?, (img, (%MyText;)
If you have mixed content you only constrain which child elements are
allowed, not the order in which they have to occur or their number:
<!ELEMENT Graph (#PCDATA|n|img)*>
See http://www.w3.org/TR/xml/#sec-mixed-content for more information.
--
Björn Höhrmann · mailto:[email protected] · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
--
--------------------------------------------------------
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
--
--------------------------------------------------------
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
Next in thread →
Next in month →