Wikidata:Property proposal/propriétés à éviter

From Wikidata
Jump to navigation Jump to search

inappropriate property for this type[edit]

Originally proposed at Wikidata:Property proposal/Generic

Descriptionproperty that should not be present for instances of that element
Data typeProperty
Example 1human (Q5)native label (P1705)
Example 2human (Q5)country (P17)
Example 3higher education institution (Q38723)academic degree (P512)
See also

Motivation[edit]

I don't know if it has been already discussed. Is there a contrary of properties for this type (P1963) so that one can state "properties that should be avoided on that item". For instance for a instance of (P31)=human (Q5) ( https://www.wikidata.org/wiki/Q5#P1963 ) , that property would state properties that might happen on items by error/confusion. Other examples : Q640506 should have inception (P571)+dissolved, abolished or demolished date (P576) but not date of birth (P569) date of death (P570). It's often obvious, sometimes confusion/doubts/faux-amis may appear. Bouzinac💬✒️💛 11:00, 28 November 2020 (UTC)[reply]

Discussion[edit]

  •  Comment in principle that sounds like a good idea, but one issue that I have is that it would need to be very clear what properties should be listed here - potentially the list could become very long and hard to use. How can we avoid this just becoming a laundry list of properties that make no sense? Should this be limited to "commonly confused properties" for example? --Hannes Röst (talk) 18:27, 30 November 2020 (UTC)[reply]
    Of course, shouldn't get all other existing properties, but be mainly a guideline to help prevent confusion, help answer questions such as "I am looking at this instance (building/battle/people/book/etc). Should I use that property or that other property?" . Good dates properties into P1963, bad dates properties into that new property. You get the idea Bouzinac💬✒️💛 20:13, 30 November 2020 (UTC)[reply]
  • I feel like restraints can accomplish this without the problems Hannes mentioned. NMaia (talk) 01:15, 1 December 2020 (UTC)[reply]
  • You could likely list 1000 properties that should never be used. How do we limit the amount of properties that get listed here? date of death (P570) seems to me very obviously not to apply to buildings and as such it's unclear what we gain by explicitely stating that. If we do want to have a property here maybe it could express that country of citizenship should be used instead of country for humans. ChristianKl20:12, 1 December 2020 (UTC)[reply]
  •  Support In working on the anatomy ontology I found that I need a property like this. I would like to word it in a way that doesn't say what the modeller should do but that's about the inherent nature. I propose "inappropriate property". ChristianKl17:09, 5 December 2020 (UTC)[reply]
  •  Comment I think it could work and complete properties for this type (P1963). Initially, I was more sceptical with negative properties, but they tend to work out.
  1. About the label: As the complementary property is called "property for this type", maybe "for this type" should be included.
  2. About the samples: I think it would be good to find better samples than the (current) P569/P570 (building (Q41176) → date of death (P570), cabinet (Q640506) → date of birth (P569)), even if eventually we find that these checks are worthwhile. This could help.
  3. Allowed values: Also, maybe one should avoid using external-id properties as values, these can easily be handled on properties.
  4. Domain: Similarly items with Wikidata property (P1687) probably wont need this. --- Jura 18:21, 5 December 2020 (UTC)[reply]
@Bouzinac, Hannes Röst, NMaia, ChristianKl, Jura1: @Dr.üsenfieber, Okkn: ✓ Done inappropriate property for this type (P8952) Pamputt (talk) 20:47, 12 December 2020 (UTC)[reply]