- From: David G. Durand <dgd@cs.bu.edu>
- Date: Sat, 28 Dec 1996 18:35:22 -0500
- To: cbullard@HiWAAY.net, "W. Eliot Kimber" <eliot@isogen.com>
- Cc: w3c-sgml-wg@www10.w3.org
At 2:35 PM 12/28/96, len bullard wrote: >No, this is not the XML standard; it is a way to discuss >the XML standard for hyperlinking in examples that a >programmer would find clear. I plead for help from >the object programmers on the list. I am one of the object programmers on this list. One of the problems I see with this is that I want to know what the data is, not how someone else thinks they should design my applications. I would be more snaguine about OO modelling of links if I had ever: A. Seen an object model for hypertext that more than the author agreed was reasonable. B. saw any proposed, meaningful applications of inheritance in defining the semantics of the two kinds of links we are considering (multi-end clink, multi-end ilink). C. any reason to apply the operational aspects (methods) of OO programming. We don't even need "set" methods in XML, so I don't see that OO field lists, with "get" methods only, are any different from simple lists of attributes. We don't need to sprinkle OO magic dust over declarative linking to make XML fly, we just need to decide on a syntax, and some simple metadata. (I think this is Gavin's model, and I'm not surprised that if this is so, we are in agreement again...) -- David I am not a number. I am an undefined character. _________________________________________ David Durand dgd@cs.bu.edu \ david@dynamicDiagrams.com Boston University Computer Science \ Sr. Analyst http://www.cs.bu.edu/students/grads/dgd/ \ Dynamic Diagrams --------------------------------------------\ http://dynamicDiagrams.com/ MAPA: mapping for the WWW \__________________________
Received on Saturday, 28 December 1996 18:29:01 UTC