• From: "Rick Jelliffe" <ricko@a...>
• To: <xml-dev@i...>
• Date: Tue, 7 Apr 1998 11:12:38 +1000

From: Jim Amsden <jamsden@u...>


> I think it's best to treat this as an object modeling problem first, and
then
> an XML representation

Without going against object modeling or any other view, you should first
be aware of any constraints in XML (Len's comment) and in your immediate
software.

If your editing software makes attributes easy, then use attributes. If your
rendering/draft software does not support attributes well, use elements.
You can do a simple translation of your DTD and document to convert
from one form to another anyway. A DTD does not need to be set in stone.

A markup language has to reconcile data modeling needs and human factors,
with the latter being the most important.

Rick Jelliffe


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: When is an attribute an attribute?
• Next by Date: msxsl bug?
• Previous by thread: Re: When is an attribute an attribute?
• Next by thread: RE: When is an attribute an attribute?
• Index(es):
  • Date
  • Thread