[Wikidata] Request for feedback on CentralNotice banner for Wikidata user diversity survey

[Mohammed Sadat Abdulai]

Hello,

The Wikidata development team at Wikimedia Germany is planning a brief
survey of the core demographics that make up the Wikidata community in
order to provide us with a baseline for future diversity efforts.

To yield representative results, we want to deploy the survey to a broad
range of users via the CentralNotice
.

We have put up a request for a CentralNotice banner
;
the request is open for feedback and comments until February 17th, 2021.
You can also find more information about the survey, the use of the data
and the questions asked

.

Feel free to take a look and let us know if you have any questions.

Cheers,

-- 

Mohammed Sadat

*Community Communications Manager for Wikidata/Wikibase*

Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

[Wikidata] Request for Oversight permissions | Kostas20142

[konstantinos07 .]

Hello everyone,

In accordance with the instructions at
Wikidata:Requests_for_permissions/Oversight
,
I am linking to my candidacy below:

<
https://www.wikidata.org/wiki/Wikidata:Requests_for_permissions/Oversight/Kostas20142
>

Thanks,

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

[Wikidata] Request for Oversight permission

[revi]

Hello,

This is a policy-instructed notification of
https://www.wikidata.org/wiki/Wikidata:Requests_for_permissions/Oversight/-revi
per https://www.wikidata.org/wiki/Wikidata:Oversight

Thank you.

-- 
revi

Please note that this address is list-only address and any non-mailing list
mails will be treated as spam.
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Request

[Stas Malyshev]

Hi!

>> I am facing a problem where I can’t get enough data for my project. So is 
>> there anything that can be done to extend the limit of queries as they 
>> timeout ?

If you have queries that take longer than timeout permits, the options
usually would be:

1. Working with Wikidata dumps, as mentioned before

2. Looking into optimizing your query - maybe timeout happens because
your query is too slow. Check out
https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/query_optimization
and https://www.wikidata.org/wiki/Wikidata:Request_a_query .

3. Download information in smaller chunks using LIMIT/OFFSET clauses.
Note that this doesn't speed up query itself.

4. Use LDF server:
https://www.mediawiki.org/wiki/Wikidata_Query_Service/User_Manual#Linked_Data_Fragments_endpoint

Depending on what data do you need, there probably would be the options.
-- 
Stas Malyshev
smalys...@wikimedia.org

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

Re: [Wikidata] Request

[Guillaume Lederrey]

Hello!

It isn't entirely clear from your email what kind of data you are
looking for, or what endpoint you are using to get this data. If you
need to extract large amount of data from Wikidata, you should
probably start from the dumps [1], not from API calls. Without knowing
more about your context, it is hard to recommend anything.

Good luck for your project!

   Guillaume


[1] https://www.wikidata.org/wiki/Wikidata:Database_download

On Wed, Apr 10, 2019 at 9:14 AM Ahmed Mamdouh  wrote:
>
> Greetings All,
>
> Hope this e-mail finds you well. I am currently doing a master project in NLP 
> in JKU under the supervision of Prof. Bruno Buchberger the famous Austrian 
> Mathematician.
>
> I am facing a problem where I can’t get enough data for my project. So is 
> there anything that can be done to extend the limit of queries as they 
> timeout ?
>
> Thanks in advance,
> Mamdouh
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata



-- 
Guillaume Lederrey
Operations Engineer, Search Platform
Wikimedia Foundation
UTC+1 / CET

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

[Wikidata] Request

[Ahmed Mamdouh]

Greetings All,

Hope this e-mail finds you well. I am currently doing a master project in NLP 
in JKU under the supervision of Prof. Bruno Buchberger the famous Austrian 
Mathematician.

I am facing a problem where I can’t get enough data for my project. So is there 
anything that can be done to extend the limit of queries as they timeout ?

Thanks in advance,
Mamdouh
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Thad Guidry]

Federico,

