Re: Multiple resource representations during LDPC POST (5.4.1)

You describe the expected result correctly.
It is not "typical", insofar as not all triples in the response's 
representation (in this case, zero) have the HTTP URI as subject.
That does not cause any compliance problem.  "Typical" is going to be 
somewhat in the eye of the beholder anyway, pretty much always.  A 
"simple" graph store might just assign a random HTTP URI that matches zero 
subject URIs _in every case_.  For it, "typical" is the mismatch case.
The fact that the difference exists at all is the interesting point.  I've 
seen a lot of implementers coming from an OO background think that these 
LDP resources are just "objects", the HTTP URL is their "object handle", 
and therefore [Shirley it must be true that] every triple's subject must 
be the HTTP URI (after all, it's one of *that object's* properties!). 
Signalling that there *is* a difference, that leads to a conversation like 
this one, is the point of the text.  The companion documents should be 
where most of the "discussion" happens; the spec here is just noting a 
consequence of the underlying specs, not adding anything new.  9.3.1 
(written long after the "typically" came into being) addresses this more 
head-on - would a link to 9.3.1 help?

Best Regards, John

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