Property talk:P5448

Documentation

• Start a query
• Properties using this qualifier (statistics)
• Count

upper limit
upper limit of a range or an interval; (qualifier) used with a dummy value which specifies the type of the range or interval

Has quality	maximum (Q10578722)
Data type	Quantity
Domain	set (Q36161) or class (Q217594)
Allowed values	any (note: this should be moved to the property statements)
Allowed units	any (note: this should be moved to the property statements)
Example	According to this template: see sample on Property talk:P5446 According to statements in the property: red blood cell count (Q48632255) → 5.55 trillion cells per litre closed interval from −1 to 1 (Q21813730) → 1 When possible, data should only be stored as statements
Source	w:en:Reference ranges for blood tests, w:en:Clinical urine tests, etc. (note: this information should be moved to a property statement; use property source website for the property (P1896))
<complementary property>	lower limit (P5447)
See also	maximum value (P2312)
Lists	Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Minimum and maximum Items with highest numeric value Items with lowest numeric value User:Laboramus/Units/P5448 (Units used) Database reports/Constraint violations/P5448
Proposal discussion	Proposal discussion
Current uses	Total 424 Main statement 53 12.5% of uses Qualifier 371 87.5% of uses

[create Create a translatable help page (preferably in English) for this property to be included here]

Allowed entity types are Wikibase item (Q29934200), Wikibase MediaInfo (Q59712033): the property may only be used on a certain entity type (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/P5448#Entity types

Scope is as qualifier (Q54828449), as main value (Q54828448): the property must be used by specified way only (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/P5448#Scope, SPARQL

Type “set (Q36161), class (Q217594)”: item must contain property “instance of (P31), subclass of (P279)” with classes “set (Q36161), class (Q217594)” or their subclasses (defined using subclass of (P279)). (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/P5448#Type Q36161, Q217594, SPARQL

Item “reference value (P5446): reference range as qualifier (Q55426051)”: Items with this property should also have “reference value (P5446): reference range as qualifier (Q55426051)”. (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/P5448#Item P5446, SPARQL

Constraint

@Infovarius: Should the property be used for sets for discrete sets which only contain a specific group of numbers within a range (i.e. integers or 0 for singleton of 0 (Q47342419) and others)? I'm not sure how this is supposed to be defined, and it currently displays a constraint violation on that item. Jc86035 (talk) 07:56, 12 July 2018 (UTC)

It was proposed as a qualifier to another property. Please re-read the description.
--- Jura 08:00, 12 July 2018 (UTC)

No, it is not restricted to the qualifier of reference value (P5446) [1]. --Okkn (talk) 08:13, 12 July 2018 (UTC)

As I read it, it's meant to be a qualifier, not a main property. You even call it "general qualifier". As I understood it, the property can be different (or the property value different from Q55426051), but it would still be a qualifier.
--- Jura 08:16, 12 July 2018 (UTC)

I presented closed interval from −1 to 1 (Q21813730) as an example, and suggested that "these properties can be used as usual properties" [2]. --Okkn (talk) 08:26, 12 July 2018 (UTC)

Somehow I missed that as I don't think it was added to the proposal template. I don't think there is a need to add yet another way of specifying things (5th or 6th).
--- Jura 08:41, 12 July 2018 (UTC)

Original descriptions of lower limit (P5447) and upper limit (P5448) in the proposal were consists of two parts, and I intended that the former part can be applied to both main property and qualifier... --Okkn (talk) 08:54, 12 July 2018 (UTC)

@Jura1, Okkn: Statement/qualifier restriction aside, can the properties be used on non-continuous ranges, such as those which only contain integers (e.g. set of prime numbers (Q47370614) – lower limit 2; set of non-positive integers (Q47379086) – upper limit 0)? Jc86035 (talk) 09:01, 12 July 2018 (UTC)

@Jc86035: I think that's reasonable, and I have no reason to oppose it. --Okkn (talk) 09:22, 12 July 2018 (UTC)

@Okkn: I've changed the type constraint for both properties to set (Q36161). Incidentally, are these always inclusive of the limits (i.e. could set of positive real numbers (Q47494165) have lower limit (P5447) 0), or must this be inferred from something like instance of (P31) → open set (Q213363)? Jc86035 (talk) 09:27, 12 July 2018 (UTC)

There's some ambiguity as to whether the lower limit is a minimum (Q10585806), an infimum (Q1199948), or just a lower bound (Q12254923). Currently I'm using the qualifier object has role (P3831) for clarification but hopefully there will be a better way. 慈居 (talk) 01:03, 9 September 2023 (UTC)

I thought it was just a sub-optimal description, as the samples indicated use as qualifier. I should probably propose this for deletion then.
--- Jura 09:02, 12 July 2018 (UTC)

Not adding examples was my lack of consideration, but the changes of these descriptions were according to this Was a bee's question. I chose to make these properties be able to use everywhere. I think there is no need to delete. --Okkn (talk) 09:22, 12 July 2018 (UTC)