[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Before fragmenting, fix the broken bits first

• To: david.lyon@c...
• Subject: Re: Before fragmenting, fix the broken bits first
• From: Uche Ogbuji <uche.ogbuji@f...>
• Date: Mon, 14 Feb 2005 20:09:44 -0700
• Cc: XML Developers List <xml-dev@l...>
• In-reply-to: <1108433683.42115b138df80@65.39.203.11>
• Organization: Fourthought, Inc.
• References: <830178CE7378FC40BC6F1DDADCFDD1D1041DF8DB@R...> <1108431243.6616.57.camel@borgia> <1108433683.42115b138df80@65.39.203.11>

On Tue, 2005-02-15 at 13:14 +1100, david.lyon@c... wrote:
> Uche,
> 
> Quoting Uche Ogbuji <Uche.Ogbuji@f...>:
> 
> > The API problem is certainly far more interesting, but I'm not convinced
> > the XML community as a whole can get together to fix it.  I think the
> > whole problem with DOM and SAX is that they are LCDs for all the various
> > languages and platforms interested in XML.  I think the best APIs are
> > environment-specific.  From COmega to HAXML, the right work is already
> > progressing.  Let's just keep the W3C out of it.
> 
> ok, but where does the xml api really start and where does it really
> end? that is the question...
> 
> sometimes we get fixated with the idea that there is only one
> CPU and one communications link. It might have been this way in
> the past in the Commodore 64 and PDP-11 days but it's not like
> this now and certainly won't be like this in the future either..
> 
> in those days.... the computer only extended as far as the
> the serial lines and the line printer....
> 
> now... the computer stretches right the way round the developed
> world...
> 
> so the parser is not the full extent of the api... just an
> ever diminishing part....

I'm being honest here.  I really don't understand this entire thought,
but I get the sense it's rather esoteric.  My interest is a bit more
pedestrian.


-- 
Uche Ogbuji                                    Fourthought, Inc.
http://uche.ogbuji.net    http://4Suite.org    http://fourthought.com
Use CSS to display XML - http://www.ibm.com/developerworks/edu/x-dw-x-xmlcss-i.html
Introducing the Amara XML Toolkit - http://www.xml.com/pub/a/2005/01/19/amara.html
Be humble, not imperial (in design) - http://www.adtmag.com/article.asp?id=10286
Querying WordNet as XML - http://www.ibm.com/developerworks/xml/library/x-think29.html
Manage XML collections with XAPI - http://www-106.ibm.com/developerworks/xml/library/x-xapi.html
Default and error handling in XSLT lookup tables - http://www.ibm.com/developerworks/xml/library/x-tiplook.html
Packaging XSLT lookup tables as EXSLT functions - http://www.ibm.com/developerworks/xml/library/x-tiplook2.html

• Follow-Ups:
  • Re: Before fragmenting, fix the broken bits first
    • From: david.lyon@c...

• References:
  • Before fragmenting, fix the broken bits first
    • From: "Dare Obasanjo" <dareo@m...>
  • Re: Before fragmenting, fix the broken bits first
    • From: Uche Ogbuji <Uche.Ogbuji@f...>
  • Re: Before fragmenting, fix the broken bits first
    • From: david.lyon@c...

• Prev by Date: Re: Before fragmenting, fix the broken bits first
• Next by Date: Re: Before fragmenting, fix the broken bits first
• Previous by thread: Re: Before fragmenting, fix the broken bits first
• Next by thread: Re: Before fragmenting, fix the broken bits first
• Index(es):
  • Date
  • Thread