[nylug-talk] What do non-programmers get out of XML?

[Henning Follmann]

Michael Bacarella wrote:
> RFCs are really useful documents.
> 
> They're clear, to the point, and speak in real world
> terms.  They're seem written by programmers for programmers.
> While they're very specific, they're also good at being language
> and platform agnostic.
> 
> Unfortunately, all of the protocol specifications I get
> nowadays are XML/DTD treatises, and they're just never as
> clear as RFCs.  Someone must find them useful for something,
> because it's had too much staying power to be a fad.
> 
> I just don't understand.  What's the value?  They can't hire
> non-programmers to write them and save money, because a specification
> written by a non-programmer would be hopeless.  And I can't imagine
> these already written specifications being of any use to non-programmers.
> 
> If they're programmer -> programmer communications, why the abstraction?
> What am I missing?
> 


Welcome to the world of webservices.

But I have to admit that I did sent out WSDLs in the past. But these are 
not design specifications these are contracts for using a service and 
you can use tools to create a program to consume these services. But the 
protocol is defined by SOAP Version 1.2 Part 0,1,2. The WSDL only 
defines a instance.

Or are we talking about something else? BEEP?


Henning

-- 
Henning Follmann           | hfollmann at itcfollmann.com
it consultant              | www.itcfollmann.com