Explain clearly the difference from LDP

[berezovskyi]

I think some fraction of the users can be expected to know what RDF is and might have heard about LDP (though not have studied the spec in detail). When such users land on oslc.co, they need a clear explanation of how OSLC builds on top of LDP for [thousand reasons here] but extends it with the [a few useful concepts here] concepts to make it particularly suitable for systems integration.

Just an idea, because I had to touch upon it in the paper draft I am working on right now for the semweb people.

[jamsden]

I have something on how OSLC builds on WWW architecture and HATEOAS. But basically LDP provides the containers for resources, and the Link headers provide incremental discovery information. Its also possible to have LDPCs correspond to OSLC ServiceProviders to bring these too approaches together.

[jamsden]

LDP also defines the predictable resource representations: Turtle and JSON-LD. So LDP provides a predictable way to know what the resources are, and how they are organized. OSLC utilizes LDP, but is not necessarily a generic LDP server. Rather it uses LDP to specify how servers provide resource operations, using the same approach as LDP for resource representations and organization.