Hi, 

aggregate demand -- broader external class --> https://schema.org/Demand
place of devotion -- broader external class --> https://schema.org/Place
festival -- broader external class --> https://schema.org/Event

 According to the "creator" of the property narrower external class (P3950), " the reverse (...) is less required because more general classes are more likely to be included in Wikidata anyway.  "

These examples seem to prove him right, since "demand" exists in Wikidata and is already linked to "http://schema.org/Demand" via the equivalent class property. Same thing for https://schema.org/Event, already mapped with event, or for  https://schema.org/Place , which could be associated with location (not sure).

To be clear, I support the creation of "broader external class" because it can be used with some external vocabularies; I point this out just to make sure that all existing mapping possibilities are used. :)

Cheers,

Ettore Rizza


On Wed, 26 Sep 2018 at 03:53, Thad Guidry <thadguidry@gmail.com> wrote:
Sure, Dan

aggregate demand -- broader external class --> https://schema.org/Demand

place of devotion -- broader external class --> https://schema.org/Place

festival -- broader external class --> https://schema.org/Event

Usually we can discover these relationships quite easily with "What links here" on the GUI and applicable SPARQL queries, but then would like to apply the Wikidata->Schema.org mappings when we discover those relationships can be made.  I suck at PHP, so I couldn't build or contribute to a native application for Wikidata to host that application to auto discover some of these mappings, but would be happy to assist someone who could code in PHP to build such application...here's looking at you, Magnus ?  :-)


On Tue, Sep 25, 2018 at 7:07 PM Dan Brickley <danbri@google.com> wrote:
On Tue, 25 Sep 2018 at 16:35, Thad Guidry <thadguidry@gmail.com> wrote:
Hi Team !

Schema.org mapping is progressing on every new Weekly Summary "Newest properties" listing.
That's great !  And thanks to Léa and team for providing the new properties listing !

What's not great, is many times, we cannot apply a "broader external class" to map to a Schema.org Type.  This is because "broader concept" https://www.wikidata.org/wiki/Property:P4900 is constrained to "qualifiers only and not for use on statements".

We are able to use the existing "narrower external class" , for example like here on this topic, https://www.wikidata.org/wiki/Q7406919 , but there is no "broader external class" property in Wikidata yet from what we see.

It would be awesome if someone could advocate for that new property to help map Wikidata to external vocabularies that have broader concepts quite often, such as Schema.org.

Could you give 2-3 specific examples, to help motivate the request, for folk who're not tracking this work?
 
Dan

_______________________________________________
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata