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

RE: Re: What should TrAX look like? (Was: Re: Artic

• To: Dare Obasanjo <dareo@m...>, xml-dev@l...
• Subject: RE: Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• From: Prakash Yamuna <techpy@y...>
• Date: Fri, 18 Feb 2005 14:08:12 -0800 (PST)
• Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=gw58MDOCIkrgkP0wBhjeMMQJjufRezikbYsaOlxZ/9nzPXhoVp7AxyjzzKoxf+kifpbwqjWy7XA8h7lwJvlfNeRAFKbz/LiRHzoCRpO1zmzFce3HU1yOlqlzRzdeVhO8qTR6KJdlH/Rz3FaECOJ6YP9iEXJhHHzawpJihc9D4sA= ;
• In-reply-to: <830178CE7378FC40BC6F1DDADCFDD1D1043275AA@R...>

I don't think I am disagreeing with you on the benefit
it brings to the table today. I am just disagreeing on
the benefit it MAY bring in the future. [That is where
I don't quite connect with your statement on it being
similar to java.lang.Object]

Of course the thought that Source may evolve - maybe
wishful thinking on my part:-(

prakash
--- Dare Obasanjo <dareo@m...> wrote:

> > -----Original Message-----
> > From: Prakash Yamuna [mailto:techpy@y...] 
> > Sent: Friday, February 18, 2005 1:07 PM
> > To: Dare Obasanjo; xml-dev@l...
> > Subject: Re:  What should TrAX look like?
> (Was: Re: 
> >  Article on JAXP 1.3 "Fast and Easy XML
> Processing")
> > 
> > I find Source more useful - sure it is very light
> weight and 
> > has little value.
> > 
> > But what it has done is put a stake in the ground
> so to speak.
> > 
> > Everybody who implements Source will adhere to the
> interface.
> 
> What interface? If you get something that implements
> Source, all you
> know is that you can ask it for its System
> identifier. How is that a
> useful contract to enforce? I might as well just
> accept java.lang.Object
> and ask for its type which is how most APIs that
> accept Source as input
> have to work anyway. 
> 
> > This becomes very useful from an evolution
> perspective. The 
> > reason it is underspecified is a lot of models
> have disparate 
> > needs and there has been no common agreement on
> how they can 
> > expose it.
> 
> Translation: Source isn't any more useful than just
> using
> java.lang.Object
> 
> --
> PITHY WORDS OF WISDOM 
> No matter how long or how hard you shop for an item,
> after you've bought
> it, it will be on sale somewhere cheaper.   
> 
> This posting is provided "AS IS" with no warranties,
> and confers no
> rights.  
> 
>
-----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org
> <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
> 
> The list archives are at
> http://lists.xml.org/archives/xml-dev/
> 
> To subscribe or unsubscribe from this list use the
> subscription
> manager:
> <http://www.oasis-open.org/mlmanage/index.php>
> 
> 



		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250

• Follow-Ups:
  • RE: Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
    • From: "Michael Kay" <mike@s...>

• References:
  • RE: Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
    • From: "Dare Obasanjo" <dareo@m...>

• Prev by Date: RE: Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• Next by Date: RE: Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• Previous by thread: RE: Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• Next by thread: RE: Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• Index(es):
  • Date
  • Thread