from March 2013 by subject

2nd LDP Public Working Draft published

A minimalist proposal for issue-50

A modest attempt to re-open ISSUE-20

ACTION-43 Draft use case for ordering

Affordances wiki page


atomic operations of LDP

Considering a PATCH model for LDP

Containers and membership subject/object asymmetry

Daylight Saving Time change –first half of 2013

Dinner for those who enjoy pain

Editor's draft is ready to advance to 2nd Public Working Draft

F2F2 confirmation

how to know that something was DELETEd

Hypermedia as the Engine of Application State

issue-13 amended proposal

issue-21 proposal

LDP Agenda for April 1st

LDP Agenda for March 11

LDP agenda for March 25

LDP Agenda for March 4

LDP Minutes for March 13

LDP Minutes for March 14

LDP Minutes for March 15

LDP Minutes for March 25

LDP Minutes of March 11

LDP Minutes of March 4

ldp-ISSUE-49 (Canonical-URI): Canonical URL - how to communicate its value to clients

ldp-ISSUE-50 (intuitive containers): Inuitive Containers: better support for relative URIs

ldp-ISSUE-51 ('backlinks'): Linking from a Resource to its Containers (aka 'backlinks') [Linked Data Platform core]

ldp-ISSUE-52 (base): base [Linked Data Platform core]

ldp-ISSUE-53 (RepresentationsToBots): Which Content Types should be returned to bots? [Linked Data Platform core]

ldp-ISSUE-54 (NullURIReplacement): Which URIs should replace null relative URIs provided in LDPR representations? [Linked Data Platform core]

ldp-ISSUE-55 (HATEOAS Compliance): Hypermedia as the Engine of Application State (HATEOAS) Compliance [Linked Data Platform core]

ldp-ISSUE-56 (Discovering LDPR PUT URLs): How can clients discover LDPR PUT URLs? [Linked Data Platform core]

ldp-ISSUE-57 (LDP Service ID): How can a client determine that it is in communication with an LDP service? [Linked Data Platform core]

ldp-ISSUE-58 (membersInlined): Property for asserting that complete description of members is included [Linked Data Platform core]

ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]

ldp-ISSUE-60 (GETting empty containers): The specification does not allow GETting empty containers [Linked Data Platform core]

ldp:contains was: linking from resource -> container ..

LDPR URL Discovery

linking from resource -> container ..

Peter's friends

Review and Comments for Linked Data Platform FPWD

Re : LDP Agenda for March 11

Section 4.2.3 Default to Turtle

Section 5.4.8 null relative URI

Testing: schemas and procedures

The Intuitive/ Requirement

Traffic on the comments list


Last message date: Saturday, 30 March 2013 21:36:16 UTC