Looking Up Issues Using Linked Data URIs
ldp-ISSUE-79 (ldp:contains): ldp:contains
ldp-ISSUE-78 (inferencing): inferencing levels [Linked Data Platform Spec]
ISSUE-67
LDP agenda for June 3
Proposal to close ISSUE-63: Need to be able to specify collation with container ordering per Ashok's suggestion
Open issues at risk
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-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 F2F3 agenda
ldp-ISSUE-76 (rename membershipXXX): rename the ldp:membershipXXX properties [Linked Data Platform core]
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-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]
section 4.1.5
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
- 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
- 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
- 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
Binary resource and metadata example (ISSUE-15)
- Re: Binary resource and metadata example (ISSUE-15)
- Re: Binary resource and metadata example (ISSUE-15)
Proposal to close ISSUE-67: Full container membership without pagination, saying no.
Proposal to close ISSUE-19: Adressing more error cases, as is
Proposal to close ISSUE-17: changesets as a recommended PATCH format, as is
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-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-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-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-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-73 (rdf:member): LDPCs to list all their rdf:member [Linked Data Platform core]
membershipPredicates or not ?
Specification edits for Issue-54 resolution
LDP Minutes for May 13 and May 20
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: 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: 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]
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: 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: 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-75 (was ISSUE-71: second bug tracking example)
- ISSUE-56/ISSUE-57
- Re: ISSUE-75 (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
- Re: ISSUE-71: second bug tracking example
- ISSUE-75 Non-montonic - was: ISSUE-71: second bug tracking example
- 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: ISSUE-75 Non-montonic - was: ISSUE-71: second bug tracking example
- 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: ISSUE-75 Non-montonic - was: ISSUE-71: second bug tracking example
- ISSUE-79 ldp:contains
- Re: ISSUE-71: second bug tracking example
- Re: ISSUE-71: second bug tracking example
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
- 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
- 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
membershipX: the first bug tracking example
ldp-ISSUE-71 (membershipX): No membershipSubject or membershipPredicate [Linked Data Platform core]
An LDP example with and without membershipSubject predicate
LD 5th Element ?
LDP F2F @ TPAC?
ISSUE-58: the simple solution to inlined membership
LDP Agenda for May 20
ldp-ISSUE-70 (simple LDPCs): simple LDPCs [Linked Data Platform core]
Re: Recommendation for concise definition of LDPR
Re: Recommendation for specification edits
Need new Product(s) in Tracker
Define a minimal restriction on LDPR representations
HEAD vs OPTIONS
Status codes for DELETE
Alternatives for using ETags
Server behaviour on PUT
Re: Issue-32 affordances
An editorial suggestion for 5.2.2 in the spec
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: 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: 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: 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: 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 - 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 - 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: 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: 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 - 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: ISSUE-58: the simple solution to inlined membership
Regrets for May 20 & 27 (Memorial Day, USA)
LDP Agenda for May 13
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
First draft of test cases
Fwd: Re: Do we need transaction support in LDP?
Fwd: Re: Do we need transaction support in LDP?
Re: Access Control Requirements
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?
Proposal to close ISSUE-69, as is
LDP minutes for May 6
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?
ldp-ISSUE-63 (Collation Support): Need to be able to specify collation with container ordering [Linked Data Platform core]
LDP agenda for May 6
PUT,POST,PATCH of <> a ldp:Container
Re: membershipSubject clarification
- Re: membershipSubject clarification
- Re: membershipSubject clarification
- Re: membershipSubject clarification
- Re: membershipSubject clarification
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
- 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