public-hydra-logs@w3.org from May 2017 by date

Monday, 29 May 2017

• [Specifications] new commits pushed by lanthaler Markus Lanthaler via GitHub
• [Specifications] Merged Pull Request: Same IRI must not denote both - the operation and the api resource which supports that operation Markus Lanthaler via GitHub
• [Specifications] new commits pushed by lanthaler Markus Lanthaler via GitHub
• [Specifications] Merged Pull Request: Add use case: Filter resources Markus Lanthaler via GitHub
• [Specifications] new commits pushed by lanthaler Markus Lanthaler via GitHub
• [Specifications] Merged Pull Request: Add use case: Search resources Markus Lanthaler via GitHub
• [Specifications] Merged Pull Request: Add use case: Update resource Markus Lanthaler via GitHub
• [Specifications] new commits pushed by lanthaler Markus Lanthaler via GitHub
• [Specifications] Merged Pull Request: Add use case: Create resource Markus Lanthaler via GitHub
• [Specifications] new commits pushed by lanthaler Markus Lanthaler via GitHub
• [Specifications] Merged Pull Request: Add use case: Retrieve resource Markus Lanthaler via GitHub
• [Specifications] new commits pushed by lanthaler Markus Lanthaler via GitHub
• Re: [Specifications] Interoperability with Linked Data Platform (especially regarding collections and paging) elf Pavlik via GitHub

Saturday, 27 May 2017

• Re: [Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation elf Pavlik via GitHub

Thursday, 25 May 2017

• Re: [Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation Markus Lanthaler via GitHub

Monday, 22 May 2017

• Re: [Specifications] Interoperability with Linked Data Platform (especially regarding collections and paging) Asbjørn Ulsberg via GitHub
• Re: [Specifications] Interoperability with Linked Data Platform (especially regarding collections and paging) Asbjørn Ulsberg via GitHub
• Re: [Specifications] Interoperability with Linked Data Platform (especially regarding collections and paging) Ruben Verborgh via GitHub
• Re: [Specifications] Interoperability with Linked Data Platform (especially regarding collections and paging) Asbjørn Ulsberg via GitHub

Sunday, 7 May 2017

• [Specifications] Pull Request: Let's discuss another use case related to filtering in general. Karol Szczepański via GitHub
• [Specifications] Pull Request: Let's discuss another case related to simple search scenario Karol Szczepański via GitHub
• Re: [Specifications] "@type": "@id" in JSON-LD context of use cases Markus Lanthaler via GitHub
• [Specifications] Merged Pull Request: "@type": "@id" in JSON-LD context of use cases Markus Lanthaler via GitHub
• [Specifications] new commits pushed by lanthaler Markus Lanthaler via GitHub

Wednesday, 3 May 2017

• Re: [Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation elf Pavlik via GitHub
• [Specifications] Pull Request: Please consider another use case with updating a resource. Karol Szczepański via GitHub
• Re: [Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation Tomasz Pluskiewicz via GitHub
• Re: [Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation Karol Szczepański via GitHub
• Re: [Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation elf Pavlik via GitHub
• Re: [Specifications] "@type": "@id" in JSON-LD context of use cases Markus Lanthaler via GitHub
• Re: [Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation Markus Lanthaler via GitHub
• Re: [Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation elf Pavlik via GitHub
• Re: [Specifications] "@type": "@id" in JSON-LD context of use cases elf Pavlik via GitHub

Tuesday, 2 May 2017

• Re: [Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation Markus Lanthaler via GitHub
• Re: [Specifications] "@type": "@id" in JSON-LD context of use cases Tomasz Pluskiewicz via GitHub
• Re: [Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation Tomasz Pluskiewicz via GitHub
• Re: [Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation Karol Szczepański via GitHub
• Re: [Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation Tomasz Pluskiewicz via GitHub
• Re: [Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation Karol Szczepański via GitHub
• Re: [Specifications] "@type": "@id" in JSON-LD context of use cases Karol Szczepański via GitHub
• [Specifications] Pull Request: Same IRI must not denote both - the operation and the api resource which supports that operation elf Pavlik via GitHub

Monday, 1 May 2017

• [Specifications] Pull Request: "@type": "@id" in JSON-LD context of use cases elf Pavlik via GitHub
• [Specifications] new commits pushed by lanthaler Markus Lanthaler via GitHub
• [Specifications] Merged Pull Request: Let's consider a use case when a Hydra client obtains events. Markus Lanthaler via GitHub
• [Specifications] new commits pushed by lanthaler Markus Lanthaler via GitHub
• [Specifications] Merged Pull Request: Let's consider an API documentation fetch use case for the Hydra client. Markus Lanthaler via GitHub
• [Specifications] new commits pushed by lanthaler Markus Lanthaler via GitHub
• [Specifications] Merged Pull Request: Let's consider first an entry-point use case of the Hydra client. Markus Lanthaler via GitHub

Last message date: Monday, 29 May 2017 19:18:14 UTC