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

Since there have been no objections, I'm marking ISSUE-30 [1] as

RESOLVED: Introduce a new property hydra:variableRepresentation that can be
used on a hydra:IriTemplate to define how a client replaces variables in the
IRI template with values. For the time being, Hydra will support two
representations: hydra:BasicRepresentation and hydra:ExplicitRepresentation.
The former, hydra:BasicRepresentation, serializes just the lexical form, but
omits language and type information. hydra:ExplicitRepresentation on the
other hand includes language and type information.

Furthermore, ISSUE-17 [2] will be marked as

RESOLVED: Introduce a new datatype hydra:rfc6570Template. This datatype can
be used to explicitly specify the syntax of the hydra:template. For the time
being,
RFC6570 [3] is the only supported IRI template syntax. The range of
hydra:template won't be changed to hydra:rfc6570Template but the Hydra
JSON-LD context will be updated to type-coerce the property "template"
automatically. If a client encounters a template with a datatype of
xsd:string, it should be interpreted as RFC6570 template.


The issues will be closed when the changes have been implemented in the
specification.

Thanks to everyone that participated in the discussions that lead to this
design.


[1] https://github.com/HydraCG/Specifications/issues/30
[2] https://github.com/HydraCG/Specifications/issues/17
[3] https://tools.ietf.org/html/rfc6570


--
Markus Lanthaler
@markuslanthaler

Received on Monday, 27 October 2014 12:09:10 UTC