bezos stole my idea(s)
in any case, I've been turned onto the idea of podcasting, and I think it's awesome. while I do not have iPod (yet), I'll just pretend by 20+ lb. desktop system is "portable" enough to be called a podcast receiver.
so, since anyone could pretty easily decry my view that Web Services will take over the world, I'm glad I stumbled over to the best podcasting site, ITConversations, to hear Bezos re-affirm my suspicions.
in other news, Zawodny has my dream job, about which I'm sure there will someday be a reality TV show that I might utilize to usurp his lofty position. all in due time, however.</div>
PRWeb
will just have to ensure that our press releases contain the most common buzzwords used by our target audience.</div>
<binary>01110000 01110010 01101111 01100010 01101100 01100101 01101101 00111111</binary>
besides looking like poster-children for some kind of Geeks Anonymous Club, these guys (or at least Joe) think that Binary XML is not only unnecessary, but that it causes problems. the same old cookie-cutter arguments against Binary come up - human readability is better, hardware will get faster, system-wide changes in how XML is handled. not only that, but these arguments and the entire article are so simplified, it seems obvious that someone was just missing a deadline?
so, if you want some good reporting on the Binary XML argument, look to other sources. I'm not saying that I could do much better, but at least I know if I can't, I can always link to someone who can.</div>
ws-comments->pause();
I plan to return to regular posts if and when I am able to find a php web services project. as it stands now, I need to just stay on the prowl for one.
I still rely on google alerts to keep me abreast of news on XML and Web Services, and I suggest everyone else do the same.</div>

ws-comments->resume();
so the latest cool WS article I read was this one that talked about WS being used to integrate supply chains. everyone been talking about this, really, so this is just more of the same old stuff. the thing that struck me about is was how simply it describes a good example of a Business Process (Order Fulfillment) and how it can benefit from an SOA based on Web Services.
elaborating:
the article breaks Order Fulfillment into:
1. Order Management System
2. Warehouse Management System
3. Transportation Management System
since I'm on a UPS kick recently, I'll use them in an example. say you have constructed your own Order Fulfillment Business Process with a good SOA, or at least a web service-conducive wrapper. 1, 2, and 3 may be completely in-house systems, so you built them all, but you have the possibility of replacing one of the systems at any time with an external system using Web Services.
let's say you (want to) make an acquisition that changes your shipping requirements from being solely domestic road freight to being international road, flight, and boat freight. if your Order Fulfillment process is flexible as described above, you can use UPS as your TMS service for the new additions rather than write it all yourself. word on the street is that their pretty good at shipping stuff. =)