public-ldp-wg@w3.org from March 2013 by author

Alexandre Bertails

• Re: ACTION-43 Draft use case for ordering (Monday, 25 March)
• Re: ACTION-43 Draft use case for ordering (Monday, 25 March)
• Re: ACTION-43 Draft use case for ordering (Monday, 25 March)

Andy Seaborne

• Re: how to know that something was DELETEd (Thursday, 28 March)
• Re: LDP agenda for March 25 (Monday, 25 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Friday, 22 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Thursday, 21 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Tuesday, 19 March)
• Re: Considering a PATCH model for LDP (Sunday, 17 March)
• Traffic on the comments list (Thursday, 14 March)
• Re: A modest attempt to re-open ISSUE-20 (Thursday, 14 March)
• Re: A modest attempt to re-open ISSUE-20 (Wednesday, 13 March)
• Re: Considering a PATCH model for LDP (Monday, 11 March)
• Re: Considering a PATCH model for LDP (Sunday, 10 March)
• Re: LDP Agenda for March 4 (Sunday, 3 March)

Antonis Loizou

• Re: LDP Agenda for March 4 (Monday, 4 March)

Arnaud Le Hors

• Re: LDP Agenda for April 1st (Saturday, 30 March)
• LDP Agenda for April 1st (Friday, 29 March)
• LDP Minutes for March 25 (Monday, 25 March)
• Re: LDP agenda for March 25 (Monday, 25 March)
• LDP agenda for March 25 (Sunday, 24 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Thursday, 21 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Thursday, 21 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Tuesday, 19 March)
• LDP Minutes for March 15 (Friday, 15 March)
• LDP Minutes for March 14 (Friday, 15 March)
• LDP Minutes for March 13 (Thursday, 14 March)
• Re: F2F2 confirmation (Tuesday, 12 March)
• LDP Minutes of March 11 (Monday, 11 March)
• Re: linking from resource -> container .. (Monday, 11 March)
• Fw: Daylight Saving Time change –first half of 2013 (Friday, 8 March)
• LDP Agenda for March 11 (Friday, 8 March)
• Re: linking from resource -> container .. (Friday, 8 March)
• 2nd LDP Public Working Draft published (Thursday, 7 March)
• Re: LDP Minutes of March 4 (Wednesday, 6 March)
• LDP Minutes of March 4 (Monday, 4 March)
• LDP Agenda for March 4 (Saturday, 2 March)
• Re: The Intuitive/ Requirement (Friday, 1 March)

Ashok Malhotra

• Re: LDP Agenda for April 1st (Friday, 29 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Wednesday, 20 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Tuesday, 19 March)
• Re: Considering a PATCH model for LDP (Saturday, 9 March)
• Re: linking from resource -> container .. (Thursday, 7 March)
• Re: linking from resource -> container .. (Friday, 1 March)

Bart van Leeuwen

• Re: LDP Agenda for March 4 (Monday, 4 March)

David Wood

• Re: LDPR URL Discovery (Friday, 15 March)
• Re: Hypermedia as the Engine of Application State (Friday, 15 March)
• Re: Section 5.4.8 null relative URI (Friday, 15 March)
• Re: Section 4.2.3 Default to Turtle (Friday, 15 March)
• Re: Review and Comments for Linked Data Platform FPWD (Tuesday, 5 March)
• Re: F2F2 confirmation (Friday, 1 March)
• Re: linking from resource -> container .. (Friday, 1 March)

Henry Story

