we implement this using "globbing" so when I GET Container/* it gives me all the messages. Perhaps not the most elegant solution but very useful! :) This is something that could perhaps benefit from more standardization.
6.2.3 LDP servers remove the resource identified by the Request-URI in response to a successful HTTP DELETE request. After such a request, a subsequent HTTP GET on the same Request-URI usually results in a 404 (Not found) or 410 (Gone) status code, although HTTP allows others.
@melvincarvalho How it works for fs is an implementation detail. Just as you presumably regenerate the ldp:contains triples whenever something new is created, you can add the resource triples to that file as well
@semanticfire Your call as to how you describe your own resource. LDP only requires the ldp:contains so that the notifications can be discovered. If you do anything on top of that, that's all fine and everything but it goes without saying that don't expect arbitrary tooling to 'make sense of' anything else that's part of that resource description.