Friday, 31 May 2013
- Re: ldp-ISSUE-75 (monotonicity): rdf:membershipProperty makes LDP PATCHing non-monotonic [Linked Data Platform core]
- ISSUE-79 ldp:contains
- Re: ldp-ISSUE-75 (monotonicity): rdf:membershipProperty makes LDP PATCHing non-monotonic [Linked Data Platform core]
- Re: ldp-ISSUE-79 (ldp:contains): ldp:contains
- Re: ISSUE-75 Non-montonic - was: ISSUE-71: second bug tracking example
- Re: ldp-ISSUE-75 (monotonicity): rdf:membershipProperty makes LDP PATCHing non-monotonic [Linked Data Platform core]
- Looking Up Issues Using Linked Data URIs
- Re: ISSUE-75 Non-montonic - was: ISSUE-71: second bug tracking example
- Re: ldp-ISSUE-78 (inferencing): inferencing levels [Linked Data Platform Spec]
- Re: Proposal to close ISSUE-63: Need to be able to specify collation with container ordering per Ashok's suggestion
- Re: ISSUE-75 Non-montonic - was: ISSUE-71: second bug tracking example
- Re: ISSUE-75 Non-montonic - was: ISSUE-71: second bug tracking example
- Re: section 4.1.5
- Re: ldp-ISSUE-75 (monotonicity): rdf:membershipProperty makes LDP PATCHing non-monotonic [Linked Data Platform core]
- Re: ldp-ISSUE-79 (ldp:contains): ldp:contains
- Re: ISSUE-75 Non-montonic - was: ISSUE-71: second bug tracking example
- Re: ldp-ISSUE-79 (ldp:contains): ldp:contains
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ldp-ISSUE-79 (ldp:contains): ldp:contains
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: ISSUE-75 Non-montonic - was: ISSUE-71: second bug tracking example
- Re: ISSUE-75 (was ISSUE-71: second bug tracking example)
- Re: ISSUE-71: second bug tracking example
- Re: ISSUE-71: second bug tracking example
- ISSUE-75 Non-montonic - was: ISSUE-71: second bug tracking example
- Re: ldp-ISSUE-78 (inferencing): inferencing levels [Linked Data Platform Spec]
- Re: ldp-ISSUE-78 (inferencing): inferencing levels [Linked Data Platform Spec]
- Re: ldp-ISSUE-78 (inferencing): inferencing levels [Linked Data Platform Spec]
- ldp-ISSUE-79 (ldp:contains): ldp:contains
- Re: ldp-ISSUE-77 (types of LDPR ): why MUST a LDPR declare it's type ... ? [Linked Data Platform core]
- ldp-ISSUE-78 (inferencing): inferencing levels [Linked Data Platform Spec]
- Re: Issue-71: the first bug tracking example
- Re: ISSUE-75 (was ISSUE-71: second bug tracking example)
- ISSUE-67
- ISSUE-56/ISSUE-57
Thursday, 30 May 2013
- Re: ISSUE-75 (was ISSUE-71: second bug tracking example)
- Re: ISSUE-71: second bug tracking example
- Re: ISSUE-71: second bug tracking example
- Re: ISSUE-71: second bug tracking example
- Re: ISSUE-71: second bug tracking example
- Re: Issue-71: the first bug tracking example
- Re: ISSUE-71: second bug tracking example
- Re: ISSUE-71: second bug tracking example
- Re: ISSUE-71: second bug tracking example
- LDP agenda for June 3
- Proposal to close ISSUE-63: Need to be able to specify collation with container ordering per Ashok's suggestion
- Re: ldp-ISSUE-77 (types of LDPR ): why MUST a LDPR declare it's type ... ? [Linked Data Platform core]
- Re: ldp-ISSUE-77 (types of LDPR ): why MUST a LDPR declare it's type ... ? [Linked Data Platform core]
- Re: ldp-ISSUE-77 (types of LDPR ): why MUST a LDPR declare it's type ... ? [Linked Data Platform core]
- Re: ldp-ISSUE-75 (monotonicity): rdf:membershipProperty makes LDP PATCHing non-monotonic [Linked Data Platform core]
- Open issues at risk
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: ldp-ISSUE-75 (monotonicity): rdf:membershipProperty makes LDP PATCHing non-monotonic [Linked Data Platform core]
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: ldp-ISSUE-75 (monotonicity): rdf:membershipProperty makes LDP PATCHing non-monotonic [Linked Data Platform core]
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: ldp-ISSUE-77 (types of LDPR ): why MUST a LDPR declare it's type ... ? [Linked Data Platform core]
- Re: ldp-ISSUE-77 (types of LDPR ): why MUST a LDPR declare it's type ... ? [Linked Data Platform core]
- ldp-ISSUE-77 (types of LDPR ): why MUST a LDPR declare it's type ... ? [Linked Data Platform core]
- Re: ldp-ISSUE-75 (monotonicity): rdf:membershipProperty makes LDP PATCHing non-monotonic [Linked Data Platform core]
- Re: ldp-ISSUE-75 (monotonicity): rdf:membershipProperty makes LDP PATCHing non-monotonic [Linked Data Platform core]
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: Issue-71: the first bug tracking example
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
Wednesday, 29 May 2013
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- LDP F2F3 agenda
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: section 4.1.5
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ldp-ISSUE-75 (monotonicity): rdf:membershipProperty makes LDP PATCHing non-monotonic [Linked Data Platform core]
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- ldp-ISSUE-76 (rename membershipXXX): rename the ldp:membershipXXX properties [Linked Data Platform core]
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- ldp-ISSUE-75 (monotonicity): rdf:membershipProperty makes LDP PATCHing non-monotonic [Linked Data Platform core]
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: ISSUE-71: second bug tracking example
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: Issue-71: the first bug tracking example
- Re: Issue-71: the first bug tracking example
- Re: ISSUE-71: second bug tracking example
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: Missing use case for supporting ldp:membershipPredicate/Subject
- Re: ISSUE-71: second bug tracking example
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ISSUE-71: second bug tracking example
- Re: Issue-71: the first bug tracking example
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: Issue-71: the first bug tracking example
- section 4.1.5
- container-first or entity-first ?
- Re: Issue-71: the first bug tracking example
- Re: Proposal to close ISSUE-67: Full container membership without pagination, saying no.
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ISSUE-71: second bug tracking example
Tuesday, 28 May 2013
- Re: Issue-71: the first bug tracking example
- Re: ISSUE-58: the simple solution to inlined membership
- Missing use case for supporting ldp:membershipPredicate/Subject
- Re: Proposal to close ISSUE-67: Full container membership without pagination, saying no.
- Re: Proposal to close ISSUE-17: changesets as a recommended PATCH format, as is
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: Binary resource and metadata example (ISSUE-15)
- Re: Issue-71: the first bug tracking example
- Re: Binary resource and metadata example (ISSUE-15)
- Re: ISSUE-71: second bug tracking example
- Re: ISSUE-71: second bug tracking example
Monday, 27 May 2013
Saturday, 25 May 2013
- Re: Proposal to close ISSUE-67: Full container membership without pagination, saying no.
- Re: Proposal to close ISSUE-17: changesets as a recommended PATCH format, as is
- Re: Proposal to close ISSUE-17: changesets as a recommended PATCH format, as is
Friday, 24 May 2013
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Proposal to close ISSUE-67: Full container membership without pagination, saying no.
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Proposal to close ISSUE-19: Adressing more error cases, as is
- Proposal to close ISSUE-17: changesets as a recommended PATCH format, as is
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: An LDP example with and without membershipSubject predicate
Thursday, 23 May 2013
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ldp-ISSUE-74 (conditional requests required): How does a client know if conditional requests are required [Linked Data Platform core]
- Issue-64 (Non-member-properties HATEOAS Compliance) proposal to resolve
- ldp-ISSUE-74 (conditional requests required): How does a client know if conditional requests are required [Linked Data Platform core]
- ldp-ISSUE-32 (affordances): new issues coming
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ISSUE-71: second bug tracking example
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- ldp-ISSUE-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
- Re: ISSUE-71: second bug tracking example
- Re: Specification edits for Issue-54 resolution
- membershipPredicates or not ?
- Specification edits for Issue-54 resolution
- Re: ISSUE-71: second bug tracking example
- Re: Issue-71: the first bug tracking example
- Re: ISSUE-71: second bug tracking example
Wednesday, 22 May 2013
- Re: Issue-71: the first bug tracking example
- Re: Issue-71: the first bug tracking example
- Re: Issue-71: the first bug tracking example
- Re: ldp-ISSUE-72 (membershipObject): The object of a membership triple isn't always the address of the created informational resource [Linked Data Platform core]
- LDP Minutes for May 13 and May 20
- Re: ldp-ISSUE-72 (membershipObject): The object of a membership triple isn't always the address of the created informational resource [Linked Data Platform core]
- Re: Issue-71: the first bug tracking example
- Re: ldp-ISSUE-72 (membershipObject): The object of a membership triple isn't always the address of the created informational resource [Linked Data Platform core]
- Re: Issue-71: the first bug tracking example
- Re: ldp-ISSUE-72 (membershipObject): The object of a membership triple isn't always the address of the created informational resource [Linked Data Platform core]
- Re: Issue-71: the first bug tracking example
- Re: ldp-ISSUE-72 (membershipObject): The object of a membership triple isn't always the address of the created informational resource [Linked Data Platform core]
- Re: ldp-ISSUE-72 (membershipObject): The object of a membership triple isn't always the address of the created informational resource [Linked Data Platform core]
- Re: Issue-71: the first bug tracking example
- Re: ldp-ISSUE-72 (membershipObject): The object of a membership triple isn't always the address of the created informational resource [Linked Data Platform core]
- Re: ldp-ISSUE-72 (membershipObject): The object of a membership triple isn't always the address of the created informational resource [Linked Data Platform core]
- Re: ldp-ISSUE-72 (membershipObject): The object of a membership triple isn't always the address of the created informational resource [Linked Data Platform core]
- Re: Issue-71: the first bug tracking example
- Re: Issue-71: the first bug tracking example
- Re: ldp-ISSUE-72 (membershipObject): The object of a membership triple isn't always the address of the created informational resource [Linked Data Platform core]
- Re: Issue-71: the first bug tracking example
- ldp-ISSUE-72 (membershipObject): The object of a membership triple isn't always the address of the created informational resource [Linked Data Platform core]
- Re: Issue-71: the first bug tracking example
- Re: Issue-71: the first bug tracking example
- Re: Issue-71: the first bug tracking example
- Re: Issue-71: the first bug tracking example
- Re: Issue-71: the first bug tracking example
Tuesday, 21 May 2013
- Re: Issue-71: the first bug tracking example
- ISSUE-71: second bug tracking example
- Re: Issue-71: the first bug tracking example
- Re: Issue-71: the first bug tracking example
- Re: Issue-71: the first bug tracking example
- Re: Issue-71: the first bug tracking example
- Issue-71: the first bug tracking example
- membershipX: the first bug tracking example
- Re: An LDP example with and without membershipSubject predicate
- ldp-ISSUE-71 (membershipX): No membershipSubject or membershipPredicate [Linked Data Platform core]
- Re: An LDP example with and without membershipSubject predicate
- Re: LD 5th Element ?
- Re: An LDP example with and without membershipSubject predicate
- An LDP example with and without membershipSubject predicate
- Re: LD 5th Element ?
- Re: LDP F2F @ TPAC?
- Re: LD 5th Element ?
- Re: LD 5th Element ?
- Re: LD 5th Element ?
- Re: LD 5th Element ?
- Re: LD 5th Element ?
- Re: LD 5th Element ?
- Re: LD 5th Element ?
- LD 5th Element ?
Monday, 20 May 2013
- Re: LDP F2F @ TPAC?
- Re: LDP F2F @ TPAC?
- Re: Recommendation for concise definition of LDPR
- LDP F2F @ TPAC?
- Re: Recommendation for concise definition of LDPR
- Re: First draft of test cases
- Re: Server behaviour on PUT
- Re: Server behaviour on PUT
- Re: ISSUE-58: the simple solution to inlined membership
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
Sunday, 19 May 2013
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
- Re: ISSUE-58: the simple solution to inlined membership
- Re: ISSUE-58: the simple solution to inlined membership
- Re: ISSUE-58: the simple solution to inlined membership
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
- Re: LDP Agenda for May 20
- ISSUE-58: the simple solution to inlined membership
- LDP Agenda for May 20
- Re: Server behaviour on PUT
- Re: Need new Product(s) in Tracker
- Re: Define a minimal restriction on LDPR representations
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
Saturday, 18 May 2013
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
- Conclusion -- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
- Re: ISSUE-58: the simple solution to inlined membership
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
- Re: ISSUE-58: the simple solution to inlined membership
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
- Re: ISSUE-58: the simple solution to inlined membership - ISSUE-45
- Re: ISSUE-58: the simple solution to inlined membership
- Re: ISSUE-58: the simple solution to inlined membership
- Re: ldp-ISSUE-70 (simple LDPCs): simple LDPCs [Linked Data Platform core]
- ldp-ISSUE-70 (simple LDPCs): simple LDPCs [Linked Data Platform core]
- Re: ISSUE-58: the simple solution to inlined membership
- Re: Recommendation for concise definition of LDPR
Friday, 17 May 2013
- Re: Recommendation for concise definition of LDPR
- Re: Recommendation for specification edits
- Need new Product(s) in Tracker
- Re: Server behaviour on PUT
- Re: Alternatives for using ETags
- Re: Status codes for DELETE
- Re: HEAD vs OPTIONS
- Re: Status codes for DELETE
- Re: Status codes for DELETE
- Re: Issue-32 affordances
- Re: Define a minimal restriction on LDPR representations
- Re: Status codes for DELETE
- Re: On ISSUE-58: Property for asserting that complete description of members is included in LDPC representation
- Re: Define a minimal restriction on LDPR representations
Thursday, 16 May 2013
- Re: ISSUE-58: the simple solution to inlined membership
- Re: Define a minimal restriction on LDPR representations
- Re: ISSUE-58: the simple solution to inlined membership
- Define a minimal restriction on LDPR representations
- HEAD vs OPTIONS
- Status codes for DELETE
- Alternatives for using ETags
- Server behaviour on PUT
- Re: An editorial suggestion for 5.2.2 in the spec
- Re: ISSUE-58: the simple solution to inlined membership
- Re: An editorial suggestion for 5.2.2 in the spec
Wednesday, 15 May 2013
- Re: ISSUE-58: the simple solution to inlined membership
- Re: ISSUE-58: the simple solution to inlined membership
- Re: ISSUE-58: the simple solution to inlined membership
- Re: ISSUE-58: the simple solution to inlined membership
- Re: On ISSUE-58: Property for asserting that complete description of members is included in LDPC representation
- Re: ISSUE-58: the simple solution to inlined membership
- Re: On ISSUE-58: Property for asserting that complete description of members is included in LDPC representation
- Re: An editorial suggestion for 5.2.2 in the spec
- Re: ISSUE-58: the simple solution to inlined membership
- Re: ISSUE-58: the simple solution to inlined membership
- Re: ISSUE-58: the simple solution to inlined membership
- Re: ISSUE-58: the simple solution to inlined membership
Tuesday, 14 May 2013
- Re: ISSUE-58: the simple solution to inlined membership
- Re: On ISSUE-58: Property for asserting that complete description of members is included in LDPC representation
- Re: Issue-32 affordances
- An editorial suggestion for 5.2.2 in the spec
Monday, 13 May 2013
- Re: ISSUE-58: the simple solution to inlined membership
- ISSUE-58: the simple solution to inlined membership
- Regrets for May 20 & 27 (Memorial Day, USA)
- Re: LDP minutes for May 6
Saturday, 11 May 2013
Friday, 10 May 2013
- Re: Proposal to close Issue-65: FirstPage HATEOAS Compliance
- Re: Proposal to close Issue-65: FirstPage HATEOAS Compliance
- Re: Proposal to close Issue-65: FirstPage HATEOAS Compliance
- Re: Proposal to close Issue-65: FirstPage HATEOAS Compliance
- LDP Agenda for May 13
- Re: First draft of test cases
- Proposal to close Issue-65: FirstPage HATEOAS Compliance
- First draft of test cases
- Re: Do we need transaction support in LDP?
- Re: Do we need transaction support in LDP?
- Re: Do we need transaction support in LDP?
Thursday, 9 May 2013
- Re: Do we need transaction support in LDP?
- Re: Do we need transaction support in LDP?
- Re: Do we need transaction support in LDP?
- Re: Do we need transaction support in LDP?
- Re: Do we need transaction support in LDP?
- Re: Do we need transaction support in LDP?
- Re: LDP minutes for May 6
- Fwd: Re: Do we need transaction support in LDP?
- Fwd: Re: Do we need transaction support in LDP?
- Re: Access Control Requirements
- Re: Access Control Requirements
- Re: Do we need transaction support in LDP?
- Do we need transaction support in LDP?
Wednesday, 8 May 2013
- Re: membershipSubject clarification
- Re: LDP minutes for May 6
- Re: ldp-ISSUE-62 (siblings): Creating Sibling Containers [Linked Data Platform core]
- 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: membershipSubject clarification
- Re: On ISSUE-58: Property for asserting that complete description of members is included in LDPC representation
Tuesday, 7 May 2013
Monday, 6 May 2013
- Proposal to close ISSUE-69, as is
- LDP minutes for May 6
- Re: LDP Issues list maintenance
- ldp-ISSUE-69: Query syntaxes for accessing the first and subsequent pages
- LDP Issues list maintenance
- ldp-ISSUE-68: Number of resources per page
- ldp-ISSUE-67: Full container membership without pagination
- ldp-ISSUE-66: Robust pagination [Linked Data Platform core]
- ldp-ISSUE-65 (FirstPage HATEOAS Compliance): FirstPage and Hypermedia as the Engine of Application State (HATEOAS) Compliance [Linked Data Platform core]
- ldp-ISSUE-64 (Non-member-properties HATEOAS Compliance): Non-member-properties and Hypermedia as the Engine of Application State (HATEOAS) Compliance [Linked Data Platform core]
- How much REST should your web API get?
- 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
- 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
- Re: On ISSUE-58: Property for asserting that complete description of members is included in LDPC representation
- ldp-ISSUE-63 (Collation Support): Need to be able to specify collation with container ordering [Linked Data Platform core]
- Re: On ISSUE-58: Property for asserting that complete description of members is included in LDPC representation
- Re: membershipSubject clarification
- Re: PUT,POST,PATCH of <> a ldp:Container
- Re: membershipSubject clarification
Friday, 3 May 2013
- Re: LDP agenda for May 6
- Re: LDP agenda for May 6
- LDP agenda for May 6
- Re: PUT,POST,PATCH of <> a ldp:Container
- Re: membershipSubject clarification
- Re: membershipSubject clarification
- Re: On ISSUE-58: Property for asserting that complete description of members is included in LDPC representation
- Re: PUT,POST,PATCH of <> a ldp:Container
Thursday, 2 May 2013
- Re: PUT,POST,PATCH of <> a ldp:Container
- PUT,POST,PATCH of <> a ldp:Container
- Re: membershipSubject clarification
Wednesday, 1 May 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: ldp-ISSUE-62 (siblings): Creating Sibling Containers [Linked Data Platform core]
- 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]