[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: DOM and Grove
Hi Len, These are words of wisdom Len. What we re-discover is that history repeats itself and that sometimes (or should I say often) humanity is slow to learn from its mistakes. regards Didier PH Martin mailto:martind@n... http://www.netfolder.com -----Original Message----- From: owner-xml-dev@i... [mailto:owner-xml-dev@i...]On Behalf Of Len Bullard Sent: Thursday, September 09, 1999 1:36 PM To: Paul Prescod Cc: xml-dev@i... Subject: Re: DOM and Grove Correct. Not just possible; it's happening. This is precisely what the IETM community faced in the late eighties and early nineties. The answer was to convert everything to HTML to get the job done. Now they have to convert again. Every time that is done, the costs recur and the information gets a little more damaged. While it is hard on some to understand terms like "notation", it is vital to understand what Paul is saying. This is where everything stopped. This where CALS broke down. This is where the war was lost and the shaky structure known as the World Wide Web emerged a winner because no two ISO committee heads could agree. Study the history of CGM. Look at the relentless duplication of the effort of SGML for reasons I still cannot fathom. Note how SGML was blamed. Look at what is happening in other notations being invented today for graphics. Note the deliberate duplication of effort spent trying to keep separate syntaxes. Note how XML is blamed. Study groves. Write the simplified explanations if you need them. You do need them. len >Paul Prescod wrote: > > The real reason groves were invented was > to answer the question: > > * what is the result of hyperlinking into an arbitrary media type? > > What are the properties of the abstract object returned? The grove > answers that question: the object has properties such as "parent", > (possibly null), "children" (possibly null), "containing entity" and so > forth. > > You cannot build a sophisticated hypertext system without answering that > question. This will become apparent after XLink, XPointer and RDF are > implemented. We'll start to see many divergences of behavior when links > are made into (e.g.) PDF, MPEGs, JPEGs and so forth. Over time we will > need to develop a framework for describing the correct results of links > in a generic way. Then we will reinvent groves. > > Or not... we could keep doing things in an ad hoc manner for ever I > suppose. It would be expensive and inefficient but it is possible. 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...) 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...)
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|