RE: Namespace and Versioning
> I agree that it is hell and no size fits all. > On the other hand, for exactly that reason, > no size should preclude any other. It is > similar to the problem of assigning security > levels to field values. It becomes a very > tortured graph. What I was looking for initially > in this thread is some comments on the practices > people are using to see if any general cases > emerge. I actually think the SOAP model works extremely well in this case - it provides a hook for mandatory evolution which can be used to extend SOAP based applications as well as SOAP itself and it is all based on URIs but leaves the exact policy (or policies) undetermined and part of the application. ...and URIs are of course opaque Henrik
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format