Wikidata:Property proposal/external subclass
narrower external class[edit]
Originally proposed at Wikidata:Property proposal/Generic
| Description | More specific subclass in other ontologies |
|---|---|
| Data type | URL |
| Domain | any item |
| Allowed values | URI |
| Example | collector (Q3243461) → http://comicmeta.org/cbo/Collector (comic book collector) slate (Q207079) → http://purl.org/heritagedata/schemes/eh_tbm/concepts/97716 (artificial slate) |
| Source | external ontologies |
| Planned use | Mapping Comic Book Ontology and other Ontologies to Wikidata |
| Robot and gadget jobs | none yet |
| See also | equivalent class (P1709), exact match (P2888) |
- Motivation
The following properties exist for mapping external ontologies to Wikidata:
- equivalent property (P1628), external superproperty (P2235), and external subproperty (P2236) to align properties
- equivalent class (P1709) and exact match (P2888) to align classes and concepts
The proposed property is needed to map a Wikidata item to a more specific class from an external ontology if Wikidata does not contain the more specific item. Note that the reverse (external superproperty) is less required because more general classes are more likely to be included in Wikidata anyway. The proposed property could also help to improve Wikidata by detecting which concepts are possibly missing from Wikidata without mass-creation of very specific concepts by non-experts. -- JakobVoss (talk) 13:51, 12 March 2017 (UTC)
WikiProject Ontology has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
- Discussion
Support I agree this seems very useful. However I don't think your first example is a subclass relationship (the other two look good). A specific type of page would be a subclass of "page", but a general "type" is a different kind of class. ArthurPSmith (talk) 17:11, 13 March 2017 (UTC)
- good point, is there any other super-class of "page type" in Wikidata? I have not even found "document type" -- JakobVoss (talk)
- I changed the example: Comic book collector (https://comicmeta.org/cbo/Collector.html) is an external subclass of collector (Q3243461) -- JakobVoss (talk) 12:10, 13 April 2017 (UTC)
- I'm not sure that the current name/description is as clear as it can be. Is there prior art in other projects that might inform how we name and describe this? ChristianKl (talk) 08:19, 30 March 2017 (UTC)
- See https://www.w3.org/TR/skos-reference/#mapping - the proposedl property could also be named "narrower external class" or "external narrower class". -- JakobVoss (talk) 12:10, 13 April 2017 (UTC)
- Support In my opinion the property would be useful. Re. naming, I too would prefer "narrower external class" or "external narrower class": With "exernal subclass", one thinks of a formal subclass relationship. The description should reflect this, e.g. "More specific class in other ontologies" Jneubert (talk) 12:42, 13 April 2017 (UTC)
Comment In English, applying proper adjective order gives us "narrower external class" as opposed to "external narrower class". Josh Baumgartner (talk) 16:52, 1 May 2017 (UTC)
- @JakobVoss, ArthurPSmith, Josh Baumgartner, Jneubert:
Done ChristianKl (talk) 21:21, 14 May 2017 (UTC)
@JakobVoss: Added alias "external subclass". I even think we should make this the pref name? --Vladimir Alexiev (talk) 09:52, 30 October 2020 (UTC)
External Superclass[edit]
WikiProject Ontology has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
@JakobVoss, ArthurPSmith, Josh Baumgartner, Jneubert:
Currently we have this:
- Classes:
- equivalent class (P1709)
- external subclass i.e. narrower external class (P3950)
- Properties:
- equivalent property (P1628)
- external subproperty (P2236)
- external superproperty (P2235)
I think we need "External Superclass", at least for symmetry. Jacob wrote "Note that the reverse (external superclass) is less required because more general classes are more likely to be included in Wikidata anyway".
Yes, WD has 10x more classes than eg Schema, but that doesn't necessarily mean we can do adequate mapping with only equivalent & subclass.
Here is an example: https://schema.org/SportsEvent is best covered by two classes:
- Sports competition (Q13406554) with 10.7k direct instances
- Sporting event (Q16510064) with 27k direct instances
WD's class hierarchy is a bit weird here:
- Sporting event (Q16510064) is subclass of Competition (Q841654) but Sports competition (Q13406554) is subclass only of Event (Q1656682)
- Sports competition (Q13406554) "has parts of the class" Sporting event (Q16510064)
- So Sports competition is considered a series (whole) whereas Sporting event is considered atomic (part).
Mapping
- https://schema.org/SportsEvent seems to be an individual match, so maps to Sporting event (Q16510064).
- But what can we map Sports competition (Q13406554) to? there is https://schema.org/EventSeries, but it's not only about sport
TLDR, we need to be able to state this:
- (CAN) Sporting event (Q16510064) equivalent class https://schema.org/SportsEvent
- (CANNOT) Sports competition (Q13406554) external superclass https://schema.org/EventSeries, https://schema.org/SportsEvent
If I get positive feedback, I'll make a prop proposal --Vladimir Alexiev (talk) 09:52, 30 October 2020 (UTC)