• Re: ACTION-43 Draft use case for ordering (Monday, 25 March)
• Re: LDP agenda for March 25 (Monday, 25 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Thursday, 21 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Thursday, 21 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Thursday, 21 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Tuesday, 19 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Tuesday, 19 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Tuesday, 19 March)
• 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] (Saturday, 16 March)
• Re: Section 5.4.8 null relative URI (Friday, 15 March)
• Re: A modest attempt to re-open ISSUE-20 (Thursday, 14 March)
• Re: A modest attempt to re-open ISSUE-20 (Thursday, 14 March)
• Re: A modest attempt to re-open ISSUE-20 (Wednesday, 13 March)
• Re: A modest attempt to re-open ISSUE-20 (Wednesday, 13 March)
• Re: A modest attempt to re-open ISSUE-20 (Wednesday, 13 March)
• Re: A modest attempt to re-open ISSUE-20 (Tuesday, 12 March)
• Re: Considering a PATCH model for LDP (Monday, 11 March)
• Re: Considering a PATCH model for LDP (Monday, 11 March)
• Aggregate/Container (Friday, 8 March)
• Re: linking from resource -> container .. (Thursday, 7 March)
• Re: linking from resource -> container .. (Monday, 4 March)
• ldp:contains was: linking from resource -> container .. (Monday, 4 March)
• Re: ldp-ISSUE-50 (intuitive containers): Inuitive Containers: better support for relative URIs (Monday, 4 March)
• Re: The Intuitive/ Requirement (Monday, 4 March)
• Re: The Intuitive/ Requirement (Friday, 1 March)

John Arwe

• Dinner for those who enjoy pain (Thursday, 14 March)
• Re: ldp-ISSUE-49 (Canonical-URI): Canonical URL - how to communicate its value to clients (Wednesday, 13 March)
• Re: linking from resource -> container .. (Wednesday, 13 March)
• Re: linking from resource -> container .. (Thursday, 7 March)
• Re: LDP Minutes of March 4 (Wednesday, 6 March)
• Re: Affordances wiki page (Sunday, 3 March)

Kingsley Idehen

• Re: how to know that something was DELETEd (Thursday, 28 March)
• Re: how to know that something was DELETEd (Wednesday, 27 March)
• Re: how to know that something was DELETEd (Wednesday, 27 March)
• 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] (Friday, 15 March)
• Re: Peter's friends (Friday, 15 March)
• Re: A modest attempt to re-open ISSUE-20 (Wednesday, 13 March)
• Re: linking from resource -> container .. (Thursday, 7 March)
• Re: linking from resource -> container .. (Monday, 4 March)
• Re: Affordances wiki page (Monday, 4 March)
• Re: Affordances wiki page (Monday, 4 March)
• Re: Affordances wiki page (Monday, 4 March)
• Re: linking from resource -> container .. (Friday, 1 March)

Linked Data Platform (LDP) Working Group Issue Tracker

• ldp-ISSUE-60 (GETting empty containers): The specification does not allow GETting empty containers [Linked Data Platform core] (Friday, 22 March)
• ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Tuesday, 19 March)
• ldp-ISSUE-58 (membersInlined): Property for asserting that complete description of members is included [Linked Data Platform core] (Friday, 15 March)
• ldp-ISSUE-57 (LDP Service ID): How can a client determine that it is in communication with an LDP service? [Linked Data Platform core] (Friday, 15 March)
• ldp-ISSUE-56 (Discovering LDPR PUT URLs): How can clients discover LDPR PUT URLs? [Linked Data Platform core] (Friday, 15 March)
• ldp-ISSUE-55 (HATEOAS Compliance): Hypermedia as the Engine of Application State (HATEOAS) Compliance [Linked Data Platform core] (Friday, 15 March)
• ldp-ISSUE-54 (NullURIReplacement): Which URIs should replace null relative URIs provided in LDPR representations? [Linked Data Platform core] (Friday, 15 March)
• ldp-ISSUE-53 (RepresentationsToBots): Which Content Types should be returned to bots? [Linked Data Platform core] (Friday, 15 March)
• ldp-ISSUE-52 (base): base [Linked Data Platform core] (Friday, 15 March)
• ldp-ISSUE-51 ('backlinks'): Linking from a Resource to its Containers (aka 'backlinks') [Linked Data Platform core] (Wednesday, 13 March)
• ldp-ISSUE-50 (intuitive containers): Inuitive Containers: better support for relative URIs (Monday, 4 March)

Nandana Mihindukulasooriya

• Re: ACTION-43 Draft use case for ordering (Monday, 25 March)

