Action 51, the final stake in the heart of issue-32

As promised, I took a pass through the editor's draft after we had all the 
normative changes drafted.
The list below shows the "server conditional" behavioral requirements 
imposed by LDP that I do not know of any way for a client to introspect 
programmatically at run time. 

Personally, I'm fine with leaving them open (things like "delete can have 
side effects on other resources" which is just a special case of the 
general HTTP statement anyway don't scare me).

The list is in spec-occurrence order.  As usual, I built in a bias for 
false positives: putting things on the list that might be covered in 
reality, like "can the container have non-LDPR members"... if you find 
one, clearly it can, but that doesn't cover a zero-member container so 
it's on the list.

4.1.3
4.1.6
4.1.9
4.2.3
4.4.1
4.4.6
4.5.2
4.7.3
4.9.2.2
4.9.2.3
4.9.2.5 ... questionable
4.10.1 paragraph 2
5.2.9
5.4.14

Best Regards, John

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