Property talk:P4179

Active discussions


tabular population
same as population (P1082); used when there is data for many different points in time
[create Create a translatable help page (preferably in English) for this property to be included here]
Scope is as main value (Q54828448): the property must be used by specified way only (Help)
List of this constraint violations: Database reports/Constraint violations/P4179#scope, hourly updated report, SPARQL, SPARQL (new)
Item “population (P1082): Items with this property should also have “population (P1082)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P4179#Item P1082, SPARQL, SPARQL (new)

Data structureEdit

Is there any way we can standardize these data so that a software client understands that the software client understands that in commons:Data:Taipei "1337350" refers the female population in February 2001. Ideally, I suppose the header would have a reference to a Wikidata item for female population. -Zolo (talk) 08:12, 27 August 2017 (UTC)

I updated the sample data to a later revision (per the talk section on the original proposal). The headers are more easy to parse now. S-1-5-7 (talk) 15:05, 27 August 2017 (UTC)
Is the text in the headers after the underscore really necessary? I feel like it just confuses things. Also, I don't suppose there are any constraints that work with this datatype that would help enforce the standard? (If there isn't, is there a place to propose new constraint types?) --Yair rand (talk) 00:15, 5 September 2017 (UTC)
@Yair: They make it more human readable and it would be trivial to parse out in code (e.g., regex "^([PS]\d+)"). They wouldn't even need to be standardised since the P###/S### is the only important part. I am not sure about the constraints.S-1-5-7 (talk) 07:19, 5 September 2017 (UTC)
Return to "P4179" page.