Pierre-Antoine Champin

• Re: LDP Agenda for April 1st (Saturday, 30 March)
• Re: issue-13 amended proposal (Tuesday, 19 March)
• Re: A minimalist proposal for issue-50 (Saturday, 16 March)
• Re: LDP Minutes for March 13 (Thursday, 14 March)
• Re: A modest attempt to re-open ISSUE-20 (Wednesday, 13 March)
• Re: A modest attempt to re-open ISSUE-20 (Wednesday, 13 March)
• A modest attempt to re-open ISSUE-20 (Tuesday, 12 March)
• Re: Considering a PATCH model for LDP (Tuesday, 12 March)
• Re: Affordances wiki page (Monday, 4 March)
• Re: Affordances wiki page (Monday, 4 March)

Raúl García Castro

• Testing: schemas and procedures (Tuesday, 12 March)
• Re: ldp-ISSUE-49 (Canonical-URI): Canonical URL - how to communicate its value to clients (Tuesday, 12 March)
• Re: The Intuitive/ Requirement (Friday, 1 March)

Richard Cyganiak

• Re: LDP Agenda for April 1st (Saturday, 30 March)
• Re: how to know that something was DELETEd (Wednesday, 27 March)
• Re: how to know that something was DELETEd (Wednesday, 27 March)
• Re: how to know that something was DELETEd (Wednesday, 27 March)
• Re: ACTION-43 Draft use case for ordering (Tuesday, 26 March)
• Re: ACTION-43 Draft use case for ordering (Tuesday, 26 March)
• Re: ACTION-43 Draft use case for ordering (Tuesday, 26 March)
• Re: ACTION-43 Draft use case for ordering (Monday, 25 March)
• Re: ACTION-43 Draft use case for ordering (Monday, 25 March)
• Re: ACTION-43 Draft use case for ordering (Monday, 25 March)
• Re: ldp-ISSUE-60 (GETting empty containers): The specification does not allow GETting empty containers [Linked Data Platform core] (Friday, 22 March)
• Re: Containers and membership subject/object asymmetry (Wednesday, 20 March)
• Re: issue-13 amended proposal (Wednesday, 20 March)
• Re: Containers and membership subject/object asymmetry (Wednesday, 20 March)
• Re: issue-13 amended proposal (Wednesday, 20 March)
• Re: issue-13 amended proposal (Tuesday, 19 March)

Roger Menday

• Peter's friends (Friday, 15 March)
• atomic operations of LDP (Thursday, 14 March)
• Re: linking from resource -> container .. (Monday, 11 March)
• Re: linking from resource -> container .. (Sunday, 10 March)
• Re: linking from resource -> container .. (Friday, 8 March)
• Re: linking from resource -> container .. (Thursday, 7 March)
• Re: The Intuitive/ Requirement (Thursday, 7 March)
• Re: linking from resource -> container .. (Thursday, 7 March)
• Re: linking from resource -> container .. (Monday, 4 March)
• Re: linking from resource -> container .. (Friday, 1 March)

Ruben Verborgh

• Re: F2F2 confirmation (Monday, 11 March)

Sandro Hawke

• Re: LDP agenda for March 25 (Monday, 25 March)
• ZAKIM PROBLEM (Monday, 4 March)
• F2F2 confirmation (Friday, 1 March)

Serena Villata

• Re: LDP Agenda for April 1st (Saturday, 30 March)
• Re : LDP Agenda for March 11 (Monday, 11 March)

Sergio Fernández

• Re: LDP Agenda for April 1st (Saturday, 30 March)
• Re: LDP Agenda for March 4 (Monday, 4 March)

Steve Battle

• RE: issue-13 amended proposal (Thursday, 21 March)
• RE: Containers and membership subject/object asymmetry (Wednesday, 20 March)
• RE: issue-13 amended proposal (Wednesday, 20 March)
• re: Containers and membership subject/object asymmetry (Wednesday, 20 March)
• Containers and membership subject/object asymmetry (Wednesday, 20 March)
• RE: issue-13 amended proposal (Wednesday, 20 March)
• issue-13 amended proposal (Tuesday, 19 March)
• Re: linking from resource -> container .. (Sunday, 10 March)
• Re: LDP Agenda for March 11 (Sunday, 10 March)
• Re: LDP Agenda for March 4 (Monday, 4 March)