Yes they are incompatible concepts.  However, one is typically treated as a
subclass of the other.
Its that https://www.wikidata.org/wiki/Q26869695 (nutritional diet) is a
subclass of https://www.wikidata.org/wiki/Q474191 (biological needs diet)
Which is correctly stated now with that 'subclass of' statement on
https://www.wikidata.org/wiki/Q26869695

Yes, it looks like Wikidata did not have the nutritional concept of a Diet,
but only had the biological needs concept.
Thanks to your creation of the nutritional concept of a Diet, this helps
everyone, Schema.org as well as dieticians, nutritionists, and other
scientists.

TODO: We just need to figure out what to do with 'external subclasses' and
a few other things concerning Schema.org mapping.  And that's part of our
Agenda on this Friday's Google Hangout with Lydia and folks.

Thanks again Federico for the bit of help!

Thad
+ThadGuidry 
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Federico Leva (Nemo)]

Thad Guidry, 13/09/2016 19:38:

There is no need, therefore, to replicate those same definitions in
Wikidata by creating a new Wikidata item (topic / entity) for each
external vocabulary class or subclass or property.

Instead, the best practice is to simply POINT to those external
definitions, such as those in Schema.org, DBPedia.org, MusicBrainz,
etc., etc.


Agreed. If the external definition is compatible, just link it. A 
specific item needs to be created only where the two definitions are 
incompatible. I would define two items to be equivalent iff swapping 
them doesn't change the truthness of any statement or inference on 
Wikidata 
(https://en.wikipedia.org/wiki/Equivalence_relation#Well-definedness_under_an_equivalence_relation 
). Makes sense?


I don't know if Q474191 and Q26869695 are incompatible definitions; I 
understood you claimed they were. If the two definitions are compatible, 
we can merge the two items and just consider Q474191 equivalent to 
SchemaOrg's definition of "Diet".


Nemo

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

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Thad Guidry]

Hi Gerard,

Good question.  lolol.  And good point, you did ask about 'how it helps'
and I didn't directly answer that, so here it is.

Schema.org provides a set of guidelines for publishing structured data on
the web in various formats.  You can read more detail on our website.

The answer Part 1 :  Schema.org helps publishers, small and large, even
folks like you and me that might have small websites with important data,
that can be crawled by bots, public scraping scripts, etc. to harvest more
public data for Wikidata to absorb, as well as helping to reconcile data
and even load the Primary Sources tool, Reasonator, or any tool eventually
if we wanted.  Adding references could in theory just be done by a bot that
was smart enough to understand Schema.org markup (there are already many
Python, Ruby, Java libraries that exist for this).

The answer Part 2:  By having Schema.org properties and classes aligned to
existing Wikidata properties and classes.  Both sides benefit to help
understand that structured data even moreand once a machine understands
it better, than those machines can be programmed to gather even more data,
or validate the quality of the existing data.

This mapping effort is not just limited to Schema.org however in the long
term.  Notice that we already have many mappings in Wikidata for external
vocabularies, but its very rudimentary.  We want to help Wikidata have a
more full understanding of data, and that requires a few more properties to
be added to support that effort.

Lydia understands this.  In fact, she was one of the motivators to have us
encourage us to perform the mapping on both sides, inside Wikidata and
inside Schema.org (both will be done, but first it was deemed necessary for
Wikidata).  In addition, she understands the struggle to bring in more
quality data for Wikidata and to help tool authors and publishers, which in
doing so helps with Goal 1b of WMDE's future plans.  Lydia and a few of us
from Schema.org will be having a Google Hangout to discuss a few more
details this Friday.  The entire effort and comments are being tracked
here:  https://github.com/schemaorg/schemaorg/issues/280

Thad
+ThadGuidry 
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Gerard Meijssen]

Hoi,
Another broken record. I understand how identifiers added to an item make
for the item and an external record to be the same. This is helpful because
it allows comparison of the statements between Wikidata and the external
source.

What is the benefit of Schema.org. Why have it how will it help us.

