Re: Pagination (ISSUE-42)

Andrew,

Range is a specific case. There was a discussion here about making the allowedValues thing extensible so that you could express implicit ranges etc. On the other hand you could simply enumerate the values ad fallback.

Regarding 'induvidual', I do not agree with you. I see where you are coming from though. The term does in fact come from OWL, but is it really so confusing? We are not talking about law or any other context. Hydra is about hypetmedia and REST. In this context individual (Resource) seems quite appropriate to me. What term would you propose as an alternative?

Regards,
Tom

-----Original Message-----
From: Andrew Hacking <ahacking@gmail.com>
To: Tomasz Pluskiewicz <tomasz@t-code.pl>
Cc: "public-hydra@w3.org" <public-hydra@w3.org>
Sent: Sun, 15 Feb 2015 15:11
Subject: Re: Pagination (ISSUE-42)

Tomasz,

Thanks for the link to issue 82.  I don't think that is going to cut it
since its just about providing an explicit list of labelled
values/"individuals" [sic] and we need a range of values to be expressed.

btw I also dislike the term "individual" in the proposal to refer to
something that is not a string or number, a truly WTF? moment. The term
"individual" used in most other contexts, including law, is used to refer
to a flesh and blood person. This is an example of the alien strangeness
that Hydra and JSON-LD faces with the pragmatic developer community who
need to build working systems yesterday.

On Sun, Feb 15, 2015 at 10:51 PM, Tomasz Pluskiewicz <tomasz@t-code.pl>
wrote:

> On 2015-02-15 13:39, Andrew Hacking wrote:
>
>> Can templates be parameterized using ranged values? That would be my
>> preferred approach, that params have their range defined based on the
>> count of members in the collection matching the query.
>>
>
> Not ATM but issue 82 [1] discusses solution to a similar problem with
> values allowed for supportedProperty. I think in general a solution to that
> issue also covers template parameters.
>
> Regards,
> Tom
>
> [1]: https://github.com/HydraCG/Specifications/issues/82
>
>
>

Received on Sunday, 15 February 2015 14:20:15 UTC