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

Andreas Kuckartz

• Interoperability with Linked Data Platform (especially regarding collections and paging) (Sunday, 9 February)
• Re: Unsubscribing (Friday, 7 February)
• Unsubscribing (Friday, 7 February)

Gregg Kellogg

• Re: terminology/necessity of hydra:required (Tuesday, 11 February)
• Re: terminology/necessity of hydra:required (Monday, 10 February)
• Re: Reconciling hydra rest semantics for collections with typical RDF entity relationships (Thursday, 6 February)
• Re: Reconciling hydra rest semantics for collections with typical RDF entity relationships (Tuesday, 4 February)
• Re: Reconciling hydra rest semantics for collections with typical RDF entity relationships (Tuesday, 4 February)
• Reconciling hydra rest semantics for collections with typical RDF entity relationships (Monday, 3 February)
• Re: More Thoughts on Links and Operation Subclasses (Monday, 3 February)
• Re: plural properties should become singular (Monday, 3 February)

James Langley

• Re: W3C standardization process (Thursday, 13 February)

Judson Lester

• Re: Reconciling hydra rest semantics for collections with typical RDF entity relationships (Thursday, 6 February)
• Re: Reconciling hydra rest semantics for collections with typical RDF entity relationships (Thursday, 6 February)

Kingsley Idehen

• Hydra Vocab and Content Negotiation (Saturday, 15 February)
• Re: Nested structures / ISSUE-26 (Friday, 14 February)
• Re: An updated draft of the schema.org/Action proposal (Tuesday, 11 February)
• Re: terminology/necessity of hydra:required (Monday, 10 February)
• Re: ISSUE-31: Are Operations violating REST's uniform interface constraint? (Friday, 7 February)
• Re: Singularization of properties and its consequences (ISSUE-25, ISSUE-27 & ISSUE-28) (Thursday, 6 February)
• Re: terminology/necessity of hydra:required (Wednesday, 5 February)
• Re: plural properties should become singular (Wednesday, 5 February)
• Re: Reconciling hydra rest semantics for collections with typical RDF entity relationships (Tuesday, 4 February)
• Re: ISSUE-32: Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? (Tuesday, 4 February)
• Re: ISSUE-32: Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? (Tuesday, 4 February)
• Re: More Thoughts on Links and Operation Subclasses (Tuesday, 4 February)
• Re: More Thoughts on Links and Operation Subclasses (Tuesday, 4 February)
• Re: More Thoughts on Links and Operation Subclasses (Monday, 3 February)
• Re: More Thoughts on Links and Operation Subclasses (Monday, 3 February)
• Re: More Thoughts on Links and Operation Subclasses (Monday, 3 February)
• Re: plural properties should become singular (Monday, 3 February)

László Lajos Jánszky

• Re: My opinion about hydra vocabulary (Tuesday, 4 February)

Mark Baker

• Re: ISSUE-31: Are Operations violating REST's uniform interface constraint? (was: More Thoughts on Links and Operation Subclasses) (Friday, 21 February)
• Re: ISSUE-31: Are Operations violating REST's uniform interface constraint? (was: More Thoughts on Links and Operation Subclasses) (Wednesday, 12 February)
• Re: ISSUE-31: Are Operations violating REST's uniform interface constraint? (was: More Thoughts on Links and Operation Subclasses) (Thursday, 6 February)

Markus Lanthaler

