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

[Specifications] Add Use Case: Creating events indirectly (ie. with PUT)

[Specifications] Adding already existing resources as collection members

[Specifications] collections with manages block & Triple Pattern Fragments

[Specifications] CreateAction with HTTP PUT

[Specifications] Explicitly mention namespace in Core Vocabulary document

[Specifications] Introduce something like hydra:memberTemplate

[Specifications] Merged Pull Request: Explicitly mention namespace in Core Vocabulary document

[Specifications] new commits pushed by lanthaler

[Specifications] POST/PUT requests in use cases shouldn't use relative URLs to reference the context

[Specifications] Pull Request: Add Use Case: Creating events indirectly (ie. with PUT)

[Specifications] Recommend to use cache revalidation

[Specifications] Should spec mandate on server removing membership triple for deleted resources

[Specifications] Should we introduce a property to associate operations and their target directly to an entity?

Closed: [Specifications] Should spec mandate on server removing membership triple for deleted resources

Last message date: Tuesday, 31 October 2017 13:00:49 UTC