ISSUE-44: 4.1.9. is obscure or too restrictive

4.1.9. is obscure or too restrictive

Linked Data Platform Spec
Raised by:
Henry Story
Opened on:
4.1.9 LDPRs must use at least one RDF triple to represent a link (relationship) to another resource. In other words, having the source resource’s URI as the subject and the target resource’s URI as the object of the triple representing the link (relationship) is enough and does not require the creation of an intermediate link resource to describe the relationship.

This seems to be saying something that is self evident or something that is too restrictive:
a) one must use at least one triple to relate 2 resources ( there is no other way to do this in RDF ! )
b) one should not use use more than one triple if possible, which would be a pragmatic self evidence, and should then go into a best-practices guide
c) It is also not clear why the resources have to be different - why does the same not apply when relating a resource to itself.

Related Actions Items:
No related actions
Related emails:
  1. LDP Rec (from on 2015-02-20)
  2. Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from on 2013-04-05)
  3. ldp-ISSUE-44: 4.1.9. is obscure or too restrictive [Linked Data Platform core] (from on 2013-01-14)

Related notes:

Resolution: Close ISSUE-44 by removing section 4.1.9 from the spec.

Arnaud Le Hors, 16 Mar 2013, 03:54:00

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 44.html,v 1.1 2015/08/17 04:43:09 denis Exp $