- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Wed, 10 Sep 2014 19:33:36 +0200
- To: Erik Wilde <dret@berkeley.edu>
- Cc: László Lajos Jánszky <laszlo.janszky@gmail.com>, public-hydra@w3.org
Hi Erik,
> what link descriptions also are supposed to do is to describe data types
Hydra does that too; by re-using existing properties and Linked Data practices.
The idea is that http://example.com/feedpaging/page would deference to the following information:
<http://example.com/feedpaging/page> rdfs:range xsd:positiveInteger.
Thereby, http://example.com/feedpaging/page is a positive integer, everywhere.
> and value ranges.
That's not supported at the moment.
> {
> "@context": "http://www.w3.org/ns/hydra/context.jsonld",
> "@type": "IriTemplate",
> "template": "http://api.example.com/issues{?page}",
> "mapping": [
> {
> "@type": "IriTemplateMapping",
> "variable": "page",
> "datatype": "http://www.w3.org/TR/xmlschema-2/#integer",
So this would already be present in the definition of http://example.com/feedpaging/page.
> "xs:minInclusive": "1",
> "xs:maxInclusive": "42",
Something like this might maybe be part of Hydra if there is demand for it. Opinions?
Best,
Ruben
Received on Wednesday, 10 September 2014 17:34:12 UTC