Property talk:P13371
Add topicAppearance
Latest comment: 1 year ago by Olea in topic Repurposing the property
Documentation
Historia Hispánica ID
identifier in the Historia Hispánica website portal
identifier in the Historia Hispánica website portal
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “human (Q5), group of humans (Q16334295), fictional human (Q15632617), mythical character (Q4271324), occurrence (Q1190554)”: item must contain property “instance of (P31), subclass of (P279)” with classes “human (Q5), group of humans (Q16334295), fictional human (Q15632617), mythical character (Q4271324), occurrence (Q1190554)” or their subclasses (defined using subclass of (P279)). (Help)
List of violations of this constraint: Database reports/Constraint violations/P13371#Type Q5, Q16334295, Q15632617, Q4271324, Q1190554, hourly updated report, SPARQLFormat “
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). (biografias|hechos)/[1-9][0-9]*”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P13371#Format, SPARQL
Single value: this property generally contains a single value. (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/P13371#Single value, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of violations of this constraint: Database reports/Constraint violations/P13371#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)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/P13371#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/P13371#Scope, SPARQL
Label required in languages: es, mul: Entities using this property should have labels in one of the following languages: es, mul (Help)
List of violations of this constraint: Database reports/Constraint violations/P13371#Label in 'es, mul' language, hourly updated report, search, SPARQL
| ||||||||||||||||||||||||||||||||||||||||||
Repurposing the property
[edit]User:Olea: this was proposed as a property for a person identifier in a biographical dictionary, and created as such. Honestly, changing it afterwards including "biografias/" and "hechos/" as prefixes IMHO is not correct. Is amalgamating clearly distinct identifiers into the same property useful to Wikidata with regards constraints, external reuses and so? For example we have BVMC place ID (P4098), BVMC person ID (P2799). How convenient would a property conflating all these ID's because they incidentally share part of their formatter url be? If these "hechos" ID's had been deemed useful, a new property should've been proposed for them. Very poorly executed. strakhov (talk) 10:39, 15 March 2025 (UTC)
- Fair enough. When the new property get ready I'll perform the modifications. —Ismael Olea (talk) 20:47, 16 March 2025 (UTC)
Categories:
- Spain-related properties
- All Properties
- Properties with external-id-datatype
- Properties used on 10000+ items
- Properties with constraints on type
- Properties with format constraints
- Properties with single value constraints
- Properties with unique value constraints
- Properties with entity type constraints
- Properties with scope constraints
- Properties with label language constraints