Saturday, 30 March 2013
- 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
Friday, 29 March 2013
Thursday, 28 March 2013
Wednesday, 27 March 2013
- Re: how to know that something was DELETEd
- Re: how to know that something was DELETEd
- Re: how to know that something was DELETEd
- Re: how to know that something was DELETEd
- Re: how to know that something was DELETEd
- Re: how to know that something was DELETEd
- Re: how to know that something was DELETEd
- Re: how to know that something was DELETEd
- Re: how to know that something was DELETEd
- Re: how to know that something was DELETEd
- Re: how to know that something was DELETEd
- how to know that something was DELETEd
Tuesday, 26 March 2013
- Re: 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
- Re: ACTION-43 Draft use case for ordering
- Re: ACTION-43 Draft use case for ordering
Monday, 25 March 2013
- Re: ACTION-43 Draft use case for ordering
- Re: ACTION-43 Draft use case for ordering
- LDP Minutes for March 25
- Re: 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
- Re: 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
- Re: ACTION-43 Draft use case for ordering
- Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
- Re: LDP agenda for March 25
- ACTION-43 Draft use case for ordering
- Re: LDP agenda for March 25
- Re: LDP agenda for March 25
- Re: LDP agenda for March 25
- Re: LDP agenda for March 25
Sunday, 24 March 2013
Friday, 22 March 2013
- Re: ldp-ISSUE-60 (GETting empty containers): The specification does not allow GETting empty containers [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-ISSUE-60 (GETting empty containers): The specification does not allow GETting empty containers [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]
Thursday, 21 March 2013
- 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: issue-13 amended proposal
Wednesday, 20 March 2013
- 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: Containers and membership subject/object asymmetry
- Re: issue-13 amended proposal
- RE: Containers and membership subject/object asymmetry
- RE: issue-13 amended proposal
- Re: Containers and membership subject/object asymmetry
- Re: issue-13 amended proposal
- re: Containers and membership subject/object asymmetry
- Containers and membership subject/object asymmetry
- RE: issue-13 amended proposal
- 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 2013
- Re: issue-13 amended proposal
- Re: issue-13 amended proposal
- 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]
- issue-13 amended proposal
- 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-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core]
Sunday, 17 March 2013
Saturday, 16 March 2013
- Re: A minimalist proposal for issue-50
- 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 2013
- LDP Minutes for March 15
- 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: ldp-ISSUE-58 (membersInlined): Property for asserting that complete description of members is included [Linked Data Platform core]
- 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: issue-21 proposal
- Re: ldp-ISSUE-55 (HATEOAS Compliance): Hypermedia as the Engine of Application State (HATEOAS) Compliance [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: Peter's friends
- Re: Section 5.4.8 null relative URI
- 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
Thursday, 14 March 2013
- Re: A minimalist proposal for issue-50
- A minimalist proposal for issue-50
- Dinner for those who enjoy pain
- Re: LDP Minutes for March 13
- Traffic on the comments list
- atomic operations of LDP
- 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 for March 13
Wednesday, 13 March 2013
- 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
- ldp-ISSUE-51 ('backlinks'): Linking from a Resource to its Containers (aka 'backlinks') [Linked Data Platform core]
- Re: A modest attempt to re-open ISSUE-20
- issue-21 proposal
- 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: linking from resource -> container ..
- 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
- Re: A modest attempt to re-open ISSUE-20
- Re: A modest attempt to re-open ISSUE-20
Tuesday, 12 March 2013
- Testing: schemas and procedures
- Re: A modest attempt to re-open ISSUE-20
- A modest attempt to re-open ISSUE-20
- Re: Considering a PATCH model for LDP
- Re: F2F2 confirmation
- Re: ldp-ISSUE-49 (Canonical-URI): Canonical URL - how to communicate its value to clients
Monday, 11 March 2013
- Re: F2F2 confirmation
- LDP Minutes of March 11
- Re: linking from resource -> container ..
- Re: Considering a PATCH model for LDP
- Re: Considering a PATCH model for LDP
- Re: ldp-ISSUE-49 (Canonical-URI): Canonical URL - how to communicate its value to clients
- Re: Considering a PATCH model for LDP
- Re: Considering a PATCH model for LDP
- Re: Considering a PATCH model for LDP
- Re : LDP Agenda for March 11
- Re: ldp-ISSUE-49 (Canonical-URI): Canonical URL - how to communicate its value to clients
- Re: linking from resource -> container ..
- Re: Considering a PATCH model for LDP
- Re: Considering a PATCH model for LDP
Sunday, 10 March 2013
- Re: linking from resource -> container ..
- Re: Considering a PATCH model for LDP
- Re: linking from resource -> container ..
- Re: LDP Agenda for March 11
Saturday, 9 March 2013
Friday, 8 March 2013
- Fw: Daylight Saving Time change –first half of 2013
- LDP Agenda for March 11
- Re: Aggregate/Container
- Aggregate/Container
- Re: linking from resource -> container ..
- Re: linking from resource -> container ..
Thursday, 7 March 2013
- Re: linking from resource -> container ..
- Re: linking from resource -> container ..
- Re: The Intuitive/ Requirement
- Re: linking from resource -> container ..
- Re: linking from resource -> container ..
- Re: 2nd LDP Public Working Draft published
- 2nd LDP Public Working Draft published
- Re: linking from resource -> container ..
- Re: linking from resource -> container ..
- Re: linking from resource -> container ..
Wednesday, 6 March 2013
Tuesday, 5 March 2013
Monday, 4 March 2013
- LDP Minutes of March 4
- Re: linking from resource -> container ..
- Editor's draft is ready to advance to 2nd Public Working Draft
- Re: Review and Comments for Linked Data Platform FPWD
- Re: linking from resource -> container ..
- Re: linking from resource -> container ..
- ZAKIM PROBLEM
- ldp:contains was: linking from resource -> container ..
- Re: LDP Agenda for March 4
- Re: Affordances wiki page
- Re: Affordances wiki page
- Re: Affordances wiki page
- Re: Affordances wiki page
- Re: Affordances wiki page
- Re: ldp-ISSUE-50 (intuitive containers): Inuitive Containers: better support for relative URIs
- ldp-ISSUE-50 (intuitive containers): Inuitive Containers: better support for relative URIs
- Re: Affordances wiki page
- Re: The Intuitive/ Requirement
- Re: LDP Agenda for March 4
- Re: LDP Agenda for March 4
- Re: LDP Agenda for March 4
- Re: LDP Agenda for March 4
Sunday, 3 March 2013
Saturday, 2 March 2013
Friday, 1 March 2013
- Re: linking from resource -> container ..
- Re: F2F2 confirmation
- F2F2 confirmation
- Re: The Intuitive/ Requirement
- Re: linking from resource -> container ..
- Re: linking from resource -> container ..
- Re: linking from resource -> container ..
- Re: linking from resource -> container ..
- Re: The Intuitive/ Requirement
- Re: The Intuitive/ Requirement