public-hydra@w3.org from July 2014 by date

Thursday, 31 July 2014

• Re: Proposed resolution for ISSUE-64 (status codes) Gregg Kellogg
• Re: 404 Re: Comments on the Triple Patterns Fragments draft Kjetil Kjernsmo
• Re: 404 Re: Comments on the Triple Patterns Fragments draft Ruben Verborgh
• Re: 404 Re: Comments on the Triple Patterns Fragments draft David Booth
• Re: 404 Re: Comments on the Triple Patterns Fragments draft David Booth
• RE: Proposed resolution for ISSUE-64 (status codes) Markus Lanthaler
• Re: Moving forward with ISSUE-30 (IRI template expansion) Gregg Kellogg
• RE: 404 Re: Comments on the Triple Patterns Fragments draft Markus Lanthaler
• RE: Proposed resolution for ISSUE-64 (status codes) Markus Lanthaler
• RE: Moving forward with ISSUE-30 (IRI template expansion) Markus Lanthaler
• RE: Introduction and a question about JSON-LD Markus Lanthaler
• Re: Moving forward with ISSUE-30 (IRI template expansion) Ruben Verborgh
• RE: Moving forward with ISSUE-30 (IRI template expansion) Markus Lanthaler
• RE: Introduction and a question about JSON-LD Dimitri van Hees
• Re: 404 Re: Comments on the Triple Patterns Fragments draft Kjetil Kjernsmo

Wednesday, 30 July 2014

• Re: Proposed resolution for ISSUE-64 (status codes) Gregg Kellogg
• Re: 404 Re: Comments on the Triple Patterns Fragments draft Ruben Verborgh
• Re: 404 Re: Comments on the Triple Patterns Fragments draft Andreas Kuckartz
• Re: 404 Re: Comments on the Triple Patterns Fragments draft Olaf Hartig
• Proposed resolution for ISSUE-64 (status codes) Ruben Verborgh
• Re: 404 Re: Comments on the Triple Patterns Fragments draft Ruben Verborgh
• Re: 404 Re: Comments on the Triple Patterns Fragments draft Erik Wilde
• Re: 404 Re: Comments on the Triple Patterns Fragments draft Ruben Verborgh
• Re: 404 Re: Comments on the Triple Patterns Fragments draft Erik Wilde
• Re: 404 Re: Comments on the Triple Patterns Fragments draft Ruben Verborgh
• Re: 404 Re: Comments on the Triple Patterns Fragments draft Nandana Mihindukulasooriya
• Re: 404 Re: Comments on the Triple Patterns Fragments draft Andreas Kuckartz
• Re: 404 Re: Comments on the Triple Patterns Fragments draft Ruben Verborgh
• 404 Re: Comments on the Triple Patterns Fragments draft Andreas Kuckartz
• Re: Comments on the Triple Patterns Fragments draft Ruben Verborgh
• RE: Comments on the Triple Patterns Fragments draft Markus Lanthaler
• Resolve ISSUE-27 by Markus Lanthaler

Monday, 28 July 2014

• RE: Introduction and a question about JSON-LD Markus Lanthaler
• Re: Introduction and a question about JSON-LD Dimitri van Hees

Sunday, 27 July 2014

• Live stream from the hypermedia panel discussion at API Craft on Monday 28th (tomorrow) Markus Lanthaler
• RE: Introduction and a question about JSON-LD Markus Lanthaler
• RE: Introduction and a question about JSON-LD Markus Lanthaler
• Re: Introduction and a question about JSON-LD john.walker
• RE: Introduction and a question about JSON-LD john.walker
• Re: Introduction and a question about JSON-LD Dimitri van Hees
• Re: Introduction and a question about JSON-LD Dimitri van Hees
• RE: Introduction and a question about JSON-LD Markus Lanthaler

Saturday, 26 July 2014

