ISSUE-16: Redirection of non-information resources to BPRs

303 redirection

Redirection of non-information resources to BPRs

State:
CLOSED
Product:
Linked Data Platform Spec
Raised by:
Steve Battle
Opened on:
2012-10-03
Description:
See <http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements#UC-BPR1:_Retrieve_RDF_representation_of_a_resource>

Should the LDP support the redirection of non-information resources to BPRs?
(of course, the host on the non-information URI must be that of the LDP).

Do we use POWDER wdrs:describedby to make the relationship explicit in the RDF?

eg. :alice a foaf:Person; wdrs:describedby :alice.rdf.

I assume the RDF response to alice.rdf should include descriptions of both the information and non-information resources (since metadata about the non-information resource can't be accessed directly). ie. the type of :alice. Although the ETag relates specifically to the information resource.

What if the information resource is hosted on a different server and the LDP holds RDF metadata about the non-information resource?

e.g. <http://example.com/alice> a foaf:Person; wdrs:describedby <http://example.org/alice.rdf>.

a) Should the LDP simply redirect the client to <http://example.org/alice.rdf>? local metadata about non-information resource alice is lost.

b) Should the LDP GET the RDF from <http://example.org/alice.rdf> and merge it with the local RDF? The Content-Location could be added to the response - or is that misleading?
Related Actions Items:
No related actions
Related emails:
  1. Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from ashok.malhotra@oracle.com on 2013-04-05)
  2. Re: Review and Comments for Linked Data Platform FPWD (from david@3roundstones.com on 2013-03-05)
  3. Re: Review and Comments for Linked Data Platform FPWD (from sspeiche@gmail.com on 2013-03-04)
  4. Re: Open Issues against UC&R (from sspeiche@gmail.com on 2012-12-05)
  5. Re: Open Issues against UC&R (from steve.battle@sysemia.co.uk on 2012-12-05)
  6. Re: Open Issues against UC&R (from lehors@us.ibm.com on 2012-12-05)
  7. Open Issues against UC&R (from steve.battle@sysemia.co.uk on 2012-12-04)
  8. Review and Comments for Linked Data Platform FPWD (from david@3roundstones.com on 2012-10-28)
  9. Re: Use-Cases and call for help to add descriptions and scenarios ISSUE-16 (from rgarcia@fi.upm.es on 2012-10-04)
  10. RE: ldp-ISSUE-16 (stevebattle): Redirection of non-information resources to BPRs [Use Cases and Requirements] (from steve.battle@sysemia.co.uk on 2012-10-04)
  11. Re: ldp-ISSUE-16 (stevebattle): Redirection of non-information resources to BPRs [Use Cases and Requirements] (from kidehen@openlinksw.com on 2012-10-04)
  12. ldp-ISSUE-16 (stevebattle): Redirection of non-information resources to BPRs [Use Cases and Requirements] (from sysbot+tracker@w3.org on 2012-10-03)
  13. Re: ldp-ISSUE-16 (stevebattle): Redirection of non-information resources to BPRs [Use Cases and Requirements] (from kidehen@openlinksw.com on 2012-10-03)

Related notes:

Resolution: Close issue-16 without making any changes (as is)
See https://www.w3.org/2013/meeting/ldp/2013-06-20#resolution_3

Arnaud Le Hors, 20 Jun 2013, 16:02:07

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 <w3t-sys@w3.org>.
$Id: 16.html,v 1.1 2015/08/17 04:43:07 denis Exp $