Property talk:P11063
Documentation
identifier of a work in the USK database
List of violations of this constraint: Database reports/Constraint violations/P11063#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P11063#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P11063#Type Q7889, Q16070115, Q209163, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P11063#Entity types
List of violations of this constraint: Database reports/Constraint violations/P11063#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P11063#allowed qualifiers, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P11063#Label in 'de' language, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P11063#mandatory qualifier, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P11063#Item P123, search, SPARQL
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 |
| ||||||||||||||||||
add value |
USK ID |
| ||||||||||||||||
add value |
If this is the intended model, I'd say that USK rating (P914)property constraint (P2302)required qualifier constraint (Q21510856) Also, I'd suggest creating a property documentation for this property and USK rating (P914). --Nw520 (talk) 11:20, 24 September 2022 (UTC)
- 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)
- 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)
(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)
- Pages using the JsonConfig extension
- Germany-related properties
- All Properties
- Properties with external-id-datatype
- Properties used on 1000+ items
- Properties with unique value constraints
- Properties with format constraints
- Properties with constraints on type
- Properties with entity type constraints
- Properties with scope constraints
- Properties with qualifiers constraints
- Properties with label language constraints
- Properties with required qualifiers constraints
- Properties with constraints on items using them
- Games properties