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

[Specifications] "@type": "@id" in JSON-LD context of use cases

[Specifications] Interoperability with Linked Data Platform (especially regarding collections and paging)

[Specifications] Merged Pull Request: "@type": "@id" in JSON-LD context of use cases

[Specifications] Merged Pull Request: Add use case: Create resource

[Specifications] Merged Pull Request: Add use case: Filter resources

[Specifications] Merged Pull Request: Add use case: Retrieve resource

[Specifications] Merged Pull Request: Add use case: Search resources

[Specifications] Merged Pull Request: Add use case: Update resource

[Specifications] Merged Pull Request: Let's consider a use case when a Hydra client obtains events.

[Specifications] Merged Pull Request: Let's consider an API documentation fetch use case for the Hydra client.

[Specifications] Merged Pull Request: Let's consider first an entry-point use case of the Hydra client.

[Specifications] Merged Pull Request: Same IRI must not denote both - the operation and the api resource which supports that operation

[Specifications] new commits pushed by lanthaler

[Specifications] Pull Request: "@type": "@id" in JSON-LD context of use cases

[Specifications] Pull Request: Let's discuss another case related to simple search scenario

[Specifications] Pull Request: Let's discuss another use case related to filtering in general.

[Specifications] Pull Request: Please consider another use case with updating a resource.

[Specifications] Pull Request: Same IRI must not denote both - the operation and the api resource which supports that operation

[Specifications] Same IRI must not denote both - the operation and the api resource which supports that operation

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