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

Re: Transformative Programming: Flow-based, functional,and mor

  • From: "Simon St.Laurent" <simonstl@simonstl.com>
  • To: "xml-dev@lists.xml.org" <xml-dev@lists.xml.org>
  • Date: Fri, 18 Oct 2013 13:05:32 -0400

Re:  Transformative Programming: Flow-based
On 10/18/13 12:09 PM, David Lee wrote:
Try calling up Google and asking them if only they would change their
Map API it would be so much easier.
And asking them to join a committee to define a schema for their API is easy?

Try calling up "The FDA" and asking if they would perhaps accept a
vendor specific change to HL7 ...
Giant bureaucracies gonna bureaucrat. For centuries paper has been capable of more than forms, and yet...

Try even calling up your business partner at "Corporation X" and
asking for the "IT Department" and seeing if they might please
change a field in the data they are sending you to something more
reasonable.
Note that I'm not describing this as a negotiation. If they're sending
you something, you get to decide how to deal with it. If the phone call
would help, you're welcome to try, but if they say no it's up to you to cope - just as it always was.

Try telling your contracted business partner that already agreed to
a fixed price implementation that you want to send a different
variant of the data and would they please process it and send a
"wafer thin" change back to you, without renegotiating a new rate.
Again, I'm not suggesting negotiation. However, I have actually done pretty much just that in the past and found people more willing to make "wafer thin" changes than you apparently expect.

For *me* schemas help solve the problem of *inherent inability* to
communicate over time, space, organization and contractual boundaries
that *preexist*.  It makes life easier for everyone involved where
otherwise it would be literally impossible to communicate.
Now _that_ is hyperbole. It's a miracle that we ever communicated before schemas!

I don't expect users and developers the world over to throw off their schema carapaces immediately. I do hope they will notice that these things are itchy, uncomfortable, limiting, and not nearly so necessary as we've been taught.

Thanks,
--
Simon St.Laurent
http://simonstl.com/



[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.