• From: "Anders W. Tell" <anderst@t...>
• To: Paul Prescod <paul@p...>
• Date: Mon, 27 Sep 1999 11:19:17 +0200

Paul Prescod wrote:

> In your description you've renamed "values" as "leaf nodes." I don't
> think that that changes the model much. It's like the distinction
> between Python and Java. Java has "basic types" and "objects". Python
> says some objects are built-in types and others are based on
> user-defined classes. In practice the difference is small.

In this variation of the Grove concept there are also built-in types and user-defined types,
but the extra benefit is a single type system instead if two, properties:"declared datatype"
nodes:"class"

> Does that help?

Yes it does :) Now I can finish my DOM/Groove compliant API's and my binary FML v2

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...)

• References:
  • Grooves: why are "data" designed as properties and not nodes ?
    • From: "Anders W. Tell" <anderst@t...>
  • 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: "Anders W. Tell" <anderst@t...>
  • Re: Grooves: why are "data" designed as properties and not nodes ?
    • From: Paul Prescod <paul@p...>

• Prev by Date: Language that do with XML?
• Next by Date: Re: Grooves: why are "data" designed as properties and not nodes ?
• Previous by thread: Language that do with XML?
• Next by thread: How to transform only unique nodes in XSLT?
• Index(es):
  • Date
  • Thread