[
Lists Home |
Date Index |
Thread Index
]
- From: Henrik Frystyk Nielsen <frystyk@microsoft.com>
- To: "Bullard, Claude L (Len)" <clbullar@ingr.com>,Tim Bray <tbray@textuality.com>, xml-dev@lists.xml.org
- Date: Thu, 31 Aug 2000 09:11:12 -0700
> 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
|
