Re: Action-126: Proposal to materialize ldp:contains

> TriG is nice but not necessary in my opinion. If I GET
> <http://example.com/foo>, I know that as an Linked Data client, I
> should consider as authoritative only the statements about
> <http://example.com/foo> itself or the derived hash-URIs as
> <http://example.com/foo#bar> or <#bar>. I would consider anything else
> as being inlined.

Search the archive + minutes for inlining, provenance, authoritative. Talk 
to Yves about the last one.
We've had "extensive spirited discussions" over the months.
TriG is just one alternative, as I said.

> Maybe that could go into Good Practices.

Whereas a year ago I would have agreed, Henry et al. has convinced me that 
this is not a general or reliable assumption.  It needs caveats if it's 
there at all.  It's completely appropriate *within certain app-specific 
contexts* where the server exercises control over what the client stores, 
and potentially over state transitions.


Best Regards, John

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