• Re: Suggestion on URLs for triple pattern fragments Ruben Verborgh
• Re: Call for consensus on defining IRI template expansion (ISSUE-30) Ruben Verborgh
• Re: Suggestion on URLs for triple pattern fragments Gregg Kellogg
• RE: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27) McBennett, Pat
• Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27) Thomas Hoppe
• Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27) Ruben Verborgh
• Re: Moving forward with ISSUE-30 (IRI template expansion) Ruben Verborgh
• Re: Suggestion on URLs for triple pattern fragments Ruben Verborgh
• RE: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27) McBennett, Pat
• Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27) Thomas Hoppe
• RE: Moving forward with ISSUE-30 (IRI template expansion) McBennett, Pat
• RE: Introduction and a question about JSON-LD john.walker
• RE: Introduction and a question about JSON-LD Markus Lanthaler
• RE: Suggestion on URLs for triple pattern fragments Markus Lanthaler
• Moving forward with ISSUE-30 (IRI template expansion) Markus Lanthaler
• RE: Call for consensus on defining IRI template expansion (ISSUE-30) Markus Lanthaler
• Resolve ISSUE-14 by renaming readonly/writeonly to readable/writeable Markus Lanthaler
• Resolve ISSUE-39 by documenting how "errors" can be given an identifier and be reused Markus Lanthaler
• RE: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27) Markus Lanthaler
• Resolved ISSUE-5 and ISSUE-11: Do not introduce RetrieveResourceOperation and remove other Operation types Markus Lanthaler

Friday, 25 July 2014

• RE: Introduction and a question about JSON-LD john.walker
• RE: Introduction and a question about JSON-LD Markus Lanthaler

Thursday, 24 July 2014

• Introduction and a question about JSON-LD Dimitri van Hees

Friday, 25 July 2014

• Suggestion on URLs for triple pattern fragments john.walker

Thursday, 24 July 2014

• Re: Call for consensus on defining IRI template expansion (ISSUE-30) Ryan Riley
• Re: Call for consensus on defining IRI template expansion (ISSUE-30) Ryan Riley
• Re: Comments on the Triple Patterns Fragments draft Ruben Verborgh
• Re: Comments on the Triple Patterns Fragments draft Ruben Verborgh
• Re: Call for consensus on defining IRI template expansion (ISSUE-30) Ruben Verborgh

Wednesday, 23 July 2014

• Re: Comments on the Triple Patterns Fragments draft Erik Wilde
• RE: Comments on the Triple Patterns Fragments draft Markus Lanthaler
• RE: Call for consensus on defining IRI template expansion (ISSUE-30) Markus Lanthaler
• RE: Call for consensus on defining IRI template expansion (ISSUE-30) Markus Lanthaler
• Re: Comments on the Triple Patterns Fragments draft Erik Wilde
• RE: Introducing myself Markus Lanthaler
• RE: Comments on the Triple Patterns Fragments draft Markus Lanthaler

Tuesday, 22 July 2014

• Re: Comments on the Triple Patterns Fragments draft Ruben Verborgh

Monday, 21 July 2014

• Introducing myself Siddhartha Ravindra Thota

Tuesday, 22 July 2014

• Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27) Thomas Hoppe

Monday, 21 July 2014

• Re: Comments on the Triple Patterns Fragments draft Kjetil Kjernsmo
• Re: Call for consensus on defining IRI template expansion (ISSUE-30) Ruben Verborgh
• Re: Call for consensus on defining IRI template expansion (ISSUE-30) Ruben Verborgh
• RE: Call for consensus on defining IRI template expansion (ISSUE-30) Markus Lanthaler
• RE: Call for consensus on defining IRI template expansion (ISSUE-30) Markus Lanthaler
• RE: Call for consensus on defining IRI template expansion (ISSUE-30) Markus Lanthaler
• RE: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27) Markus Lanthaler
• RE: Call for consensus on renaming readonly/writeonly to readable/writeable (ISSUE-14) Markus Lanthaler
• RE: Call for consensus on documenting how "errors" can be given an identifier and be reused (ISSUE-39) Markus Lanthaler
• RE: Reconsidering template mappings Markus Lanthaler
• RE: Hydra generic servers Markus Lanthaler
• Re: Comments on the Triple Patterns Fragments draft Ruben Verborgh
• Re: Comments on the Triple Patterns Fragments draft Olaf Hartig
• Re: Comments on the Triple Patterns Fragments draft Ruben Verborgh

Sunday, 20 July 2014

• Comments on the Triple Patterns Fragments draft Kjetil Kjernsmo
• Hydra generic servers Andreas Kuckartz

Saturday, 19 July 2014

• Re: Call for consensus on renaming readonly/writeonly to readable/writeable (ISSUE-14) ☮ elf Pavlik ☮
• Re: Call for consensus: Do not introduce RetrieveResourceOperation (ISSUE-5) and remove other Operation types (ISSUE-11) ☮ elf Pavlik ☮

Friday, 18 July 2014

• Re: Call for consensus: Do not introduce RetrieveResourceOperation (ISSUE-5) and remove other Operation types (ISSUE-11) Chris Chapman

Thursday, 17 July 2014