• RE: removing hydra:search (Friday, 28 February)
• RE: ISSUE-31: Are Operations violating REST's uniform interface constraint? (was: More Thoughts on Links and Operation Subclasses) (Friday, 28 February)
• RE: ISSUE-31: Are Operations violating REST's uniform interface constraint? (Friday, 28 February)
• RE: concerns about hydra:mappings (ISSUE-30) (Friday, 28 February)
• RE: Singularization of properties and its consequences (ISSUE-25, ISSUE-27 & ISSUE-28) (Saturday, 22 February)
• RE: concerns about hydra:mappings (ISSUE-30) (Tuesday, 18 February)
• RE: ISSUE-31: Are Operations violating REST's uniform interface constraint? (Tuesday, 18 February)
• RE: ActionHandlers vs "App resources" (was: An updated draft of the schema.org/Action proposal) (Monday, 17 February)
• RE: concerns about hydra:mappings (ISSUE-30) (Monday, 17 February)
• RE: ISSUE-31: Are Operations violating REST's uniform interface constraint? (Monday, 17 February)
• RE: Define/change the range of "supportedProperties" (ISSUE-37) (Monday, 17 February)
• RE: Singularization of properties and its consequences (ISSUE-25, ISSUE-27 & ISSUE-28) (Monday, 17 February)
• RE: concerns about hydra:mappings (ISSUE-30) (Monday, 17 February)
• RE: removing hydra:search (Monday, 17 February)
• RE: ActionHandlers vs "App resources" (was: An updated draft of the schema.org/Action proposal) (Friday, 14 February)
• RE: Nested structures / ISSUE-26 (was: An updated draft of the schema.org/Action proposal) (Friday, 14 February)
• RE: W3C standardization process (Thursday, 13 February)
• RE: ISSUE-31: Are Operations violating REST's uniform interface constraint? (was: More Thoughts on Links and Operation Subclasses) (Thursday, 13 February)
• RE: Define/change the range of "supportedProperties" (ISSUE-37) (Wednesday, 12 February)
• RE: concerns about hydra:mappings (ISSUE-30) (Wednesday, 12 February)
• RE: terminology/necessity of hydra:required (Tuesday, 11 February)
• RE: Define/change the range of "supportedProperties" (ISSUE-37) (Tuesday, 11 February)
• RE: concerns about hydra:mappings (ISSUE-30) (Tuesday, 11 February)
• RE: StatusCodeDescription vs. Status (ISSUE-32) (Tuesday, 11 February)
• RE: An updated draft of the schema.org/Action proposal (Tuesday, 11 February)
• RE: An updated draft of the schema.org/Action proposal (Monday, 10 February)
• Define/change the range of "supportedProperties" (ISSUE-37) (Monday, 10 February)
• RE: Interoperability with Linked Data Platform (especially regarding collections and paging) ISSUE-36 (Monday, 10 February)
• RE: concerns about hydra:mappings (ISSUE-30) (Monday, 10 February)
• RE: ISSUE-31: Are Operations violating REST's uniform interface constraint? (was: More Thoughts on Links and Operation Subclasses) (Sunday, 9 February)
• StatusCodeDescription vs. Status (ISSUE-32) (Sunday, 9 February)
• RE: terminology/necessity of hydra:required (Sunday, 9 February)
• RE: concerns about hydra:mappings (ISSUE-30) (Sunday, 9 February)
• RE: Reconciling hydra rest semantics for collections with typical RDF entity relationships (Friday, 7 February)
• RE: ISSUE-31: Are Operations violating REST's uniform interface constraint? (was: More Thoughts on Links and Operation Subclasses) (Friday, 7 February)
• RE: Wrap up and Discussion of ways to Specify Supported Properties and corresponding Validation Rules for Operations (Thursday, 6 February)
• RE: ISSUE-31: Are Operations violating REST's uniform interface constraint? (was: More Thoughts on Links and Operation Subclasses) (Thursday, 6 February)
• RE: terminology/necessity of hydra:required (Thursday, 6 February)
• RE: concerns about hydra:mappings (ISSUE-30) (Thursday, 6 February)
• Singularization of properties and its consequences (ISSUE-25, ISSUE-27 & ISSUE-28) (Thursday, 6 February)
• RE: ISSUE-32: Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? (Wednesday, 5 February)
• RE: Reconciling hydra rest semantics for collections with typical RDF entity relationships (Wednesday, 5 February)
• RE: plural properties should become singular (Wednesday, 5 February)
• RE: ISSUE-31: Are Operations violating REST's uniform interface constraint? (was: More Thoughts on Links and Operation Subclasses) (Wednesday, 5 February)
• RE: Wrap up and Discussion of ways to Specify Supported Properties and corresponding Validation Rules for Operations (Wednesday, 5 February)
• RE: Reconciling hydra rest semantics for collections with typical RDF entity relationships (Tuesday, 4 February)
• RE: Reconciling hydra rest semantics for collections with typical RDF entity relationships (Tuesday, 4 February)
• FW: An updated draft of the schema.org/Actions proposal! (Tuesday, 4 February)
• RE: Wrap up and Discussion of ways to Specify Supported Properties and corresponding Validation Rules for Operations (Tuesday, 4 February)
• RE: ISSUE-32: Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? (Tuesday, 4 February)
• RE: More Thoughts on Links and Operation Subclasses (Tuesday, 4 February)
• ISSUE-32: Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? (was: More Thoughts on Links and Operation Subclasses) (Tuesday, 4 February)
• ISSUE-31: Are Operations violating REST's uniform interface constraint? (was: More Thoughts on Links and Operation Subclasses) (Tuesday, 4 February)
• RE: More Thoughts on Links and Operation Subclasses (Tuesday, 4 February)
• RE: More Thoughts on Links and Operation Subclasses (Monday, 3 February)
• RE: More Thoughts on Links and Operation Subclasses (Monday, 3 February)
• RE: More Thoughts on Links and Operation Subclasses (Monday, 3 February)
• RE: terminology/necessity of hydra:required (Monday, 3 February)
• RE: terminology/necessity of hydra:required (Monday, 3 February)
• RE: concerns about hydra:mappings (Monday, 3 February)
• RE: plural properties should become singular (Monday, 3 February)
• Properties and types differing only in their capitalization ISSUE-28 (was: plural properties should become singular) (Monday, 3 February)
• RE: Wrap up and Discussion of ways to Specify Supported Properties and corresponding Validation Rules for Operations (Monday, 3 February)
• Nested structures / ISSUE-26 (was: An updated draft of the schema.org/Action proposal) (Monday, 3 February)
• RE: My opinion about hydra vocabulary (Monday, 3 February)
• RE: An updated draft of the schema.org/Action proposal (Monday, 3 February)

