ISSUE-17: changesets as a recommended PATCH format

changesets

changesets as a recommended PATCH format

State:
CLOSED
Product:
Linked Data Platform Spec
Raised by:
Steve Battle
Opened on:
2012-10-03
Description:
Resources may be selectively updated using HTTP PATCH
<http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements#UC-BPR2:_Update_existing_resource>

No minimal set of patch document formats is mandated by the Linked Data Basic Profile 1.0.

Should the basic profile recommend (i.e. MAY USE) at least one patch format, so that we are able to develop concrete examples and test-cases, as well as providing positive guidance to implementers.

The Talis Changeset provides a well-defined basis for this: <http://docs.api.talis.com/getting-started/changesets>.

See also: http://www.w3.org/2001/sw/wiki/TurtlePatch

(NOTE that Talis does not seem to give any clues how to deal with Blank Nodes.)
Related Actions Items:
No related actions
Related emails:
  1. Re: Proposal to close ISSUE-17: changesets as a recommended PATCH format, as is (from johnarwe@us.ibm.com on 2013-05-28)
  2. Re: Proposal to close ISSUE-17: changesets as a recommended PATCH format, as is (from henry.story@bblfish.net on 2013-05-25)
  3. Re: Proposal to close ISSUE-17: changesets as a recommended PATCH format, as is (from cody.burleson@base22.com on 2013-05-24)
  4. Proposal to close ISSUE-17: changesets as a recommended PATCH format, as is (from lehors@us.ibm.com on 2013-05-24)
  5. 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)
  6. Re: Considering a PATCH model for LDP (from andy.seaborne@epimorphics.com on 2013-03-17)
  7. Re: ldp-ISSUE-57 (LDP Service ID): How can a client determine that it is in communication with an LDP service? [Linked Data Platform core] (from henry.story@bblfish.net on 2013-03-16)
  8. Re: ldp-ISSUE-57 (LDP Service ID): How can a client determine that it is in communication with an LDP service? [Linked Data Platform core] (from kidehen@openlinksw.com on 2013-03-15)
  9. Re: ldp-ISSUE-57 (LDP Service ID): How can a client determine that it is in communication with an LDP service? [Linked Data Platform core] (from Erik.Wilde@emc.com on 2013-03-15)
  10. ldp-ISSUE-57 (LDP Service ID): How can a client determine that it is in communication with an LDP service? [Linked Data Platform core] (from sysbot+tracker@w3.org on 2013-03-15)
  11. Re: Considering a PATCH model for LDP (from pierre-antoine.champin@liris.cnrs.fr on 2013-03-12)
  12. Re: Considering a PATCH model for LDP (from henry.story@bblfish.net on 2013-03-11)
  13. Re: Considering a PATCH model for LDP (from henry.story@bblfish.net on 2013-03-11)
  14. Re: Considering a PATCH model for LDP (from andy.seaborne@epimorphics.com on 2013-03-11)
  15. Re: Considering a PATCH model for LDP (from sspeiche@gmail.com on 2013-03-11)
  16. Re: Considering a PATCH model for LDP (from sspeiche@gmail.com on 2013-03-11)
  17. Re: Considering a PATCH model for LDP (from andy.seaborne@epimorphics.com on 2013-03-10)
  18. Re: Considering a PATCH model for LDP (from ashok.malhotra@oracle.com on 2013-03-09)
  19. Considering a PATCH model for LDP (from sspeiche@gmail.com on 2013-03-09)
  20. Re: Review and Comments for Linked Data Platform FPWD (from david@3roundstones.com on 2013-03-05)
  21. Re: Review and Comments for Linked Data Platform FPWD (from sspeiche@gmail.com on 2013-03-04)
  22. Re: Open Issues against UC&R (from sspeiche@gmail.com on 2012-12-05)
  23. Re: Open Issues against UC&R (from steve.battle@sysemia.co.uk on 2012-12-05)
  24. Re: Open Issues against UC&R (from lehors@us.ibm.com on 2012-12-05)
  25. Open Issues against UC&R (from steve.battle@sysemia.co.uk on 2012-12-04)
  26. Review and Comments for Linked Data Platform FPWD (from david@3roundstones.com on 2012-10-28)
  27. ldp-ISSUE-17 (changesets): changesets as a recommended PATCH format [Use Cases and Requirements] (from sysbot+tracker@w3.org on 2012-10-03)

Related notes:

Another reference is work I've done in SW tool integration domain, within OSLC. See http://open-services.net/wiki/core/OSLC-Core-Partial-Update/

Steve Speicher, 19 Jun 2013, 12:48:57

Resolution: Close Issue-17 and put it on the wish list.
See https://www.w3.org/2013/meeting/ldp/2013-06-19#resolution_5

Arnaud Le Hors, 19 Jun 2013, 22:46:40

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: 17.html,v 1.1 2015/08/17 04:43:07 denis Exp $