Or to give you an example. I propose to link red links and wiki links in
all Wikipedias to Wikidata items. It allows for an improved quality in the
Wikipedias in a similar way as the interwiki links brought more quality. It
will also add items to the lists of items that have no article based on
queries from Wikidata (a benefit to projects like women in red). It will
make it easier to add the sources from DBpedia to Wikidata based on the
statements in Wikidata.

So what is the benefit from your proposal? Stating that it will in the
abstract does not give me a warm feeling.
Thanks,
  GerardM

On 13 September 2016 at 22:24, Thad Guidry  wrote:

> The benefit is directly towards WMDE's goals.
>
> Specifically,
> https://meta.wikimedia.org/wiki/Grants:APG/Proposals/
> 2015-2016_round1/Wikimedia_Deutschland_e.V./Proposal_
> form#Financials:_current_funding_period
> Goal 1b: Grow the reach of Wikidata beyond the Wikimedia projects
>
> A Wikidata property = Some external vocabulary property
> A Wikidata property is similar to Some external vocabulary property
> A Wikidata property is considered a parent class to Some external
> vocabulary class  <-- Needs new property for support.
> A Wikidata property is considered a child class to Some external
> vocabulary class
>
> What Schema.org needs now from Wikidata is the addition of a few new
> properties that seem to be missing.  (I sound like a broken record now)
>
> 1. 'external subclass'.
>
> ​DONE.
>
> Let's start there.  I don't even want to drag this discussion further than
> beyond that 1 request, at this point in time.
>
> Thad
> +ThadGuidry 
>
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
>
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Thad Guidry]

All,

Vocabularies have their own definitions already hosted.
There is no need, therefore, to replicate those same definitions in
Wikidata by creating a new Wikidata item (topic / entity) for each external
vocabulary class or subclass or property.

Instead, the best practice is to simply POINT to those external
definitions, such as those in Schema.org, DBPedia.org, MusicBrainz, etc.,
etc.

(sorry, Andra, but unfortunately, your proposal to just create Wikidata
items (recreating a vocabulary inside Wikidata, instead of using Wikidata
properties to point to external URLs) makes Wikidata harder to use, not
easier for itself, or for external partners or vocabularies.  I won't do
this, its not required, its the wrong approach, and gives grief to others
that query Wikidata)

The right solution is to help propose and finish adding some of the missing
'external properties' in Wikidata, then we help the web to help us.
By adding those missing properties in Wikidata, as is done nearly everyday
from what I see.  We help external communities align with Wikidata and
vice-versa.

Andra - let me know once your 'external subclass' is ready for proposal
review.

Thad
+ThadGuidry 
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Gerard Meijssen]

Hoi,
Please explain how this would make a practical difference. We do not need
it unless there is a structural need.

Please describe practical benefits.
Thanks,
  GerardM

On 13 September 2016 at 12:28, Andra Waagmeester  wrote:

> Thad,
>
> I actually don't see how using internal properties would go against
> Wikidata policy. There is the  requirement of notability, "
>
>1.  It fulfills *some structural need*, for example: it is needed to
>make statements made in other items more useful." [1]
>
> I might be wrong, but I would consider creating a new item to describe a
> subclass, fulfilling a structural need.
> Modelling classes and subclasses this way, also makes writing federated
> queries where the WDQS is used in the SERVICE operator easier. I only need
> to consider one wikidata property to bridge Wikidata with external sources,
> and deal with child and parent classes in Wikidata.
>
> Cheers,
>
> Andra
>
>
> [1] https://www.wikidata.org/wiki/Wikidata:Notability
>
>
> On Tue, Sep 13, 2016 at 3:34 AM, Thad Guidry  wrote:
>
>> Andra,
>>
>> That type of powerful expressiveness is certainly doable in Wikidata.
>> To blatantly create properties on a whim by pseudo proxy of using
>> Wikidata items to do the heavy lifting.
>> But that idea is against most of what I have seen in Wikidata
>> documentation, policy, and community best practices say to do.
>>
>> The right way forward is to patiently wait for the new property to exist,
>> and then we can continue.
>> Thank you for drafting the property proposal by the way.  I'll wait for
>> it for review.
>>
>> Here's some examples where we have subclasses under these :
>>
>>   https://www.wikidata.org/wiki/Q4026292  Action
>> should also ideally have all of Schema.org's subclasses of Action
>> that we have like
>> http://schema.org/TravelAction
>>
>>   https://www.wikidata.org/wiki/Q11410  Game
>> should also ideally have the subclass of Videogame
>>   http://schema.org/VideoGame
>>
>> Here's an example of flipping it around and saying that Schema.org can be
>> used as an 'external parent class'
>>   https://www.wikidata.org/wiki/Q7889  Videogame
>> should also ideally have a proeprty on it for 'external parent class'
>> or something similar with the value of
>>   http://schema.org/Game
>>
>> Our full heirarchy is here for your perusal :
>> http://schema.org/docs/full.html
>>
>> Thad
>> +ThadGuidry 
>>
>>
>> ___
>> Wikidata mailing list
>> Wikidata@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikidata
>>
>>
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
>
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Andra Waagmeester]