Paul Kuykendall

• RE: Reconciling hydra rest semantics for collections with typical RDF entity relationships (Tuesday, 4 February)
• RE: More Thoughts on Links and Operation Subclasses (Monday, 3 February)

Ruben Verborgh

• Re: Singularization of properties and its consequences (ISSUE-25, ISSUE-27 & ISSUE-28) (Saturday, 22 February)
• Re: Define/change the range of "supportedProperties" (ISSUE-37) (Wednesday, 19 February)
• Re: Define/change the range of "supportedProperties" (ISSUE-37) (Wednesday, 19 February)
• Re: removing hydra:search (Wednesday, 19 February)
• Re: removing hydra:search (Wednesday, 19 February)
• Re: concerns about hydra:mappings (ISSUE-30) (Tuesday, 18 February)
• Re: concerns about hydra:mappings (ISSUE-30) (Monday, 17 February)
• Re: concerns about hydra:mappings (ISSUE-30) (Monday, 17 February)
• Re: Define/change the range of "supportedProperties" (ISSUE-37) (Saturday, 15 February)
• Re: Singularization of properties and its consequences (ISSUE-25, ISSUE-27 & ISSUE-28) (Friday, 14 February)
• Re: removing hydra:search (Friday, 14 February)
• Re: Define/change the range of "supportedProperties" (ISSUE-37) (Friday, 14 February)
• Re: concerns about hydra:mappings (ISSUE-30) (Thursday, 13 February)
• Re: removing hydra:search (Wednesday, 12 February)
• Re: Define/change the range of "supportedProperties" (ISSUE-37) (Tuesday, 11 February)
• Re: concerns about hydra:mappings (ISSUE-30) (Tuesday, 11 February)
• Re: Define/change the range of "supportedProperties" (ISSUE-37) (Tuesday, 11 February)
• Re: concerns about hydra:mappings (ISSUE-30) (Tuesday, 11 February)
• Re: terminology/necessity of hydra:required (Tuesday, 11 February)
• Re: terminology/necessity of hydra:required (Monday, 10 February)
• Re: terminology/necessity of hydra:required (Monday, 10 February)
• Re: StatusCodeDescription vs. Status (ISSUE-32) (Monday, 10 February)
• Re: terminology/necessity of hydra:required (Monday, 10 February)
• Re: concerns about hydra:mappings (ISSUE-30) (Monday, 10 February)
• Re: terminology/necessity of hydra:required (Thursday, 6 February)
• Re: concerns about hydra:mappings (ISSUE-30) (Thursday, 6 February)
• Re: ISSUE-32: Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? (Thursday, 6 February)
• Re: Properties and types differing only in their capitalization ISSUE-28 (was: plural properties should become singular) (Thursday, 6 February)
• Re: terminology/necessity of hydra:required (Wednesday, 5 February)
• Re: concerns about hydra:mappings (Wednesday, 5 February)
• Re: Properties and types differing only in their capitalization ISSUE-28 (was: plural properties should become singular) (Wednesday, 5 February)
• Re: plural properties should become singular (Wednesday, 5 February)

Ryan J. McDonough

