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

AW: Finalizing the IriTemplate design - serialization (ISSUE-30 & ISSUE-17)

AW: Re: Getting around in Event API Demo

blank nodes

blank nodes [was: DBpedia now available as triple pattern fragments]

Call for consensus on IriTemplate design (ISSUE-30 & ISSUE-17)

Comments on the Triple Patterns Fragments draft

DBpedia now available as triple pattern fragments

Editing resources

Enquiry

Finalizing the IriTemplate design - serialization (ISSUE-30 & ISSUE-17)

Finalizing the IriTemplate design - serialization name (ISSUE-30 & ISSUE-17)

Finalizing the IriTemplate design - serialization name, no datatype/language (ISSUE-30 & ISSUE-17)

Finalizing the IriTemplate design - variable serialization property (ISSUE-30 & ISSUE-17)

First release of hydra-java for spring-hateoas in Maven central

Fwd: Re: using object keys in JSON-LD

Fwd: Step by step resource editing

Fwd: Using Hydra for Data Model Genration and Validation

Getting around in Event API Demo

How to correctly specify JSON-LD flavor in Accept and Content-Type headers?

hydra and void

hydra:Collection and hydra:PagedCollection URIs

In-place hydra:Link

Interpretation of POST operation given large relationship collections

IriTemplate design finalized - ISSUE-30 & ISSUE-17 resolved

Link, operation keywords

Pre-release of my partial TPF implementation

relate a Collection and a PagedCollection

Schema.org properties having a collection as value and hydra:Collection

some more feedback

totalItems vs void:triples

Using Hydra for Data Model Genration and Validation

Using hydra:Link

using object keys in JSON-LD

VoID Requirement

W3C standardization process

Last message date: Friday, 31 October 2014 16:16:21 UTC