• Re: Call for consensus on defining IRI template expansion (ISSUE-30) Ruben Verborgh
• Re: Reconsidering template mappings Tomasz Pluskiewicz
• Re: Call for consensus on defining IRI template expansion (ISSUE-30) Tomasz Pluskiewicz
• Re: Reconsidering template mappings Ruben Verborgh
• Re: Call for consensus on defining IRI template expansion (ISSUE-30) Ruben Verborgh
• Re: Call for consensus on defining IRI template expansion (ISSUE-30) Tomasz Pluskiewicz
• Re: Call for consensus on defining IRI template expansion (ISSUE-30) Ruben Verborgh
• Re: Call for consensus on renaming readonly/writeonly to readable/writeable (ISSUE-14) Ruben Verborgh
• Re: Call for consensus on documenting how "errors" can be given an identifier and be reused (ISSUE-39) Ruben Verborgh
• Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27) Ruben Verborgh
• Re: Call for consensus: Do not introduce RetrieveResourceOperation (ISSUE-5) and remove other Operation types (ISSUE-11) Ruben Verborgh

Wednesday, 16 July 2014

• Re: Call for consensus on renaming readonly/writeonly to readable/writeable (ISSUE-14) Chris Chapman
• Reconsidering template mappings Tomasz Pluskiewicz
• Re: Call for consensus on defining IRI template expansion (ISSUE-30) Tomasz Pluskiewicz
• Re: Call for consensus on documenting how "errors" can be given an identifier and be reused (ISSUE-39) Tomasz Pluskiewicz
• Re: Call for consensus on renaming readonly/writeonly to readable/writeable (ISSUE-14) Tomasz Pluskiewicz
• Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27) Tomasz Pluskiewicz
• Re: Call for consensus: Do not introduce RetrieveResourceOperation (ISSUE-5) and remove other Operation types (ISSUE-11) Tomasz Pluskiewicz
• Re: Call for consensus on defining IRI template expansion (ISSUE-30) Gregg Kellogg
• Re: Call for consensus on renaming readonly/writeonly to readable/writeable (ISSUE-14) Gregg Kellogg
• Re: Call for consensus on documenting how "errors" can be given an identifier and be reused (ISSUE-39) Gregg Kellogg
• Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27) Gregg Kellogg
• Re: Call for consensus: Do not introduce RetrieveResourceOperation (ISSUE-5) and remove other Operation types (ISSUE-11) Gregg Kellogg
• Call for consensus on defining IRI template expansion (ISSUE-30) Markus Lanthaler
• Call for consensus on renaming readonly/writeonly to readable/writeable (ISSUE-14) Markus Lanthaler
• Call for consensus on documenting how "errors" can be given an identifier and be reused (ISSUE-39) Markus Lanthaler
• Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27) Markus Lanthaler
• Re: Call for consensus: Do not introduce RetrieveResourceOperation (ISSUE-5) and remove other Operation types (ISSUE-11) Thomas Hoppe
• Call for consensus: Do not introduce RetrieveResourceOperation (ISSUE-5) and remove other Operation types (ISSUE-11) Markus Lanthaler
• RE: Is the term ApiDocumentation misleading (ISSUE-61) / was: RE: Specifying operations for instances Markus Lanthaler
• Re: Semantic Domination Melvin Carvalho
• RE: ISSUE-41 resolved Markus Lanthaler
• RE: Semantic Domination Markus Lanthaler

Friday, 11 July 2014

• Re: Is the term ApiDocumentation misleading (ISSUE-61) / was: RE: Specifying operations for instances Andreas Kuckartz
• Re: Is the term ApiDocumentation misleading (ISSUE-61) / was: RE: Specifying operations for instances Alexandr Krylovskiy
• Re: ISSUE-41 resolved ☮ elf Pavlik ☮
• Re: Semantic Domination ☮ elf Pavlik ☮
• RE: Semantic Domination Markus Lanthaler
• RE: Express "go to specific page" for a collection Markus Lanthaler
• Semantic Domination Lee Curtis
• Re: Express "go to specific page" for a collection Philipp Zins

Thursday, 10 July 2014

• RE: Express "go to specific page" for a collection Markus Lanthaler
• Re: Is the term ApiDocumentation misleading (ISSUE-61) / was: RE: Specifying operations for instances Chris Chapman
• Re: Express "go to specific page" for a collection Tomasz Pluskiewicz
• RE: Express "go to specific page" for a collection Markus Lanthaler
• Re: Is the term ApiDocumentation misleading (ISSUE-61) / was: RE: Specifying operations for instances Andreas Kuckartz
• RE: Discovering Hydra API by dereferencing Markus Lanthaler
• Re: Express "go to specific page" for a collection Philipp Zins
• RE: Please help with JSON-LD processing Markus Lanthaler
• Is the term ApiDocumentation misleading (ISSUE-61) / was: RE: Specifying operations for instances Markus Lanthaler
• ISSUE-41 resolved Markus Lanthaler
• Re: Specifying operations for instances Alexandr Krylovskiy
• Re: Express "go to specific page" for a collection Tomasz Pluskiewicz
• Re: Express "go to specific page" for a collection Philipp Zins

