Re: Why MD5 Headers are Imperative

Eric J. Bowman wrote:

> http://example.com/2006/aug/9.01.atom is the XQUERY file URI.  
> This is one resource.  

Ok.


> I could also expose the XQUERY at this URI:
>
> https://example.com/2006/aug/9.01.atom
>
> But, it's still an XQUERY with an .atom extension.

Ok. I think you need to drill it down further and look at what you mean 
by "an XQUERY". Is it the source of the xquery as found in the file, or 
the result of that xquery after it's been run through an interpreter? 
When you said "Execute for some, display code for others" that's the key 
distinction. Instinctively I would say those are different things and 
that distinction is worth preserving because I can imagine situations 
where making the distinction matters*. I think you are conflating these 
things, and it's biting you because the APP is relatively precise in how 
it distributes URIs to referents, but I'm not sure.

cheers
Bill

* http://mitpress.mit.edu/sicp/full-text/book/book-Z-H-26.html#%_sec_4.1