Property talk:P11063

Latest comment: 2 years ago by Jean-Frédéric in topic How to use?

Documentation

Associated itemUnterhaltungssoftware Selbstkontrolle (Q157754)
Applicable "stated in" valueUSK Classification Database (Q105272106)
Data typeExternal identifier
Domainvideo game (Q7889), video game compilation (Q16070115) or expansion pack (Q209163)
Allowed values^[1-9]\d{0,4}$
ExampleBloodNet (Q4927532)1
Elden Ring (Q64826862)50644
50632
50645
50646
Monster Hunter World: Iceborne (Q81690497)46484
46485
Metal Gear Solid: The Legacy Collection (Q15199106)35702
SaGa Frontier 2 (Q2660493)4496
Sourcehttps://usk.de/usktitle/
https://usk.de/en/usktitle/
Formatter URLhttps://usk.de/usktitle/$1
https://usk.de/en/usktitle/$1
Related to country  Germany (Q183) (See 361 others)
See alsoUSK rating (P914)
Lists
Proposal discussionProposal discussion
Current uses
Total2,622
Main statement2,096 out of 39,665 (5% complete)79.9% of uses
Qualifier90.3% of uses
Reference51719.7% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P11063#Unique value, SPARQL (every item), SPARQL (by value)
Format “^[1-9]\d{0,4}$: 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). Known exceptions: Aces of the Deep (Q1467531), Der Planer (Q1196230), Star Wars: X-Wing (Q54853), Q-Pop (Q114227287)
List of violations of this constraint: Database reports/Constraint violations/P11063#Format, 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/P11063#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/P11063#Scope, SPARQL
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/P11063#allowed qualifiers, SPARQL
Label required in languages: de: Entities using this property should have labels in one of the following languages: de (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/P11063#Label in 'de' language, search, SPARQL
Required qualifier “platform (P400): this property should be used with the listed qualifier. (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/P11063#mandatory qualifier, SPARQL
Item “publisher (P123): Items with this property should also have “publisher (P123)”. (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/P11063#Item P123, search, SPARQL
Item “language of work or name (P407): Items with this property should also have “language of work or name (P407)”. (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/P11063#Item P407, search, SPARQL

How to use?

edit

@Jean-Frédéric, Dexxor, Sir Lothar, Telaneo: How are items supposed to be modelled and existing statements migrated, especially with regards to rating certificate ID (P2676) and qualifiers like platform (P400), start time (P580) and subject named as (P1810)? For example Cyberpunk 2077 (Q3182559):

USK rating
  USK 18
rating certificate ID 48018/20
start time
platform Microsoft Windows
subject named as (optional) Cyberpunk 2077
0 references
add reference
add value
USK ID
  48018
start time
platform Microsoft Windows
subject named as (optional) Cyberpunk 2077
0 references
add reference
add value

If this is the intended model, I'd say that USK rating (P914)property constraint (P2302)required qualifier constraint (Q21510856)property (P2306)rating certificate ID (P2676) (link) should be removed. Also, I'd suggest creating a property documentation for this property and USK rating (P914). --Nw520 (talk) 11:20, 24 September 2022 (UTC)Reply

Yes, this is the intended model, but subject named as (P1810) shouldn't be a required qualifier. Dexxor (talk) 08:42, 25 September 2022 (UTC)Reply
start time (P580) and subject named as (P1810) are currently not included in the list of allowed qualifiers. --Nw520 (talk) 11:01, 25 September 2022 (UTC)Reply

(Sorry for the belated answer) I would keep rating certificate ID (P2676) as qualifier to USK rating (P914). In general I think it makes some sense for consistency with other rating properties (but not a very strong argument I’d agree) ; in this case there’s actually a difference between the certificate ID (48018/20 in the example) and the USK ID (48018, missing the post slash numbers). I don’t really understand what’s the point of this suffix, but I’d guess it’s worth keeping. Jean-Fred (talk) 13:58, 14 October 2022 (UTC)Reply

Return to "P11063" page.