Wednesday, 9 July 2014

• Discovering Hydra API by dereferencing Tomasz Pluskiewicz
• Re: Please help with JSON-LD processing Tomasz Pluskiewicz
• Re: Specifying operations for instances Chris Chapman
• RE: Specifying operations for instances Markus Lanthaler
• RE: Specifying operations for instances McBennett, Pat
• RE: Specifying operations for instances Markus Lanthaler
• RE: Please help with JSON-LD processing Markus Lanthaler
• Re: Please help with JSON-LD processing Tomasz Pluskiewicz

Tuesday, 8 July 2014

• RE: Please help with JSON-LD processing Markus Lanthaler
• Re: Specifying operations for instances Tomasz Pluskiewicz
• RE: Express "go to specific page" for a collection Markus Lanthaler
• RE: Specifying operations for instances McBennett, Pat
• RE: Express "go to specific page" for a collection Philipp Zins

Monday, 7 July 2014

• RE: Express "go to specific page" for a collection Markus Lanthaler
• RE: Specifying operations for instances Markus Lanthaler
• RE: Questions Markus Lanthaler
• RE: Specifying operations for instances McBennett, Pat
• RE: Call for consensus on collection design (ISSUE-41) Markus Lanthaler
• RE: Specifying operations for instances Markus Lanthaler
• RE: Specifying operations for instances Markus Lanthaler
• Express "go to specific page" for a collection Philipp Zins
• Re: Express "go to specific page" for a collection Jindřich Mynarz
• Express "go to specific page" for a collection Philipp Zins

Friday, 4 July 2014

• Questions Bieg Mauro
• Re: Call for consensus on collection design (ISSUE-41) Ruben Verborgh
• Re: Specifying operations for instances Tomasz Pluskiewicz

Thursday, 3 July 2014

• RE: Call for consensus on collection design (ISSUE-41) McBennett, Pat
• RE: Call for consensus on collection design (ISSUE-41) McBennett, Pat
• RE: Specifying operations for instances McBennett, Pat
• RE: Call for consensus on collection design (ISSUE-41) Markus Lanthaler
• RE: Call for consensus on collection design (ISSUE-41) Markus Lanthaler
• RE: Call for consensus on collection design (ISSUE-41) Markus Lanthaler
• RE: Call for consensus on collection design (ISSUE-41) Markus Lanthaler
• Re: Call for consensus on collection design (ISSUE-41) Gregg Kellogg
• Re: Call for consensus on collection design (ISSUE-41) Ruben Verborgh
• Re: Call for consensus on collection design (ISSUE-41) Andreas Kuckartz
• RE: Call for consensus on collection design (ISSUE-41) McBennett, Pat
• Re: Call for consensus on collection design (ISSUE-41) Ruben Verborgh
• Re: Call for consensus on collection design (ISSUE-41) Ruben Verborgh
• Re: Call for consensus on collection design (ISSUE-41) Andreas Kuckartz
• RE: Call for consensus on collection design (ISSUE-41) McBennett, Pat
• Re: Call for consensus on collection design (ISSUE-41) Ruben Verborgh
• Call for consensus on collection design (ISSUE-41) Markus Lanthaler
• The path to standardization at W3C Markus Lanthaler

Wednesday, 2 July 2014

• Re: ISSUE-56: Date ranges / intervals for LDF Ruben Verborgh
• Re: ISSUE-56: Date ranges / intervals for LDF Andreas Kuckartz
• RE: ISSUE-56: Date ranges / intervals for LDF Markus Lanthaler
• [CfP] 6 ways for SemWeb developers to participate Ruben Verborgh
• Re: ISSUE-56: Date ranges / intervals for LDF Andreas Kuckartz
• Re: ISSUE-56: Date ranges / intervals for LDF Ruben Verborgh
• Re: ISSUE-56: Date ranges / intervals for LDF Ruben Verborgh

Tuesday, 1 July 2014

• RE: Representation of an empty indexed collection Markus Lanthaler
• Representation of an empty indexed collection Vagif Abilov

Last message date: Thursday, 31 July 2014 22:58:00 UTC