Thad,

I actually don't see how using internal properties would go against
Wikidata policy. There is the  requirement of notability, "

   1.  It fulfills *some structural need*, for example: it is needed to
   make statements made in other items more useful." [1]

I might be wrong, but I would consider creating a new item to describe a
subclass, fulfilling a structural need.
Modelling classes and subclasses this way, also makes writing federated
queries where the WDQS is used in the SERVICE operator easier. I only need
to consider one wikidata property to bridge Wikidata with external sources,
and deal with child and parent classes in Wikidata.

Cheers,

Andra


[1] https://www.wikidata.org/wiki/Wikidata:Notability


On Tue, Sep 13, 2016 at 3:34 AM, Thad Guidry  wrote:

> Andra,
>
> That type of powerful expressiveness is certainly doable in Wikidata.
> To blatantly create properties on a whim by pseudo proxy of using Wikidata
> items to do the heavy lifting.
> But that idea is against most of what I have seen in Wikidata
> documentation, policy, and community best practices say to do.
>
> The right way forward is to patiently wait for the new property to exist,
> and then we can continue.
> Thank you for drafting the property proposal by the way.  I'll wait for it
> for review.
>
> Here's some examples where we have subclasses under these :
>
>   https://www.wikidata.org/wiki/Q4026292  Action
> should also ideally have all of Schema.org's subclasses of Action that
> we have like
> http://schema.org/TravelAction
>
>   https://www.wikidata.org/wiki/Q11410  Game
> should also ideally have the subclass of Videogame
>   http://schema.org/VideoGame
>
> Here's an example of flipping it around and saying that Schema.org can be
> used as an 'external parent class'
>   https://www.wikidata.org/wiki/Q7889  Videogame
> should also ideally have a proeprty on it for 'external parent class'
> or something similar with the value of
>   http://schema.org/Game
>
> Our full heirarchy is here for your perusal :
> http://schema.org/docs/full.html
>
> Thad
> +ThadGuidry 
>
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
>
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Andrew Gray]

I'm a little confused by this suggestion - surely on Wikidata, the
natural thing is for Game (Q11410) should have the subclass of
Videogame (Q7889), or vice versa, and each of those items should link
out to their equivalents of schema.org/Game / schema.org/VideoGame.

I'm not sure why we then need to add that Game has an external
subclass of schema.org/VideoGame - surely this is just repeating
information we already have? Mirroring all of schema.org, including
its internal relationships, directly within Wikidata seems a bit
excessive.

Am I missing something really obvious here? Nemo's suggestion to just
create a new Wikidata entry (item, topic, Q-number) for any missing
concepts, and then use the existing class properties, seems to solve
the core problem without introducing excessive complexity...

Andrew.