• Re: ISSUE-31: Are Operations violating REST's uniform interface constraint? (Tuesday, 18 February)
• Re: ISSUE-31: Are Operations violating REST's uniform interface constraint? (Monday, 17 February)
• Re: ISSUE-31: Are Operations violating REST's uniform interface constraint? (Sunday, 16 February)
• Re: ISSUE-31: Are Operations violating REST's uniform interface constraint? (Saturday, 15 February)
• Re: ISSUE-31: Are Operations violating REST's uniform interface constraint? (was: More Thoughts on Links and Operation Subclasses) (Saturday, 15 February)
• Re: ISSUE-31: Are Operations violating REST's uniform interface constraint? (was: More Thoughts on Links and Operation Subclasses) (Friday, 7 February)
• Re: ISSUE-32: Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? (Wednesday, 5 February)
• Re: ISSUE-32: Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? (was: More Thoughts on Links and Operation Subclasses) (Wednesday, 5 February)
• Re: ISSUE-31: Are Operations violating REST's uniform interface constraint? (was: More Thoughts on Links and Operation Subclasses) (Wednesday, 5 February)
• Re: More Thoughts on Links and Operation Subclasses (Tuesday, 4 February)
• Re: More Thoughts on Links and Operation Subclasses (Tuesday, 4 February)
• Re: terminology/necessity of hydra:required (Saturday, 1 February)

Sam Goto

• Re: ActionHandlers vs "App resources" (was: An updated draft of the schema.org/Action proposal) (Wednesday, 26 February)
• Re: ActionHandlers vs "App resources" (was: An updated draft of the schema.org/Action proposal) (Friday, 21 February)
• Re: Nested structures / ISSUE-26 (Friday, 14 February)
• Re: ActionHandlers vs "App resources" (was: An updated draft of the schema.org/Action proposal) (Friday, 14 February)
• ActionHandlers vs "App resources" (was: An updated draft of the schema.org/Action proposal) (Friday, 14 February)
• Re: Nested structures / ISSUE-26 (was: An updated draft of the schema.org/Action proposal) (Friday, 14 February)
• Re: An updated draft of the schema.org/Action proposal (Monday, 10 February)

Savas Parastatidis

• Re: ActionHandlers vs "App resources" (was: An updated draft of the schema.org/Action proposal) (Thursday, 27 February)

Thomas Hoppe

• Re: Define/change the range of "supportedProperties" (ISSUE-37) (Thursday, 20 February)
• Re: removing hydra:search (Thursday, 20 February)
• Re: Define/change the range of "supportedProperties" (ISSUE-37) (Tuesday, 18 February)
• Re: removing hydra:search (Tuesday, 18 February)
• Re: removing hydra:search (Tuesday, 18 February)
• Re: ISSUE-31: Are Operations violating REST's uniform interface constraint? (Sunday, 16 February)
• Re: Define/change the range of "supportedProperties" (ISSUE-37) (Saturday, 15 February)
• Re: StatusCodeDescription vs. Status (ISSUE-32) (Saturday, 15 February)
• Re: ISSUE-31: Are Operations violating REST's uniform interface constraint? (Saturday, 15 February)
• Re: removing hydra:search (Friday, 14 February)
• Re: Define/change the range of "supportedProperties" (ISSUE-37) (Friday, 14 February)
• Re: concerns about hydra:mappings (ISSUE-30) (Wednesday, 12 February)
• Re: StatusCodeDescription vs. Status (ISSUE-32) (Tuesday, 11 February)
• Re: terminology/necessity of hydra:required (Monday, 10 February)
• Re: terminology/necessity of hydra:required (Monday, 10 February)
• Re: Singularization of properties and its consequences (ISSUE-25, ISSUE-27 & ISSUE-28) (Thursday, 6 February)
• Re: Wrap up and Discussion of ways to Specify Supported Properties and corresponding Validation Rules for Operations (Thursday, 6 February)
• Re: ISSUE-32: Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? (Thursday, 6 February)
• Re: ISSUE-32: Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? (Thursday, 6 February)
• Re: Wrap up and Discussion of ways to Specify Supported Properties and corresponding Validation Rules for Operations (Thursday, 6 February)
• Re: ISSUE-32: Should hydra:returns and hydra:statusCodes be removed to avoid tight coupling? (Wednesday, 5 February)
• Re: Wrap up and Discussion of ways to Specify Supported Properties and corresponding Validation Rules for Operations (Tuesday, 4 February)
• Re: Wrap up and Discussion of ways to Specify Supported Properties and corresponding Validation Rules for Operations (Monday, 3 February)

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