public-hydra@w3.org from February 2014 by subject

ActionHandlers vs "App resources" (was: An updated draft of the schema.org/Action proposal)

An updated draft of the schema.org/Action proposal

An updated draft of the schema.org/Actions proposal!

concerns about hydra:mappings

concerns about hydra:mappings (ISSUE-30)

Define/change the range of "supportedProperties" (ISSUE-37)

Hydra Vocab and Content Negotiation

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

Interoperability with Linked Data Platform (especially regarding collections and paging) ISSUE-36

ISSUE-31: Are Operations violating REST's uniform interface constraint?

ISSUE-31: Are Operations violating REST's uniform interface constraint? (was: More Thoughts on Links and Operation Subclasses)

ISSUE-32: Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling?

ISSUE-32: Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? (was: More Thoughts on Links and Operation Subclasses)

More Thoughts on Links and Operation Subclasses

My opinion about hydra vocabulary

Nested structures / ISSUE-26

Nested structures / ISSUE-26 (was: An updated draft of the schema.org/Action proposal)

plural properties should become singular

Properties and types differing only in their capitalization ISSUE-28 (was: plural properties should become singular)

Reconciling hydra rest semantics for collections with typical RDF entity relationships

removing hydra:search

Singularization of properties and its consequences (ISSUE-25, ISSUE-27 & ISSUE-28)

StatusCodeDescription vs. Status (ISSUE-32)

terminology/necessity of hydra:required

Unsubscribing

W3C standardization process

Wrap up and Discussion of ways to Specify Supported Properties and corresponding Validation Rules for Operations

Last message date: Friday, 28 February 2014 21:08:24 UTC