• From: "Anders W. Tell" <anderst@t...>
• To: xml-dev@i...
• Date: Thu, 23 Sep 1999 17:22:59 +0200

Like many others have I started to look at the Grooves model once more
and this time at little closer. Im especially interested in how my
current "DOM-compliant" model matches the Groove.
One aspect got my attention and it was that properties and not nodes
contains "data" such as strings,integer,etc.

Could somone explain the design rationale why properties and not node
carries data ?
Does this design imply that tree-algorithms are easier to implement ?
Any other aspects that benefits from this design ?

Regards Anders
--
/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
/  Financial Toolsmiths AB  /
/  Anders W. Tell           /
/_/_/_/_/_/_/_/_/_/_/_/_/_/_/



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/ and on CD-ROM/ISBN 981-02-3594-1
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...)

• Follow-Ups:
  • Re: Grooves: why are "data" designed as properties and not nodes ?
    • From: "W. Eliot Kimber" <eliot@i...>
  • Re: Grooves: why are "data" designed as properties and not nodes ?
    • From: "Christopher Travers" <ctravers@n...>
  • Re: Grooves: why are "data" designed as properties and not nodes ?
    • From: "Steven R. Newcomb" <srn@t...>

• Prev by Date: RE: RFC: Attributes and XML-RPC
• Next by Date: RE: XMLized mails (RE: We gotta break up these digests)
• Previous by thread: Re: [MAILER-DAEMON@n...: Returned mail: User unknown]
• Next by thread: Re: Grooves: why are "data" designed as properties and not nodes ?
• Index(es):
  • Date
  • Thread