ISSUE-91: The LDP (REST) interactions must be driven by the rel='type' Link header

rel='type' Link-based interaction

The LDP (REST) interactions must be driven by the rel='type' Link header

State:

CLOSED

Product:

Linked Data Platform Spec

Raised by:

Alexandre Bertails

Opened on:

2013-11-22

Description:

We have already agreed that LDP interactions are not strictly hypermedia driven, as we agreed not to define a new media-type for LDP. Instead we have a Link header for Resource [1].

The problem is that 4.2.10 [1] does not really advertise the LDP interaction, just the "LDP support" for the resource, and the interaction is currently derived from a { <> a ldp:Container } triple (or its absence). That means than I cannot create a simple LDPR with that triple _without_ the related interaction model. This is wrong.

My proposal is to say that the interaction model is directly (and solely) derived from the "type" Link header, having one for the LDPR and one for the LDPC. This is aligned with the previous proposal of not defining a new media type but to extend the existing RDF ones with the rel='type' Link header.

For an LDPR (and ideally for Binary if it also were an LDPR):
Link: <http://www.w3.org/ns/ldp#Resource>; rel="type"

For an LDPC:
Link: <http://www.w3.org/ns/ldp#Container>; rel="type"

Now, I can copy the content of an LDPC (eg. for backup purposes) into a new LDPR, without inheriting the LDPC interactions.

Also, creating an LDPC is now easy to define (and implement): you POST a document *with* the corresponding Link header (otherwise, it's an LDPR, or a Binary).

Alexandre.

[1] https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpr-4_2_10

Related Actions Items:

No related actions

Related emails:

1. Re: LDPR Interaction Model on Create (from sspeiche@gmail.com on 2014-10-14)
2. Re: LDPR Interaction Model on Create (from andrei@w3.org on 2014-10-14)
3. Re: LDPR Interaction Model on Create (from sspeiche@gmail.com on 2014-10-14)
4. Re: LDPR Interaction Model on Create (from nmihindu@fi.upm.es on 2014-10-13)
5. Re: LDP agenda for 20 January - issue-92 (from henry.story@bblfish.net on 2014-01-22)
6. Re: rel=type or rel=profile, issue 92 (from sandro@w3.org on 2014-01-19)
7. Re: rel=type or rel=profile, issue 92 - rel=profile definition problem (from henry.story@bblfish.net on 2014-01-19)
8. Re: rel=type or rel=profile, issue 92 (from bertails@w3.org on 2014-01-18)
9. Re: rel=type or rel=profile, issue 92 (from henry.story@bblfish.net on 2014-01-18)
10. Re: rel=type or rel=profile, issue 92 (from henry.story@bblfish.net on 2014-01-18)
11. Re: ldp-ISSUE-92 (interaction model): Change rel=type to rel=profile for client introspection of interaction model [Linked Data Platform Spec] (from henry.story@bblfish.net on 2014-01-06)
12. Re: ldp-ISSUE-92 (interaction model): Change rel=type to rel=profile for client introspection of interaction model [Linked Data Platform Spec] (from bertails@w3.org on 2014-01-06)
13. ldp-ISSUE-92 (interaction model): Change rel=type to rel=profile for client introspection of interaction model [Linked Data Platform Spec] (from sysbot+tracker@w3.org on 2014-01-02)
14. Re: ldp-ISSUE-91 (rel='type' Link-based interaction): The LDP (REST) interactions must be driven by the rel='type' Link header [Linked Data Platform Spec] (from bertails@w3.org on 2013-12-02)
15. Re: ldp-ISSUE-91 (rel='type' Link-based interaction): The LDP (REST) interactions must be driven by the rel='type' Link header [Linked Data Platform Spec] (from lehors@us.ibm.com on 2013-11-27)
16. Re: ldp-ISSUE-91 (rel='type' Link-based interaction): The LDP (REST) interactions must be driven by the rel='type' Link header [Linked Data Platform Spec] (from bertails@w3.org on 2013-11-27)
17. Re: ldp-ISSUE-91 (rel='type' Link-based interaction): The LDP (REST) interactions must be driven by the rel='type' Link header [Linked Data Platform Spec] (from sspeiche@gmail.com on 2013-11-26)
18. Re: ldp-ISSUE-91 (rel='type' Link-based interaction): The LDP (REST) interactions must be driven by the rel='type' Link header [Linked Data Platform Spec] (from bertails@w3.org on 2013-11-26)
19. Re: ldp-ISSUE-91 (rel='type' Link-based interaction): The LDP (REST) interactions must be driven by the rel='type' Link header [Linked Data Platform Spec] (from bertails@w3.org on 2013-11-26)
20. Re: ldp-ISSUE-91 (rel='type' Link-based interaction): The LDP (REST) interactions must be driven by the rel='type' Link header [Linked Data Platform Spec] (from sspeiche@gmail.com on 2013-11-26)
21. Re: ldp-ISSUE-91 (rel='type' Link-based interaction): The LDP (REST) interactions must be driven by the rel='type' Link header [Linked Data Platform Spec] (from sspeiche@gmail.com on 2013-11-26)
22. Re: ldp-ISSUE-91 (rel='type' Link-based interaction): The LDP (REST) interactions must be driven by the rel='type' Link header [Linked Data Platform Spec] (from henry.story@bblfish.net on 2013-11-23)
23. Re: ldp-ISSUE-91 (rel='type' Link-based interaction): The LDP (REST) interactions must be driven by the rel='type' Link header [Linked Data Platform Spec] (from bertails@w3.org on 2013-11-23)
24. Re: ldp-ISSUE-91 (rel='type' Link-based interaction): The LDP (REST) interactions must be driven by the rel='type' Link header [Linked Data Platform Spec] (from kidehen@openlinksw.com on 2013-11-22)
25. ldp-ISSUE-91 (rel='type' Link-based interaction): The LDP (REST) interactions must be driven by the rel='type' Link header [Linked Data Platform Spec] (from sysbot+tracker@w3.org on 2013-11-22)

Related notes:

Display change log