On 13 September 2016 at 02:34, Thad Guidry  wrote:
> Andra,
>
> That type of powerful expressiveness is certainly doable in Wikidata.
> To blatantly create properties on a whim by pseudo proxy of using Wikidata
> items to do the heavy lifting.
> But that idea is against most of what I have seen in Wikidata documentation,
> policy, and community best practices say to do.
>
> The right way forward is to patiently wait for the new property to exist,
> and then we can continue.
> Thank you for drafting the property proposal by the way.  I'll wait for it
> for review.
>
> Here's some examples where we have subclasses under these :
>
>   https://www.wikidata.org/wiki/Q4026292  Action
> should also ideally have all of Schema.org's subclasses of Action that
> we have like
> http://schema.org/TravelAction
>
>   https://www.wikidata.org/wiki/Q11410  Game
> should also ideally have the subclass of Videogame
>   http://schema.org/VideoGame
>
> Here's an example of flipping it around and saying that Schema.org can be
> used as an 'external parent class'
>   https://www.wikidata.org/wiki/Q7889  Videogame
> should also ideally have a proeprty on it for 'external parent class' or
> something similar with the value of
>   http://schema.org/Game
>
> Our full heirarchy is here for your perusal :
> http://schema.org/docs/full.html
>
> Thad
> +ThadGuidry
>
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>



-- 
- Andrew Gray
  andrew.g...@dunelm.org.uk

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

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Thad Guidry]

Andra,

That type of powerful expressiveness is certainly doable in Wikidata.
To blatantly create properties on a whim by pseudo proxy of using Wikidata
items to do the heavy lifting.
But that idea is against most of what I have seen in Wikidata
documentation, policy, and community best practices say to do.

The right way forward is to patiently wait for the new property to exist,
and then we can continue.
Thank you for drafting the property proposal by the way.  I'll wait for it
for review.

Here's some examples where we have subclasses under these :

  https://www.wikidata.org/wiki/Q4026292  Action
should also ideally have all of Schema.org's subclasses of Action that
we have like
http://schema.org/TravelAction

  https://www.wikidata.org/wiki/Q11410  Game
should also ideally have the subclass of Videogame
  http://schema.org/VideoGame

Here's an example of flipping it around and saying that Schema.org can be
used as an 'external parent class'
  https://www.wikidata.org/wiki/Q7889  Videogame
should also ideally have a proeprty on it for 'external parent class'
or something similar with the value of
  http://schema.org/Game

Our full heirarchy is here for your perusal :
http://schema.org/docs/full.html

Thad
+ThadGuidry 
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Andra Waagmeester]

Hi Thad,

   Coincidentally I am drafting an abstract on exactly this topic. So yes I
am keen on getting more of these properties in place. Bare mind that
getting properties proposed can be challenging.  I will draft the proposal
for close match.  Do you have a show case example,  I could use to draft
this proposal. An example where an actual Wikidata item, maps to the one or
more  systems with more granularity.

Regarding the external subclass, why not create an item for the external
subclass in Wikidata and map that with the internal sub class property
(P279) and  then use the property exact match (P2888) to map the new item
to the external class.

Cheers,

Andra

On Mon, Sep 12, 2016 at 6:38 PM, Thad Guidry  wrote:

>
> Hi Andra,
>
> Yes, we'll want to have skos:closeMatch availablebut also...
>
> We need to help with long-tail domain support, and one way to do that is
> support more 'external' properties.  Wikidata doesn't have all the data in
> the world yet, or a full understanding of it...but many times external
> systems do.  So I'd like to see the 'classes' properties of Wikidata to
> also have 'external' support.
>
> Please propose additionally, a 'external subclass' Wikidata property as
> well.
>
> That should do for now.
>
> Thad
> +ThadGuidry 
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
>
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Thad Guidry]

Thanks Federico.  Much appreciated, but...besides creating extra layers
inside of Wikidata just to expose external data correctly

Still, there is a need to have 'external subclass' directly on the parent
class of diet https://www.wikidata.org/wiki/Q474191

One reason is to ease the burden of SPARQL queries for both sides.
Wikidata users/developers and Schema.org

We are tracking all of the work here:
https://github.com/schemaorg/schemaorg/issues/280

