W3C home > Mailing lists > Public > public-hydra@w3.org > July 2014

Re: Call for consensus on renaming "statusCodes" to "possibleStatus" and "StatusCodeDescription" to "Status" (ISSUE-27)

From: Thomas Hoppe <thomas.hoppe@n-fuse.de>
Date: Sat, 26 Jul 2014 04:41:46 -0400
Message-ID: <53D369CA.8040706@n-fuse.de>
To: public-hydra@w3.org
Yea, potentialStatus is synonym to possibleStatus to me,
as both express the existence of a status but also hint
that they are not limited to the ones enumerated.
So I'm also fine with that.

On 07/25/2014 09:50 PM, Markus Lanthaler wrote:
> Hi all,
>
> I would like to get some more opinions about this naming decision here
> before I mark the issue as resolved. We have two candidates "possibleStatus"
> and "potentialStatus". Thomas said:
>
> On 22 Jul 2014 at 00:11, Thomas Hoppe wrote:
>> I vote for possibleStatus or just status as we
>> could just describe in prose that the property conveys
>> the meaning of a potential Status.
> I personally would prefer potentialStatus as I think it is less definitive
> (other statuses are possible as well). Thomas, why do you prefer
> possibleStatus?
>
>
> --
> Markus Lanthaler
> @markuslanthaler
>
>
>
>
Received on Saturday, 26 July 2014 08:42:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:29:42 UTC