Property talk:P3260

Documentation

points awarded
points awarded to the winning person, team or work for a win, draw, tie or loss. If no points are awarded for some category of finish (e.g. loss) use value 0 not no value.
Descriptionpoints awarded to the winning person or team for a win, draw, tie or loss. Values should not have uncertainty bounds, so enter "+-0" after the value. If no points are awarded for some category of finish (e.g. loss) use value 0 not no value.
Data typeQuantity
Domainpoint systems, competitions (note: this should be moved to the property statements)
Allowed valuesexact numbers (integer or decimal) (note: this should be moved to the property statements)
Allowed units
According to this template: none
According to statements in the property:
not applicable
When possible, data should only be stored as statements
Usage notesValues should not have uncertainty bounds, so enter "+-0" after the value. If no points are awarded for some category of finish (e.g. loss) use value 0 not no value.
Οι τιμές πρέπει να μην έχουν καθορισμένο όρια, έτσι προσθέστε "+-0" μετά την τιμή. Αν για κάποια κατηγορία δεν απονέμονται βαθμοί (π.χ. στην ήττα) χρησιμοποιήστε την τιμή 0 αντί του "καμία τιμή".
Werte sollen keine Ungenauigkeitsgrenzen haben, deshalb sollte "+-0" hinter dem Wert eingegeben werden; falls keine Punkte für bestimmte Ergebnisse (z. B. Verloren) vergeben werden, nutze "0" und nicht kein Wert.
Examplethree points for a win (Q1431533) → 3
three points for a win (Q1431533) → 1
three points for a win (Q1431533) → 0
Lists
Proposal discussionProposal discussion
Current uses
Total83
Main statement4959% of uses
Qualifier3441% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
Units: “novalue”: value unit must be one of listed. (Help)
List of violations of this constraint: Database reports/Constraint violations/P3260#Units, hourly updated report
No bounds: values can't have any bounds (e.g. 1 not 1±0) (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P3260#No Bounds, SPARQL
Integer: values should be integers (ie. they shouldn't have a fractional part) (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: draw (Q1137224)
List of violations of this constraint: Database reports/Constraint violations/P3260#integer, SPARQL
Return to "P3260" page.