Property talk:P11088

Distinct values: this property likely contains a value that is different from all other items. (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/P11088#Unique value, SPARQL (every item), SPARQL (by value)

Format “^\d{15,17}$”: value must be formatted using this pattern (PCRE syntax). (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/P11088#Format, SPARQL

Type “video game (Q7889), application (Q166142), virtual reality software (Q130380979)”: item must contain property “instance of (P31)” with classes “video game (Q7889), application (Q166142), virtual reality software (Q130380979)” 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/P11088#Type Q7889, Q166142, Q130380979, SPARQL

Allowed entity types are Wikibase item (Q29934200): 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/P11088#Entity types

Scope is as main value (Q54828448), as reference (Q54828450): 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/P11088#Scope, SPARQL

Item “output device (P5196): Oculus Quest (Q63777286), Quest 2 (Q99620218), Oculus Rift (Q3274429), Oculus Rift (Q69464718), Oculus Rift S (Q64021532), Oculus Go (Q56353330), Gear VR (Q18031572), Meta Quest 3 (Q119090835), Meta Quest 3S (Q130437846)”: Items with this property should also have “output device (P5196): Oculus Quest (Q63777286), Quest 2 (Q99620218), Oculus Rift (Q3274429), Oculus Rift (Q69464718), Oculus Rift S (Q64021532), Oculus Go (Q56353330), Gear VR (Q18031572), Meta Quest 3 (Q119090835), Meta Quest 3S (Q130437846)”. (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/P11088#Item P5196

Item “distributed by (P750): Meta Store (Q110074099), Oculus Rift Store (Q110870359), Oculus Go Store (Q110872622), Oculus Gear VR Store (Q110872637)”: Items with this property should also have “distributed by (P750): Meta Store (Q110074099), Oculus Rift Store (Q110870359), Oculus Go Store (Q110872622), Oculus Gear VR Store (Q110872637)”. (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/P11088#Item P750, search

Pattern ^(quest|rift|go|gear-vr)/(\d{15,17})$ will be automatically replaced to \2. Testing: TODO list

I see that the database has finally updated its domain and decided to stop using prefixes, which is good. Since the new formatter URL has already been set, I also changed the current regex, corrected the property IDs to the new format (i.e. prefixless format) and finally added an autofix so that the Mix'n'Match IDs will be corrected to the new format as well. Regards Kirilloparma (talk) 01:23, 2 May 2024 (UTC)[reply]