Subject:Defining a DTD element content model that contains #PCDATA and child elements Author:Jean Farnsworth Date:24 Feb 2005 10:17 AM
I'm not clear on how Stylus Studio accommodates mixed content models in DTDs, if at all. I have several elements in my DTD that require a definition that includes both #PCDATA and a whole list of inline elements, all optional and in no particular order. The DTD training I have had suggests defining an entity for #PCDATA, and then using that entity within ELEMENT declarations rather than #PCDATA. I've done that. My XML editor has no problem with this, but Stylus Studio doesn't like it and (incidentally), neither does our transformation software. Any suggestions? I can send you the DTD if you need it.
Subject:Re: Defining a DTD element content model that contains #PCDATA and child elements Author:Alberto Massari Date:24 Feb 2005 11:40 AM
the XML specs requires mixed content to be defined using this structure
(#PCDATA | child1 | child2 | child3)*
You can use a parameter entity like %PC; instead of #PCDATA, but the final
result must be this (#PCDATA must be the first item, and there must be no
extra parenthesis or '?' after a child element name).
If you already followed these guidelines please post (or send me by e-mail)
the DTD in question.