ISSUE-92: Change rel=type to rel=profile for client introspection of interaction model

interaction model

Change rel=type to rel=profile for client introspection of interaction model

State:

CLOSED

Product:

Linked Data Platform Spec

Raised by:

John Arwe

Opened on:

2014-01-02

Description:

When we discussed issue-91, we said that rel=type is probably not the best choice, and issue-91's proposer was very open to alternatives.

Most RDF literates would think of rel=type uri=ldp:Resource as a Link header as equivalent semantically to content (in an RDF resource) of <s, rdf:type, ldp:Resource>. Indeed, until we closed action-122 the spec even said these were notionally equivalent. The defining RFC 6903 simply says that the context uri is considered to be an instance of the target uri's abstract semantic type (i.e. it's a good match for rdf:type). There is no mention of interaction constraints being conveyed.

By Alexandre's own example (making a backup of an LDPC/LDPR), the backup is just a document (it has the same RDF content, including the same rdf:type(s), but a different interaction model), not an LDPC or LDPR.

The best candidate I see in the existing relation type registry is profile (RFC 6906), which I propose we use instead of 'type'.

If we cannot agree to use profile, then I propose that LDP mints an extension link relation type that it owns (making it an extension implies zero registration requirements).

Related Actions Items:

No related actions

Related emails:

1. Re: Getting to closure on the remaining issues - issue-92 (from kidehen@openlinksw.com on 2014-01-27)
2. Re: Getting to closure on the remaining issues - issue-92 (from bertails@w3.org on 2014-01-27)
3. Re: Getting to closure on the remaining issues - issue-92 (from kidehen@openlinksw.com on 2014-01-27)
4. Re: Getting to closure on the remaining issues - issue-92 (from kidehen@openlinksw.com on 2014-01-26)
5. Re: Getting to closure on the remaining issues - issue-92 (from kidehen@openlinksw.com on 2014-01-25)
6. Re: Getting to closure on the remaining issues - issue-92 (from kidehen@openlinksw.com on 2014-01-25)
7. Re: Getting to closure on the remaining issues - issue-92 (from henry.story@bblfish.net on 2014-01-25)
8. Re: Getting to closure on the remaining issues - issue-92 (from kidehen@openlinksw.com on 2014-01-25)
9. Re: Getting to closure on the remaining issues - issue-92 (from henry.story@bblfish.net on 2014-01-25)
10. Re: Getting to closure on the remaining issues - issue-92 (from eric@w3.org on 2014-01-25)
11. Re: Getting to closure on the remaining issues - issue-92 (from henry.story@bblfish.net on 2014-01-25)
12. Re: Getting to closure on the remaining issues - issue-92 (from eric@w3.org on 2014-01-25)
13. Re: Getting to closure on the remaining issues - issue-92 (from henry.story@bblfish.net on 2014-01-24)
14. Re: Getting to closure on the remaining issues - issue-92 (from eric@w3.org on 2014-01-24)
15. Re: Getting to closure on the remaining issues - issue-92 (from henry.story@bblfish.net on 2014-01-24)
16. Re: Getting to closure on the remaining issues (from henry.story@bblfish.net on 2014-01-24)
17. Re: Getting to closure on the remaining issues (from bertails@w3.org on 2014-01-23)
18. Re: Getting to closure on the remaining issues (from eric@w3.org on 2014-01-23)
19. Re: Getting to closure on the remaining issues (from bertails@w3.org on 2014-01-23)
20. Re: Getting to closure on the remaining issues (from eric@w3.org on 2014-01-22)
21. Re: LDP agenda for 20 January - issue-92 (from johnarwe@us.ibm.com on 2014-01-22)
22. Re: LDP agenda for 20 January - issue-92 (from henry.story@bblfish.net on 2014-01-22)
23. Re: rel=type or rel=profile, issue 92 (from sandro@w3.org on 2014-01-19)
24. Re: rel=type or rel=profile, issue 92 - rel=profile definition problem (from henry.story@bblfish.net on 2014-01-19)
25. Re: rel=type or rel=profile, issue 92 (from bertails@w3.org on 2014-01-18)
26. Re: rel=type or rel=profile (from henry.story@bblfish.net on 2014-01-15)
27. Re: rel=type or rel=profile (from bertails@w3.org on 2014-01-15)
28. Re: rel=type or rel=profile (from henry.story@bblfish.net on 2014-01-15)
29. Re: ldp-ISSUE-92 (interaction model): Change rel=type to rel=profile for client introspection of interaction model [Linked Data Platform Spec] (from Roger.Menday@uk.fujitsu.com on 2014-01-08)
30. 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-08)
31. Re: ldp-ISSUE-92 (interaction model): Change rel=type to rel=profile for client introspection of interaction model [Linked Data Platform Spec] (from kidehen@openlinksw.com on 2014-01-07)
32. Re: ldp-ISSUE-92 (interaction model): Change rel=type to rel=profile for client introspection of interaction model [Linked Data Platform Spec] (from roger.menday@uk.fujitsu.com on 2014-01-07)
33. 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-07)
34. Re: ldp-ISSUE-92 (interaction model): Change rel=type to rel=profile for client introspection of interaction model [Linked Data Platform Spec] (from kidehen@openlinksw.com on 2014-01-07)
35. Re: ldp-ISSUE-92 (interaction model): Change rel=type to rel=profile for client introspection of interaction model [Linked Data Platform Spec] (from roger.menday@uk.fujitsu.com on 2014-01-07)
36. Re: ldp-ISSUE-92 (interaction model): Change rel=type to rel=profile for client introspection of interaction model [Linked Data Platform Spec] (from johnarwe@us.ibm.com on 2014-01-07)
37. 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)
38. 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)
39. 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)

Related notes:

Display change log