- From: Wilde, Erik <Erik.Wilde@emc.com>
- Date: Fri, 15 Mar 2013 14:16:58 -0400
- To: Linked Data Platform Working Group <public-ldp-wg@w3.org>
hello richard. On 2013-03-15 10:51 , "Linked Data Platform (LDP) Working Group Issue Tracker" <sysbot+tracker@w3.org> wrote: >PROPOSAL: Add a property ldp:membersInlined true/false. The default (if >not specified) is false. If true, it means that a complete description of >all members [on the current page] are inlined with the container document >[or page], and therefore clients SHOULD NOT do GET on the member URIs to >retrieve additional triples. what about (also) adding this as an interaction affordance, meaning that it's expressed as a URI parameter and servers may even offer clients the ability to request inline representations or not. in a more complicated scenario, you could also consider inlining to support inlining *all LDP properties*, or inlining *all server-managed properties including non LDP ones*. this just refers to service-managed member metadata, right? for the member content (which could be non-LDP, also referred to as "binary" right now), unless it had been supplied inline when creating the member, even inlining would only result in returning the link to the content, right? cheers, dret.
Received on Friday, 15 March 2013 18:17:47 UTC