Cart
[Home] [By Thread] [By Date] [Recent Entries]
I like what John says. It connotes the nuttiness of having useless declarations and therefore, attempts to get the authority of note to lock down the agreement on the use. I can put BAFFLEGAB://myrant.com/myrant in the namespace value, and I can have a *consistent* expectation that it won't be dereferenced. I can't guarantee it, but I can expect it. If I put http or ftp there, my expectations will quickly become frustrations. Why? The browser turns it blue and makes it clickable. Sorry, but the running code does set the expectations and that is just the way a global interoperable system bounces. Rail at it, curse it, ignore it; you built it. consistency: expect to see this term in lots of places where there are no guarantees but there are expectations. Consistency is almost analogous to system. len From: Mark Feblowitz [mailto:mfeblowitz@f...] Not to mention John Cowan's: ' requiring that if a version number appears in the XML declaration, that it must be "1.0".'
|
