- From: BigBlueHat via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jul 2015 18:24:05 +0000
- To: public-annotation@w3.org
@melvincarvalho great read, but not quite what I was after. Mostly what I'm wondering is how an LDP server or client expresses / "knows" a resource is an LDP-RS vs. a non-RDF Source. Is it merely that the document's media type is an encoding of an RDF-based data model (ala JSON-LD, Turtle, etc)? and, if that is the vector on which the "RDF-ness" of the resource is deteremined to what end is it valuable/important to the server or client? Can the client do anything "smart" with it--particularly in the scenario where there is *only* and LDP Basic Container and no Direct or Indirect access to "sub-graphs." My feeling is that one could setup an LDP Basic Container which stores only JSON-LD has no particular graph related "smarts" and is still technically compliant per the spec. However, I'm not sure how LDP clients would feel about it. :confused: -- GitHub Notif of comment by BigBlueHat See https://github.com/w3c/web-annotation/issues/34#issuecomment-126049297
Received on Wednesday, 29 July 2015 18:24:08 UTC