|
Updated: 9/1/2002; 6:58:05 PM.
 |
Tuesday, July 30, 2002 |
 ;)
10:26:46 PM 
|
|
Don Box: The specific epiphany I had today was as follows: There is a sweet spot in XML Schema that combines element wildcards (e.g., <xsd:any>) and D-B-R [derivation by restriction]. Specifically, if one terminates the content model of a complex type with the traditional element wildcard:
<xs:any minOccurs="0" maxOccurs="unbounded" />
That one can easily emulate D-B-E [derivation by extension] simply by peeling N particles in the derived type, one for each "extended" element.
10:23:38 PM
|
|
Thanks go out to James Strachan for committing my patch to Jaxen. Now the gump build gets a bit further again. Also, it looks like James liked my essay. Thanks. I continue to strive to find the middle ground between the Web Services and REST advocates, running the risk of alienating both camps. Meanwhile, the ever moderate Jon Udell seems always be able to find the middle ground between my middle ground and the position that I am trying to moderate. How does he do that? 
1:04:51 PM
|
|
Tomas Restrepo: First, I agree with Sam that this makes sense in a loose coupled world. Cool. Second, this can also provide some pretty painful debugging and head scratching (wondering why your argument's are being ignored?) Absolutely has, many times. However, I don't think that's entirely the way to go. I think published interfaces should be in essence immutable.
Clearly, .NET (or is it SOAP itself?) has cemented association between XML and interface is too strongly. Be back later today with something that may provide insight into other perspectives... some REST advocates may find this amusing too. For a hint... see Don Box's XML & Inclusion.
1:16:23 AM
|
|
Joe Gregorio: Of course, the Amazon URL's I copied were originally very long but I had a sneaking suspicion that there was extra info in there and found that this much shorter URL works just fine. I guess they just don't make them as opaque as they used to... LOL!
12:14:49 AM
|
|
|
