Wikidata:Property proposal/Estado actual

software life cycle state

Originally proposed at Wikidata:Property proposal/Term

Not done

Description	Describes the status of a software/website/product/etc.
Represents	state (Q3505845)
Data type	Item
Template parameter	"estado actual" on w:es:Plantilla:Ficha de sitio web
Allowed values	If possible, elements that are a instance of software version type (Q28530564)
Example	OpenStreetMap (Q936) → active (Q29415466)
Planned use	Set the property on all items that are a instance of software, website, software standard, etc.
Robot and gadget jobs	Sí

Motivation

This property is useful in many Wikipedia articles. Giovanni Alfredo Garciliano Diaz (talk) 21:32, 15 April 2017 (UTC)[reply]

Discussion

Comment "current" would be something true at the time a statement was entered, but it may not be correct later. If we have thousands of items in wikidata with "current status" entries of "active", say, how do we know they are actually still "active"? Perhaps instead just a generic "status" property would be helpful, with a rule to generally use a point in time (P585) qualifier. We do have a number of properties that could be considered subproperties of a generic "status" - canonization status (P411) for example so I think it would be useful to have. ArthurPSmith (talk) 18:33, 17 April 2017 (UTC)[reply]

@ArthurPSmith: I'm according you, a statement with a point in time (P585) will be useful, after all, this property is only a generic property... Also, the possible values can be, for example: active (Q29415466), "inactive", "discontinued", "on development", etc. Giovanni Alfredo Garciliano Diaz (talk) 01:18, 26 April 2017 (UTC)[reply]

As soon as we have calculated values, properties that describe 'current' situations, could be transferred to calculations based on date values. --Hannolans (talk) 10:30, 28 April 2017 (UTC)[reply]

I would propose to have a more defined name, as now, it could also be the status of a building, the copyright status etc. --Hannolans (talk) 10:32, 28 April 2017 (UTC)[reply]

@Hannolans: Then we would need many properties for each type of item, e.g., for software items, we would need a "development state" property, and as possible values, active (Q29415466), "inactive", "discontinued", "on development", etc.; for website items, we would need a "development state", with its possible values, "online", "offline", etc.; and for a standard, we would need a standard state, with his possible values, "draft", "standard", "candidate to standard", "rejected", etc. I propose to create this property, and the previous items, and use this property only in case when doesn't exists a more specific property. Giovanni Alfredo Garciliano Diaz (talk) 19:13, 6 May 2017 (UTC)[reply]

The description only talks about software. But the proposal is broader? So for example, a person can have a status 'live' or 'dead', or 'married', 'unmarried'? --Hannolans (talk) 19:40, 6 May 2017 (UTC)[reply]

@Hannolans: No, for those there should be other more specific properties. This property is related with software items. Giovanni Alfredo Garciliano Diaz (talk) 23:36, 17 May 2017 (UTC)[reply]

I would suggest to call it something like 'Software life cycle state" in that case. 'Current state' can mean anything--Hannolans (talk) 00:02, 18 May 2017 (UTC)[reply]

@Hannolans: Can I change the name of this proposal? Or I must to create a new proposal? Giovanni Alfredo Garciliano Diaz (talk) 19:17, 21 May 2017 (UTC)[reply]

I think changing 'en = current status' and 'es = Estado actual' is enough--Hannolans (talk) 19:19, 21 May 2017 (UTC)[reply]

NB: I would remove 'current', as we would have multiple states with a start and end date (alpha from to, beta from to). --Hannolans (talk) 19:39, 21 May 2017 (UTC)[reply]

@ChristianKl:, @Hannolans: I've changed the property name. Giovanni Alfredo Garciliano Diaz (talk) 02:38, 26 May 2017 (UTC)[reply]

Oppose towards the present name. If a status is only true at a particular moment of time properties like "start time", "end time" and "point in time" should be used. Using "end time"="NoValue" is also a possible way to signal that the project is still active. ChristianKl (talk) 17:52, 22 May 2017 (UTC)[reply]

Discovered we already have version type (P548). See Wikidata:WikiProject_Informatics/Software --Hannolans (talk) 06:59, 26 May 2017 (UTC)[reply]

Support — Dimon4ezzz (^обс.) 14:32, 18 August 2017 (UTC)[reply]

Comment Maybe a more appropiate name could be «Developer state». And we could be to expand the use to other items. Giovanni Alfredo Garciliano Diaz (talk) 00:15, 4 October 2017 (UTC)[reply]

Oppose, use version type (P548) to indicate the maturity of the project, plus the inception/abolished claims which should be enough to tell if a project is active. − Pintoch (talk) 15:03, 19 February 2018 (UTC)[reply]

Not done Lack of support. Micru (talk) 21:26, 20 March 2018 (UTC)[reply]