LDP Agenda for April 1st
- Re: LDP Agenda for April 1st
- Re: LDP Agenda for April 1st
- Re: LDP Agenda for April 1st
- Re: LDP Agenda for April 1st
- Re: LDP Agenda for April 1st
how to know that something was DELETEd
- Re: how to know that something was DELETEd
LDP Minutes for March 25
ACTION-43 Draft use case for ordering
- Re: ACTION-43 Draft use case for ordering
- Re: ACTION-43 Draft use case for ordering
- Re: ACTION-43 Draft use case for ordering
LDP agenda for March 25
ldp-ISSUE-60 (GETting empty containers): The specification does not allow GETting empty containers [Linked Data Platform core]
Containers and membership subject/object asymmetry
- re: Containers and membership subject/object asymmetry
- Re: Containers and membership subject/object asymmetry
issue-13 amended proposal
ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
LDP Minutes for March 15
ldp-ISSUE-58 (membersInlined): Property for asserting that complete description of members is included [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]
- 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]
- 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]
Re: LDPR URL Discovery
ldp-ISSUE-56 (Discovering LDPR PUT URLs): How can clients discover LDPR PUT URLs? [Linked Data Platform core]
Re: Hypermedia as the Engine of Application State
ldp-ISSUE-55 (HATEOAS Compliance): Hypermedia as the Engine of Application State (HATEOAS) Compliance [Linked Data Platform core]
Re: Section 5.4.8 null relative URI
Re: Section 4.2.3 Default to Turtle
ldp-ISSUE-54 (NullURIReplacement): Which URIs should replace null relative URIs provided in LDPR representations? [Linked Data Platform core]
ldp-ISSUE-53 (RepresentationsToBots): Which Content Types should be returned to bots? [Linked Data Platform core]
Peter's friends
ldp-ISSUE-52 (base): base [Linked Data Platform core]
LDP Minutes for March 14
A minimalist proposal for issue-50
Dinner for those who enjoy pain
Traffic on the comments list
atomic operations of LDP
LDP Minutes for March 13
ldp-ISSUE-51 ('backlinks'): Linking from a Resource to its Containers (aka 'backlinks') [Linked Data Platform core]
issue-21 proposal
Testing: schemas and procedures
A modest attempt to re-open ISSUE-20
- Re: A modest attempt to re-open ISSUE-20
- Re: A modest attempt to re-open ISSUE-20
- Re: A modest attempt to re-open ISSUE-20
- Re: A modest attempt to re-open ISSUE-20
LDP Minutes of March 11
Re: ldp-ISSUE-49 (Canonical-URI): Canonical URL - how to communicate its value to clients
- Re: ldp-ISSUE-49 (Canonical-URI): Canonical URL - how to communicate its value to clients
- Re: ldp-ISSUE-49 (Canonical-URI): Canonical URL - how to communicate its value to clients
Considering a PATCH model for LDP
- Re: Considering a PATCH model for LDP
- Re: Considering a PATCH model for LDP
- Re: Considering a PATCH model for LDP
Fw: Daylight Saving Time change –first half of 2013
LDP Agenda for March 11
2nd LDP Public Working Draft published
LDP Minutes of March 4
Editor's draft is ready to advance to 2nd Public Working Draft
Re: Review and Comments for Linked Data Platform FPWD
ZAKIM PROBLEM
ldp-ISSUE-50 (intuitive containers): Inuitive Containers: better support for relative URIs
Re: Affordances wiki page
LDP Agenda for March 4
- Re: LDP Agenda for March 4
- Re: LDP Agenda for March 4
- Re: LDP Agenda for March 4
- Re: LDP Agenda for March 4
- Re: LDP Agenda for March 4
F2F2 confirmation
Re: linking from resource -> container ..
- Re: linking from resource -> container ..
- Re: linking from resource -> container ..
- ldp:contains was: linking from resource -> container ..
- Re: linking from resource -> container ..