Tuesday, 30 April 2013
- Re: On ISSUE-58: Property for asserting that complete description of members is included in LDPC representation
- Re: ldp-ISSUE-62 (siblings): Creating Sibling Containers [Linked Data Platform core]
- Re: On ISSUE-58: Property for asserting that complete description of members is included in LDPC representation
- Re: ldp-ISSUE-62 (siblings): Creating Sibling Containers [Linked Data Platform core]
- Re: On ISSUE-58: Property for asserting that complete description of members is included in LDPC representation
- Re: On ISSUE-58: Property for asserting that complete description of members is included in LDPC representation
- On ISSUE-58: Property for asserting that complete description of members is included in LDPC representation
- membershipSubject clarification
- Issue-32 affordances
- Re: ldp-ISSUE-62 (siblings): Creating Sibling Containers [Linked Data Platform core]
Monday, 29 April 2013
- LDP Minutes of April 29
- ldp-ISSUE-62 (siblings): Creating Sibling Containers [Linked Data Platform core]
- Re: Clarification on section 5.4.1
- Clarification on section 5.4.1
- Re: Proposal to close ISSUE-26 (creation model for LDP)
- Re: LDP Minutes for April 22
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior - take #2
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior - take #2
- Re: LDP Agenda for April 29
Sunday, 28 April 2013
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior - take #2
- LDP in Google Summer of Code with Scala
Saturday, 27 April 2013
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior - take #2
- Re: Fwd: access control vocabulary - where to start?
Friday, 26 April 2013
- LDP Agenda for April 29
- Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior - take #2
- Proposal to close ISSUE-26 (creation model for LDP)
- Regrets for Apr-29 <eom>
Thursday, 25 April 2013
- Re: ldp-ISSUE-61 (membershipSubject): remove membershipSubject [Linked Data Platform core]
- Re: ldp-ISSUE-61 (membershipSubject): remove membershipSubject [Linked Data Platform core]
- Re: ldp-ISSUE-61 (membershipSubject): remove membershipSubject [Linked Data Platform core]
Wednesday, 24 April 2013
Tuesday, 23 April 2013
- Re: ldp-ISSUE-61 (membershipSubject): remove membershipSubject [Linked Data Platform core]
- Re: ldp-ISSUE-61 (membershipSubject): remove membershipSubject [Linked Data Platform core]
- ldp-ISSUE-61 (membershipSubject): remove membershipSubject [Linked Data Platform core]
Monday, 22 April 2013
Sunday, 21 April 2013
Saturday, 20 April 2013
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
Friday, 19 April 2013
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: LDP Agenda for April 22
- Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Question regarding POST versus PUT for creating an LDPC
- LDP Agenda for April 22
- Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Question regarding POST versus PUT for creating an LDPC
Thursday, 18 April 2013
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Proposal to close ISSUE-35: POSTing to a container MUST yield a fresh URI
- Re: Access Control Requirements
- Re: Access Control Requirements
- Re: Access Control Requirements
- Re: Proposal to close ISSUE-35: POSTing to a container MUST yield a fresh URI
- Re: Question regarding POST versus PUT for creating an LDPC
Wednesday, 17 April 2013
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Recommendation for specification edits
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Proposal to close ISSUE-35: POSTing to a container MUST yield a fresh URI
- Proposal to close ISSUE-35: POSTing to a container MUST yield a fresh URI
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Question regarding POST versus PUT for creating an LDPC
- Re: Question regarding POST versus PUT for creating an LDPC
- Question regarding POST versus PUT for creating an LDPC
Monday, 15 April 2013
- LDP Minutes for April 15
- Re: Access Control Requirements
- Re: Access Control Requirements
- Re: Access Control Requirements
- Re: Recommendation for specification edits
- Re: Recommendation for specification edits
- Re: Recommendation for specification edits
- Re: ldp-ISSUE-58 (membersInlined): Property for asserting that complete description of members is included [Linked Data Platform core]
- Re: Access Control Requirements
- Re: Access Control Requirements
- Re: ldp-ISSUE-58 (membersInlined): Property for asserting that complete description of members is included [Linked Data Platform core]
- Re: ldp-ISSUE-58 (membersInlined): Property for asserting that complete description of members is included [Linked Data Platform core]
- Re: ldp-ISSUE-58 (membersInlined): Property for asserting that complete description of members is included [Linked Data Platform core]
- regrets for 4/22
- Re: Recommendation for specification edits
- Re : LDP agenda for April 15th
- Re: LDP agenda for April 15th
- Re: ldp-ISSUE-58 (membersInlined): Property for asserting that complete description of members is included [Linked Data Platform core]
- Re: Recommendation for specification edits
- Re: Access Control Requirements
- Re: Recommendation for concise definition of LDPR
- Re: Access Control Requirements
Sunday, 14 April 2013
Friday, 12 April 2013
- Re: LDP agenda for April 15th
- LDP agenda for April 15th
- Recommendation for concise definition of LDPR
- Recommendation for specification edits
Thursday, 11 April 2013
Tuesday, 9 April 2013
Monday, 8 April 2013
- for editors "don't forget" list
- LDP Minutes for April 8
- RE: LDP Agenda for April 8
- RE: LDP Agenda for April 8
Friday, 5 April 2013
- LDP Agenda for April 8
- 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]
Thursday, 4 April 2013
Wednesday, 3 April 2013
- Re: Trying to close ISSUE-14
- Re: Trying to close ISSUE-14
- Re: Trying to close ISSUE-14
- Re: Trying to close ISSUE-14
- Re: Trying to close ISSUE-14
- Re: Trying to close ISSUE-14
- Re: Trying to close ISSUE-14
Tuesday, 2 April 2013
- Re: Trying to close ISSUE-14
- Re: Trying to close ISSUE-14
- Re: Trying to close ISSUE-14
- Re: Trying to close ISSUE-14
- Re: Trying to close ISSUE-14
- Re: Trying to close ISSUE-14
- Re: Trying to close ISSUE-14
- Re: Trying to close ISSUE-14
- Trying to close ISSUE-14