Re: Multiple resource representations during LDPC POST (5.4.1)

> as input -- but why call it "representation" as 5.4.1 does, and not
> "graph"?

Because 5.4.1 applies to creation of all types of members, not only of 
members representable as RDF.
It's an HTTP interaction, and HTTP transfers representations (generally).

> I'm arguing that one cannot PUT or POST a resource representation (in
> full). One can only GET it, possibly as product of multiple graphs, as
> with the DESCRIBE result.

At the HTTP level, your PUT argument sounds equivalent to saying PUT 
cannot be implemented, which conflicts with implementation experience. 
You MIGHT be in similar trouble with POST, I have not checked 2616's 
wording today but generally it talks about POST accepting processing 
instructions (create is one example of that usage, but not the only one).

If you are talking about some restricted subset of all Web resources, 
"maybe" [he says, without checking ;-) ].  But as soon as I wrote "Web", I 
started to feel like it will be a definitional issue.

> I think "description of resource" from SPARQL is actually the true
> meaning of LDP "resource representation", and defined better:

That might be true if LDP 5.4.1 ONLY dealt with graphs, but that's not the 
case.  Search on "binary" for other points in the text where this comes 
out more clearly.



Best Regards, John

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