SELECT * WHERE {
{?property wdt:P2235 ?extsuper.}
UNION { ?property wdt:P2236 ?extsub. }
UNION { ?property wdt:P1628 ?extequiv. }
UNION { ?property wdt:P1709 ?_equivalent_class. }
FILTER( REGEX(STR(?extequiv), "schema.org") ||
  REGEX(STR(?extsub), "schema.org") ||
  REGEX(STR(?extsuper), "schema.org") ||
  REGEX(STR(?_equivalent_class), "schema.org")
)
}


Thad
+ThadGuidry 
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Federico Leva (Nemo)]

Thad Guidry, 12/09/2016 21:29:

The reason is that our definition in Schema.org is slightly different
than
  which is the biological
definition (a mixture of food sources that sustains a living thing) and
from that derives the nutritional definition, the one Schema.org has,
like a specific diet


Better now?
https://www.wikidata.org/w/index.php?title=Q26869695=375889582=375889390
https://www.wikidata.org/w/index.php?title=Q26869695=375889582=375889390

Do we need a help page on how hypernymy/hyponymy is handled on Wikidata? 
I know it can be confusing.


Nemo

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

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Federico Leva (Nemo)]

Thad Guidry, 12/09/2016 15:46:

Not sure I understand what you mean by 'item' ?  Do you mean a Wikidata
topic ?


I don't know what a "Wikidata topic" is, no such term is found on 
https://www.wikidata.org/wiki/Wikidata:Glossary .


Your example Q474191 already has an "equivalent class" link to 
SchemaOrg, can you make an example of an item (Q-number) and an external 
thingy which you are unable to link? Thanks.


Nemo

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

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Thad Guidry]

Hi Andra,

Yes, we'll want to have skos:closeMatch availablebut also...

We need to help with long-tail domain support, and one way to do that is
support more 'external' properties.  Wikidata doesn't have all the data in
the world yet, or a full understanding of it...but many times external
systems do.  So I'd like to see the 'classes' properties of Wikidata to
also have 'external' support.

Please propose additionally, a 'external subclass' Wikidata property as
well.

That should do for now.

Thad
+ThadGuidry 
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Thad Guidry]

Federico,

Not sure I understand what you mean by 'item' ?  Do you mean a Wikidata
topic ?  We are performing mapping at the Wikidata property level with a
value of URL.

Those Wikidata properties have to exist already for us to accomplish our
work.  Most of them do ,thanks to Denny and TPT... but this 'external
subclass' is also a needed one as well.  We just could not find anything
close to that currently.

Help.


Thad
+ThadGuidry 

On Mon, Sep 12, 2016 at 1:51 AM, Federico Leva (Nemo) 
wrote:

> Thad Guidry, 10/09/2016 17:03:
>
>> Does anyone know if a useful property like 'external subclass' is
>> available to use to help us with our mapping ?
>>
>
> Why can't you create an item for the subclass and link from there?
>
> Nemo
>
> ___
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata

Re: [Wikidata] Request for Property help (Schema.org mapping taskforce)

[Federico Leva (Nemo)]

Thad Guidry, 10/09/2016 17:03:

Does anyone know if a useful property like 'external subclass' is
available to use to help us with our mapping ?


Why can't you create an item for the subclass and link from there?

Nemo

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

[Wikidata] Request for Property help (Schema.org mapping taskforce)

[Thad Guidry]

Hello,

We have a small taskforce effort at Schema.org (myself and a few others)
that have been adding Schema.org mappings into Wikidata to help with
alignment.

However, an issue came up where we did not have a complete 'equivalent
class' between the 2 topics but had the need to say 'external subclass'
instead.  Example: https://www.wikidata.org/wiki/Q474191

We searched and searched through Talk pages and querying Wikidata
properties...but did not find something close to the meaning of 'external
subclass' or a property that expresses 'skos:closeMatch' ?

Does anyone know if a useful property like 'external subclass' is available
to use to help us with our mapping ?

Thad
+ThadGuidry 
___
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata