Re: Singularization of properties and its consequences (ISSUE-25, ISSUE-27 & ISSUE-28) from Ruben Verborgh on 2014-02-14 (public-hydra@w3.org from February 2014)

From: Ruben Verborgh <ruben.verborgh@ugent.be>
Date: Fri, 14 Feb 2014 10:41:35 +0000
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Cc: public-hydra@w3.org
Message-Id: <08CF1DCC-6602-4CA6-9C23-6AC8A12B85AC@ugent.be>

> Thanks a lot for taking a stab at this Ruben. Much appreciated. It LGTM but
> as you say
> 
>> [...] the statusCodes issue needs fixing before it can be
>> singularized:
>> https://github.com/HydraCG/Specifications/issues/27

Is there any way we can move on issue 25 (pull request 34)?
The singularization is OK except for hydra:statusCodes,
which is a separate issue anyway (27).

The faster we do this, the less chance that the old pluralized properties
are actually being used in designs.
What happens to hydra:statusCodes is a different story anyway.

Best,

Ruben

Received on Friday, 14 February 2014 10:42:08 UTC