Property talk:P3026
Documentation
exceptions to open days (P3025), usually special dates
Data type | Item | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Usage notes | Can be used as a qualifier with P3025 or as a standalone property. | |||||||||
Example | British Museum (Q6373) → December 24 (Q2705) | |||||||||
<complementary property> | open days (P3025) | |||||||||
See also | open period from (P3027), open period to (P3028), opening time (P8626), closing time (P8627) | |||||||||
Lists | ||||||||||
Proposal discussion | Proposal discussion | |||||||||
Current uses |
| |||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P3026#Value type Q14795564, Q1445650, Q41825, Q1197685, Q99731370, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3026#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3026#Entity types
This property is being used by: Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Qualifier?
[edit]Pinging folks who participated in the discussion of the property proposal: @Jura1, Lymantria, Pigsonthewing, ArthurPSmith, K7L: this property was intended as a qualifier for open days (P3025) on the assumption that open days (P3025) will always accept neat, single values like in the example of British Museum (Q6373). However, opening hours are usually more complex than that, as can be seen on SOJO (Q28804296), which currently indicates a constraint violation because of this. I'm wondering if we can remove the qualifier constraint and allow this to be used as a standalone property. What do you think? NMaia (talk) 03:40, 2 May 2019 (UTC)
- Relaxing the constraint is ok with me. ArthurPSmith (talk) 12:31, 2 May 2019 (UTC)