• From: rbourret@d... (Ron Bourret)
• To: xml-dev@i...
• Date: Fri, 22 May 1998 11:45:58 +0200

A couple of comments about the example on your Web page:

   <ELEMENT TAG="FIGURE">
   <CONTENTMODEL>IMAGE,CAPTION?</CONTENTMODEL>
   <ATTRIBUTE NAME="DESCRIPTION">
   <ATTCONTENT>CDATA</ATTCONTENT>
   <ATTREQUIRED>#IMPLIED</ATTREQUIRED>
   </ATTRIBUTE>
   </ELEMENT>

Content model should contain sub-elements, such as <ELEMENTUSE>, not text.  You 
don't want to force applications to parse text.  On the other hand, attribute 
descriptions are probably better stored in attributes:

   <ATTRIBUTE NAME = "DESCRIPTION" CONTENT = "CDATA" REQUIRED = "OPTIONAL">
   
The reason is that the possible choices are limited and work very well as 
enumerated attributes.  Note that this is what XML-Data does.  If you are 
defining some sort of XML-Data-Lite, XML-Data is probably a pretty good starting 
place.

-- Ron Bourret

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Prev by Date: Re: Proposal Announcement - XML DTDs to XML docs
• Next by Date: Re: Q: SW for parsing DTD's
• Previous by thread: Re: Proposal Announcement - XML DTDs to XML docs
• Next by thread: Re: Proposal Announcement - XML DTDs to XML docs
• Index(es):
  • Date
  • Thread