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

Re: Lessons learned from the XML experiment

  • From: Kurt Cagle <kurt.cagle@gmail.com>
  • To: Michael Kay <mike@saxonica.com>
  • Date: Tue, 12 Nov 2013 21:41:23 -0800

Re:  Lessons learned from the XML experiment
The biggest problem with constraints that I've seen has to do with the fact that data itself, in the real world, has this very annoying tendency to morph over time. That's in great part because programmers do not think in terms of resources that evolve but data structures that represent state that is most useful to them, something that strong typing in particular has reinforced. XML was a radical departure from that model - unlike databases, where type was intrinsic, atomic, and implicit to the implementation, and binary objects, which similarly placed constraints upon type for optimization, XML was extrinsically typed, in an advisory rather than compulsory fashion. 

I think this is a lesson lost on many corporate developers who see XML only as an intermediation format from one strongly typed object to another (I've often wondered whether so much of the bad press that XML gained would have been spared if JSON had come out a few years earlier, and whether it would be JSON that would be villified as being too unwieldy as an object broker language, when the real culprit was the tendency for application developers to put too much of the business logic of an application, rather than more generic system logic, into heavyweight OOP in the first place).  

Kurt Cagle
Invited Expert, XForms Working Group, W3C
Managing Editor, XMLToday.org



On Tue, Nov 12, 2013 at 9:16 PM, Kurt Cagle <kurt.cagle@gmail.com> wrote:
+1

On Mon, Nov 11, 2013 at 4:38 PM, Michael Kay <mike@saxonica.com> wrote:
n a perfect world, we wouldn't put such constraints in our systems. However, I don't think that systems that have such constraints are "deeply broken". On the contrary, I think all human attempts to monitor, regulate, and systematize the world we live in rely on putting things into categories and labelling the categories as if they were unambiguous. Constraints saying that every company has two or more directors are typically imposed by legislators rather than IT people, and it's often IT people who have to cope with the fact that the constraints are broken (does the company cease to exist if the directors are killed in a plane crash?). We simply don't have the ability to design systems without such constraints, and a constraint language that enables us to be explicit about the constraints the system is imposing makes the system less broken than it would be if the constraints were there but not clearly articulated.



Kurt Cagle
Invited Expert, XForms Working Group, W3C
Managing Editor, XMLToday.org




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.