[Commentor] LC-2837 Tim Berners-Lee (archived comment) [Comment] 4.11.1 "LDP does not provide clients with any way to detect whether or not the server is capable of inlining (all its resources or any specific resource), nor does it provide clients with any way to influence which (if any) resources are inlined in any given response." This implies cleints must all be able to handle inlining and recover from it if they didn't really want it. Need to define a protocol here properly or abandon the feature. (N3 or one of its weak imitations is obviously a clear choice for a inlined data, as it allows you to preserve the provenance, and basically explain which triples are from which resource. I understand this would frighten people at this stage.) [Commentor reply] tocheck [Working Group decision] 
Drop inlining from the spec, put it on the wish list for LDPnext See http://www.w3.org/2013/meeting/ldp/2013-09-12#resolution_2