Difference between revisions of "LDPNext"

From Linked Data Platform
Jump to: navigation, search
(Embedded representations)
(Richer Containers)
Line 16: Line 16:
 
== Richer Containers ==
 
== Richer Containers ==
  
 +
An ongoing (and persistent) discussion within LDP is that of containers, ..
 +
 +
when a resource is strictly contain
  
 
'''Related Issues'''
 
'''Related Issues'''

Revision as of 13:11, 29 April 2013

1 A wish list for LDP.Next

In the scope of the current activity there is some potential extension work we we might want to consider. Please extend the following list.


1.1 Embedded representations

When retreving a representation of a resource, a minimal expectation of the server is that it returns all the triples it where the addressed resource is found in the subject position (entity view). The server may also choose to inline other triples where the targeted resource is found in the object position. The baseline practice is that the client navigates to related resources to find out about them. However, to improve the efficiency of this interaction, it might be useful for client to instruct the server to provide inline representations of related resources. This requirement is similar to the functionity that OData provides with its 'expand' query option [1].


Related Issues

  • 38 Filtered Representations and Inlining
  • 58 Property for asserting that complete description of members is included in LDPC representation

1.2 Richer Containers

An ongoing (and persistent) discussion within LDP is that of containers, ..

when a resource is strictly contain

Related Issues

  • 25 Weak aggregation and strong composition in containers
  • 59 Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior

1.3 Application specific APIs

Related Issues

  • 26 Creation Model