Re: Accept on GET and access control

Erik, I'm having trouble translating that into spec-ese.
You might be saying: 
- the "write related" headers like Accept-Patch/Post need to be "less than 
Musts"
- we should leave them as MAYs ("inherit" from HTTP et al. w/o adding 
stronger guarantees in LDP)
- we should remove all mention of them, or minimally move them to the new 
section covering "things ldp inherits from base specs that not everyone is 
aware of"
- something else.

We actually got into the OPTIONS business mainly because HEAD requires the 
same headers as GET, and Content-Length can be expensive to compute.  So 
the notion that some headers are problem children is something we've made 
accommodations for in the past - no reason to avoid doing so here if we 
see a clear path.

Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario