Error 404--Not Found |
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:10.4.5 404 Not FoundThe server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. |
| That's one of my other questions. How do you see XML factoring into your e-commerce plans? Quinn: Clearly the most exciting thing that's happened on the data standards, messaging side of healthcare in the last several years is the concept of using XML as a mechanism for transport, definition of data, and with the addition of XSL [Extensible Stylesheet Language], the ability to maintain the integrity of presentation format across the network as well. So we're not just moving parsed data, we're also moving format [instructions] so that the order the data is presented in by the original producer of the document is maintained. Those all combined together have made XML basically the keystone of serious work now being done on how we actually move entire patient records around between institutions. Ragunas: In the Staples case, we're looking to deploy XML for a couple of strategic projects. As we grow, particularly in the area of providing services to our small business customers, which is a key focal area for us, this is a great way for us to integrate relatively quickly and in a standardized way with third-party partners that are providing services to our customers. We can use it to integrate shopping cart information, for example. So if somebody's ordering something on a third-party site, we could bring that transaction back into our Staples.com shopping cart, so you're creating an integrated shopping experience for the customer. There are things of that nature as well as integrating with other third parties, like procurement systems, that are out there already making use of this technology. Grim: We just launched the American Express B2B Commerce Network. As part of it, we're offering to deliver purchase orders to suppliers via basic fax, XML, as well as an e-fax and an e-mail. But most suppliers are not enabled to accept XML yet. So we've got to make sure that we create the supporting infrastructure for people. Any other concerns regarding XML? Quinn: From the healthcare side, primarily just the pace of development and getting it sooner rather than later into a shape where we all agree on what the structures are. Ragunas: In our space, part of the concern is working through some of the standards issues around exactly how you communicate. What are the standard transactions that are going to happen between different providers? It still is a rapidly evolving technology space, and making sure that you, again, pick the right partners and allow yourself flexibility is important. | |
 
|
|
Responsible for insuring the safety of your network?
NWFusion offers two FREE security e-mail newsletters to help you keep your enterprise network
secure.
Click here to sign-up.
Click here to sign-up.
Three free and easy ways to bring Network World's in-depth editorial content to your own Web site.
Learn more
Learn more