Property talk:P1112

From Wikidata
Jump to navigation Jump to search

This property is being considered for deletion. Please share your thoughts on the matter at this property's entry on the Properties for deletion page.


Documentation

Pokédex number
Pokémon identification number
Descriptiona Pokémon identification number
RepresentsPokédex (Q1250520)
Data typeQuantity
Domain
According to this template: any Pokémonn
According to statements in the property:
Pokémon species (Q3966183)
When possible, data should only be stored as statements
Allowed valuesidentification numbers (note: this should be moved to the property statements)
Allowed unitsnot applicable
Example
According to this template:

<Bulbasaur>

According to statements in the property:
Ivysaur (Q1636903) → 2
When possible, data should only be stored as statements
Sourcein-game informations from the Pokémon main games, external references, Wikipedia list article (note: this information should be moved to a property statement; use property source website for the property (P1896))
Lists
Proposal discussionProperty proposal/Archive/18#P1112
Current uses811
[create] Create a translatable help page (preferably in English) for this property to be included here
Type “Pokémon species (Q3966183): element must contain property “instance of (P31)” with classes “Pokémon species (Q3966183)” or their subclasses (defined using subclass of (P279)). (Help)
List of this constraint violations: Database reports/Constraint violations/P1112#Type Q3966183, hourly updated report, SPARQL, SPARQL (new)
Item “from fictional universe (P1080): Pokémon universe (Q17562848): Items with this property should also have “from fictional universe (P1080): Pokémon universe (Q17562848)”. (Help)
List of this constraint violations: Database reports/Constraint violations/P1112#Item P1080, hourly updated report, SPARQL, SPARQL (new)
Range from “0” to “807”: values should be in the range from “0” to “807”. (Help)
List of this constraint violations: Database reports/Constraint violations/P1112#Range, hourly updated report, SPARQL (new)
Units: “novalue”: value unit must be one of listed. (Help)
List of this constraint violations: Database reports/Constraint violations/P1112#Units, hourly updated report, SPARQL (new)
Mandatory qualifier “of (P642): this property should be used with the listed qualifier. (Help)
List of this constraint violations: Database reports/Constraint violations/P1112#mandatory qualifier, hourly updated report, SPARQL, SPARQL (new)
Mandatory qualifier “follows (P155): this property should be used with the listed qualifier. (Help)
List of this constraint violations: Database reports/Constraint violations/P1112#mandatory qualifier, hourly updated report, SPARQL, SPARQL (new)
Mandatory qualifier “followed by (P156): this property should be used with the listed qualifier. (Help)
List of this constraint violations: Database reports/Constraint violations/P1112#mandatory qualifier, hourly updated report, SPARQL, SPARQL (new)
Conflicts with “follows (P155): this property must not be used with the listed properties and values. (Help)
List of this constraint violations: Database reports/Constraint violations/P1112#Conflicts with P155, hourly updated report, SPARQL, SPARQL (new)
Conflicts with “followed by (P156): this property must not be used with the listed properties and values. (Help)
List of this constraint violations: Database reports/Constraint violations/P1112#Conflicts with P156, hourly updated report, SPARQL, SPARQL (new)
No bounds: values can't have any bounds (e.g. 1 not 1±0) (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1112#No Bounds, SPARQL, SPARQL (new)
Integer: values should be integers (ie. they shouldn't have a fractional part) (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1112#integer, SPARQL, SPARQL (new)
Scope is: the property must be used by specified way only (Help)
List of this constraint violations: Database reports/Constraint violations/P1112#scope, hourly updated report, SPARQL (new)

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)


Which Pokédex?[edit]

@Legoktm, Ju gatsu mikka:

(Continuing Wikidata:Property_proposal/Archive/18#P1112.) This property has now been created, but the issue of how to qualify it to indicate which Pokédex the number is from has not been resolved. stated in (P248) is, as I understand it, only supposed to be used in source fields. --Yair rand (talk) 21:57, 2 February 2014 (UTC)

First of all, doesn't "Data type" should be "String" as there is neither unit nor accurency. Second, I still don't understand what you mean by qualify it. Ju gatsu mikka (talk) 21:31, 6 February 2014 (UTC)
I ask a friend to explain me, if I understand well, the property for the qualiifer should be someting like "Pokédex" and the values "global", "Kanto", "Johto", "Hoenn", "Sinnoh", "Unova", "Kalos", "Fiore", "Almia" and "Oblivia"'. For the three latters however, the restriction for the values will be a problem as their Pokédex use other format : R-XXX mainly, N-XXX (as a second classification for the latter), some S-XXX and one X-001. Ju gatsu mikka (talk) 22:14, 6 February 2014 (UTC)