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

RE: constructive (was RE: Markup perspective not co

• To: "Didier PH Martin" <martind@n...>,"Simon St.Laurent" <simonstl@s...>,<xml-dev@l...>
• Subject: RE: constructive (was RE: Markup perspective not code)
• From: "Dare Obasanjo" <dareo@m...>
• Date: Sun, 4 Aug 2002 12:47:43 -0700
• Thread-index: AcI70An4KD+JbLpQRt6Hq9N1BWtW1gAHh2kf
• Thread-topic: constructive (was RE: Markup perspective not code)

I disagree with you and completely agree with Simon on this regard. 
 
Platform and implementation specific technology like how to map XML to programming language objects is the last thing that needs to go through the design-by-commitee/lowest-common denominator process that has characterized the W3C's efforts in coming up with programming language related standards. 
 
This is exactly the problem with the DOM which you rail against. One standard API for all languages regardless of whether staticlly or dynamically typed, weakly or strongly typed, garbage collected or not is bound to be insufficient many cases. Add the fact that this API will have to ignore programming idioms, design patterns and naming conventions in most of its target languages since it will just pick one means that using it will be counter-intuitive from using other APIs in these target languages. 

	-----Original Message----- 
	From: Didier PH Martin [mailto:martind@n...] 
	Sent: Sun 8/4/2002 8:59 AM 
	To: Dare Obasanjo; 'Simon St.Laurent'; xml-dev@l... 
	Cc: 
	Subject: RE:  constructive (was RE:  Markup perspective not code)
	
	

	Hi Dare,
	
	Dare said:
	Converting XML to an object hierarchy? Isn't this what Castor does for
	Java objects and .NET XML Serialization does for CLR objects? There was
	a recent article on XML.com that provides can act an introduction to XML
	data binding if you are unaware of this technology
	
	Didier replies:
	Precisely, yes I am aware of these technologies. My concern is more that
	there is no support from W3C for these technologies. Moreover, this
	needs to be advocated to developers in order that they know there exist
	an alternative to RPCs that does not require them to back to archaic
	tools. The XML.com article was a good move toward that goal.
	
	Cheers
	Didier PH Martin
	
	
	
	

• Follow-Ups:
  • Re: constructive (was RE: Markup perspective not code)
    • From: Uche Ogbuji <uche.ogbuji@f...>
  • RE: constructive (was RE: Markup perspective not code)
    • From: "Didier PH Martin" <martind@n...>

• Prev by Date: Merge docs
• Next by Date: RE: constructive (was RE: Markup perspective not code)
• Previous by thread: RE: constructive (was RE: Markup perspective not code)
• Next by thread: RE: constructive (was RE: Markup perspective not code)
• Index(es):
  • Date
  • Thread