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
membershipSubject clarification
Issue-32 affordances
LDP Minutes of April 29
ldp-ISSUE-62 (siblings): Creating Sibling Containers [Linked Data Platform core]
Clarification on section 5.4.1
LDP in Google Summer of Code with Scala
Re: Fwd: access control vocabulary - where to start?
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
- 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
Proposal to close ISSUE-26 (creation model for LDP)
Regrets for Apr-29 <eom>
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]
LDP Minutes for April 22
Access Control Requirements
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: 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
Proposal to close ISSUE-35: POSTing to a container MUST yield a fresh URI
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
- 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
- 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
- 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
LDP Minutes for April 15
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: ldp-ISSUE-58 (membersInlined): Property for asserting that complete description of members is included [Linked Data Platform core]
Access Control Requirements
LDP agenda for April 15th
Recommendation for concise definition of LDPR
Recommendation for specification edits
Google Summer of Code 2013 at W3C
for editors "don't forget" list
LDP Minutes for April 8
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]
Trying to close ISSUE-14
- Re: Trying to close ISSUE-14
- Re: Trying to close ISSUE-14