Resolve ISSUE-27 by
Live stream from the hypermedia panel discussion at API Craft on Monday 28th (tomorrow)
Moving forward with ISSUE-30 (IRI template expansion)
- RE: Moving forward with ISSUE-30 (IRI template expansion)
- Re: Moving forward with ISSUE-30 (IRI template expansion)
Resolve ISSUE-14 by renaming readonly/writeonly to readable/writeable
Resolve ISSUE-39 by documenting how "errors" can be given an identifier and be reused
Resolved ISSUE-5 and ISSUE-11: Do not introduce RetrieveResourceOperation and remove other Operation types
Introduction and a question about JSON-LD
- RE: Introduction and a question about JSON-LD
- Re: Introduction and a question about JSON-LD
- Re: Introduction and a question about JSON-LD
- Re: Introduction and a question about JSON-LD
Suggestion on URLs for triple pattern fragments
- RE: Suggestion on URLs for triple pattern fragments
- Re: Suggestion on URLs for triple pattern fragments
Introducing myself
Comments on the Triple Patterns Fragments draft
- Re: Comments on the Triple Patterns Fragments draft
- Re: Comments on the Triple Patterns Fragments draft
- Re: Comments on the Triple Patterns Fragments draft
- Re: Comments on the Triple Patterns Fragments draft
- RE: Comments on the Triple Patterns Fragments draft
- Re: Comments on the Triple Patterns Fragments draft
- RE: Comments on the Triple Patterns Fragments draft
- Re: Comments on the Triple Patterns Fragments draft
- Re: Comments on the Triple Patterns Fragments draft
- RE: Comments on the Triple Patterns Fragments draft
- Re: Comments on the Triple Patterns Fragments draft
- 404 Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- RE: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- Proposed resolution for ISSUE-64 (status codes)
- Re: Proposed resolution for ISSUE-64 (status codes)
- RE: Proposed resolution for ISSUE-64 (status codes)
- Re: Proposed resolution for ISSUE-64 (status codes)
- Re: Comments on the Triple Patterns Fragments draft
- RE: Comments on the Triple Patterns Fragments draft
- RE: Proposed resolution for ISSUE-64 (status codes)
- Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- Re: 404 Re: Comments on the Triple Patterns Fragments draft
- RE: 404 Re: Comments on the Triple Patterns Fragments draft
Hydra generic servers
Reconsidering template mappings
Call for consensus on defining IRI template expansion (ISSUE-30)
- Re: Call for consensus on defining IRI template expansion (ISSUE-30)
- Re: Call for consensus on defining IRI template expansion (ISSUE-30)
- RE: Call for consensus on defining IRI template expansion (ISSUE-30)
Call for consensus on renaming readonly/writeonly to readable/writeable (ISSUE-14)
- Re: Call for consensus on renaming readonly/writeonly to readable/writeable (ISSUE-14)
- Re: Call for consensus on renaming readonly/writeonly to readable/writeable (ISSUE-14)
- Re: Call for consensus on renaming readonly/writeonly to readable/writeable (ISSUE-14)
Call for consensus on documenting how "errors" can be given an identifier and be reused (ISSUE-39)
- Re: Call for consensus on documenting how "errors" can be given an identifier and be reused (ISSUE-39)
Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- RE: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- RE: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- RE: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- RE: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- RE: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- RE: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
- Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)
Call for consensus: Do not introduce RetrieveResourceOperation (ISSUE-5) and remove other Operation types (ISSUE-11)
- Re: Call for consensus: Do not introduce RetrieveResourceOperation (ISSUE-5) and remove other Operation types (ISSUE-11)
- Re: Call for consensus: Do not introduce RetrieveResourceOperation (ISSUE-5) and remove other Operation types (ISSUE-11)
- Re: Call for consensus: Do not introduce RetrieveResourceOperation (ISSUE-5) and remove other Operation types (ISSUE-11)
- Re: Call for consensus: Do not introduce RetrieveResourceOperation (ISSUE-5) and remove other Operation types (ISSUE-11)
Semantic Domination
Is the term ApiDocumentation misleading (ISSUE-61) / was: RE: Specifying operations for instances
- Re: Is the term ApiDocumentation misleading (ISSUE-61) / was: RE: Specifying operations for instances
- Re: Is the term ApiDocumentation misleading (ISSUE-61) / was: RE: Specifying operations for instances
- Re: Is the term ApiDocumentation misleading (ISSUE-61) / was: RE: Specifying operations for instances
ISSUE-41 resolved
Discovering Hydra API by dereferencing
RE: Please help with JSON-LD processing
Express "go to specific page" for a collection
- RE: Express "go to specific page" for a collection
- RE: Express "go to specific page" for a collection
Express "go to specific page" for a collection
Questions
Re: Specifying operations for instances
RE: Specifying operations for instances
- RE: Specifying operations for instances
Call for consensus on collection design (ISSUE-41)
- Re: Call for consensus on collection design (ISSUE-41)
- RE: Call for consensus on collection design (ISSUE-41)