Steve Speicher

• ACTION-43 Draft use case for ordering (Monday, 25 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Wednesday, 20 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Tuesday, 19 March)
• Re: Considering a PATCH model for LDP (Monday, 11 March)
• Re: Considering a PATCH model for LDP (Monday, 11 March)
• Considering a PATCH model for LDP (Saturday, 9 March)
• Re: Aggregate/Container (Friday, 8 March)
• Editor's draft is ready to advance to 2nd Public Working Draft (Monday, 4 March)
• Re: Review and Comments for Linked Data Platform FPWD (Monday, 4 March)

Steven Battle

• A minimalist proposal for issue-50 (Thursday, 14 March)
• issue-21 proposal (Wednesday, 13 March)

Ted Thibodeau Jr

• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Monday, 25 March)
• Re: LDP agenda for March 25 (Monday, 25 March)

Wilde, Erik

• Re: how to know that something was DELETEd (Wednesday, 27 March)
• Re: how to know that something was DELETEd (Wednesday, 27 March)
• Re: how to know that something was DELETEd (Wednesday, 27 March)
• Re: how to know that something was DELETEd (Wednesday, 27 March)
• Re: how to know that something was DELETEd (Wednesday, 27 March)
• Re: how to know that something was DELETEd (Wednesday, 27 March)
• how to know that something was DELETEd (Wednesday, 27 March)
• Re: ACTION-43 Draft use case for ordering (Tuesday, 26 March)
• Re: ACTION-43 Draft use case for ordering (Tuesday, 26 March)
• Re: ACTION-43 Draft use case for ordering (Tuesday, 26 March)
• Re: ACTION-43 Draft use case for ordering (Monday, 25 March)
• Re: ACTION-43 Draft use case for ordering (Monday, 25 March)
• Re: ACTION-43 Draft use case for ordering (Monday, 25 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Friday, 22 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Friday, 22 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Wednesday, 20 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Tuesday, 19 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Tuesday, 19 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Tuesday, 19 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Tuesday, 19 March)
• Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (Tuesday, 19 March)
• 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] (Friday, 15 March)
• Re: ldp-ISSUE-58 (membersInlined): Property for asserting that complete description of members is included [Linked Data Platform core] (Friday, 15 March)
• Re: issue-21 proposal (Friday, 15 March)
• Re: ldp-ISSUE-55 (HATEOAS Compliance): Hypermedia as the Engine of Application State (HATEOAS) Compliance [Linked Data Platform core] (Friday, 15 March)
• Re: A minimalist proposal for issue-50 (Thursday, 14 March)
• Re: ldp-ISSUE-49 (Canonical-URI): Canonical URL - how to communicate its value to clients (Wednesday, 13 March)
• Re: ldp-ISSUE-49 (Canonical-URI): Canonical URL - how to communicate its value to clients (Wednesday, 13 March)
• Re: ldp-ISSUE-49 (Canonical-URI): Canonical URL - how to communicate its value to clients (Monday, 11 March)
• Re: Considering a PATCH model for LDP (Monday, 11 March)
• Re: Considering a PATCH model for LDP (Monday, 11 March)
• Re: 2nd LDP Public Working Draft published (Thursday, 7 March)
• Re: linking from resource -> container .. (Thursday, 7 March)
• Re: Affordances wiki page (Monday, 4 March)
• Re: LDP Agenda for March 4 (Monday, 4 March)
• Re: linking from resource -> container .. (Friday, 1 March)

Yves Lafon

• Re: ldp-ISSUE-49 (Canonical-URI): Canonical URL - how to communicate its value to clients (Wednesday, 13 March)
• Re: ldp-ISSUE-49 (Canonical-URI): Canonical URL - how to communicate its value to clients (Monday, 11 March)

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