Property talk:P4937
Jump to navigation
Jump to search
Documentation
Japan Rugby Football Union player ID
identifier for a rugby union player on the Japan Rugby Football Union website
identifier for a rugby union player on the Japan Rugby Football Union website
[create Create a translatable help page (preferably in English) for this property to be included here]
Item “instance of (P31): human (Q5)”: Items with this property should also have “instance of (P31): human (Q5)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P4937#Item P31, hourly updated report, search, SPARQLDistinct 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/P4937#Unique value, SPARQL (every item), SPARQL (by value)
Item “occupation (P106): rugby union player (Q14089670), rugby sevens player (Q26237722)”: Items with this property should also have “occupation (P106): rugby union player (Q14089670), rugby sevens player (Q26237722)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P4937#Item P106, hourly updated report, searchAllowed 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/P4937#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/P4937#Scope, SPARQL
Item “sport (P641): rugby union (Q5849), rugby sevens (Q270102)”: Items with this property should also have “sport (P641): rugby union (Q5849), rugby sevens (Q270102)”. (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/P4937#Item P641, search
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/P4937#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4937#Format, SPARQL
|
|
Note about this property
[edit]This property links a Rugby Union player item to player articles in Japan Rugby Football Union website. The values are not identifying players, but identifying pages describing a player at some time. A player can have multiple such pages time to time, so we cannot assume single-value constraint. Mzaki (talk) 05:47, 22 January 2024 (UTC)
- There are 4 player properties related to Japan Rugby Football Union: Japan Rugby Football Union player ID (P4937), P4938 (P4938), P4940 (P4940), and P4941 (P4941). All these properties share the ID namespace, and accessible with the same URL, formatter URL (P1630)https://www.rugby-japan.jp/player/$1. The difference among them comes from the fact that the player will be listed in 4 different categories and accessible with the specific URL, formatter URL (P1630)https://www.rugby-japan.jp/****/member/detail/$1 during he/she is selected as a national team member of 4 categories: men's, women's, men's sevens, and women's sevens. I think this distinction is needless and these 4 properties should be unified. Mzaki (talk) 07:09, 22 January 2024 (UTC)
- Hello @Mzaki. When I proposed these 4 Properties for creation, I think that the URL structure was not shared between the 4 categories and the website has since evolved... or I was not aware of it ! In any case, if a shared URL structure exists, I am in favour of merging the 4 properties ID. - Daxipedia - 達克斯百科 (talk) 21:43, 22 January 2024 (UTC)
- Thanks for your comment, @Daxipedia. Since P4938, P4940, and P4941 have single use for each, actually nobody uses after its creation based on the proposal, we can proceed for requesting deletion of these 3 properties in order to unify them into P4937. Mzaki (talk) 09:45, 23 January 2024 (UTC)
- Since there was no objection against my proposal for almost a month, I have changed the English label and description to accommodate statements of 3 properties, and flushed the translations in other languages, keeping old labels as aliases. Mzaki (talk) 14:25, 20 February 2024 (UTC)
- Thanks for your comment, @Daxipedia. Since P4938, P4940, and P4941 have single use for each, actually nobody uses after its creation based on the proposal, we can proceed for requesting deletion of these 3 properties in order to unify them into P4937. Mzaki (talk) 09:45, 23 January 2024 (UTC)
- Hello @Mzaki. When I proposed these 4 Properties for creation, I think that the URL structure was not shared between the 4 categories and the website has since evolved... or I was not aware of it ! In any case, if a shared URL structure exists, I am in favour of merging the 4 properties ID. - Daxipedia - 達克斯百科 (talk) 21:43, 22 January 2024 (UTC)
Categories:
- Japan-related properties
- All Properties
- Properties with external-id-datatype
- Properties used on 10+ items
- Properties with constraints on items using them
- Properties with unique value constraints
- Properties with entity type constraints
- Properties with scope constraints
- Properties with format constraints
- Sports properties