Re: [Wikidata-l] OpenStreetMap + Wikidata for light houses

t; On Thu, Apr 23, 2015 at 10:16 AM, Edward Betts wrote: > >> Thad Guidry wrote: >> > I helped with the Lighthouses schema in Freebase. >> > >> > Some of which is based on List of Lights (NGA) USA. >> > >> > I have DB conversion data for

Re: [Wikidata-l] World's largest cities with a female mayor :-)

BTW, the Freebase ingestion later this summer should help fill a few of those holes in population and other statistics. We had US Census, World Bank, and UN Data as our primary data sources for any /statistics/ of a City/Town/Village. Here's Houston - https://www.freebase.com/m/03l2n#/location/st

Re: [Wikidata-l] Wikidata-Freebase mappings

Nice work Haklae and team ! And thanks for making this investment and sharing it publicly. This will help everyone involved as migration progresses forward. Thanks again, Thad +ThadGuidry On Wed, Apr 8, 2015 at 8:03 AM, Kim Haklae wrote: > Hi all, > > I a

Re: [Wikidata-l] External identifiers vs. Wikidata-internal links & data

statement (instance of:wikidata database index property) > instead of trying to do this with the English language label as it is > easier to localise statement s. > On 4 Apr 2015 17:23, "Helder ." wrote: > >> On Sat, Apr 4, 2015 at 5:19 AM, Smolenski Nikola >> wrote: &

Re: [Wikidata-l] External identifiers vs. Wikidata-internal links & data

Re-reading... Erik, I think you mean that the display itself for instance on this page: https://www.wikidata.org/wiki/Q42 would be more useful if all Identifiers were pushed down to the bottom half or different section, for instance, and keeping descriptor properties on the upper half ? (instead

Re: [Wikidata-l] External identifiers vs. Wikidata-internal links & data

Why do you have to get lost in them ? Most already have the phrase "ID" or "Identifier" in their naming convention. So perhaps a better approach would be to standardize the naming convention used for External Identifiers and make it a best practice and golden rule during property creation and vot

[Wikidata-l] Mapping Wikidata properties to Freebase properties

Experiment for tonight: Figure out how the hell to map 1 of my Freebase base types...to a wikidata SOMETHING. https://www.wikidata.org/wiki/Q1427887 is the same as https://www.freebase.com/base/beefbase/meat_product?schema= and I noted on Q1427887 that the Freebase identifier is /m/0gxp3zs GRE

Re: [Wikidata-l] next Wikidata office hour

Hi Lydia, When Tpt_ goes over to Google in the summer, please pass on my info to him, to reach out to me about any questions the team may have about some of my /base's in Freebase. Many have found them useful, and the data comes mostly from government sources already. I am sure that there are oth

Re: [Wikidata-l] FAQ for Freebase users

Overall, that's a pretty good summary FAQ, Lydia. Good Job putting that together and thanks ! Thad +ThadGuidry 2015-03-20 11:57 GMT-05:00 Lydia Pintscher : > Hey folks :) > > At the end of the month Freebase is going read-only and I expect we'll > get an inf

Re: [Wikidata-l] OpenStreetMap + Wikidata

Think... BIGGER. Jo has the right idea... Linked Data. It sounds to me like the right way forward for domain specific interest data (like OSM) ...is, Instead of 1 source of data (Wikidata)...and throwing domain specific interest data into Wikidata (not all data needs to live inside it). Just us

Re: [Wikidata-l] OpenStreetMap + Wikidata for light houses

Markus, Here's the basic schema that we put together in Freebase that is semi-populated with data now. Whomever whats to build the structure for Wikidata can just setup like it: http://www.freebase.com/architecture/lighthouse?schema=&lang=en Thad +ThadGuidry

Re: [Wikidata-l] OpenStreetMap + Wikidata for light houses

I helped with the Lighthouses schema in Freebase. Some of which is based on List of Lights (NGA) USA. I have DB conversion data for the PDFs...just never got around to loading them all in. Let me know if I can help. Thad +ThadGuidry On Tue, Mar 10, 2015 at

[Wikidata-l] Derived Properties (Computed Properties) or Metaschema ?

Freebase originally had 2 modes. View and Edit. And then changed to only an Edit mode (where some properties were no longer hidden) Wikidata as far as I know only has Edit (All properties are shown in the UI) Derived properties might work, but only in a "View mode". Or only if Derived properti

Re: [Wikidata-l] Freebase's incompatible types and Property description permissions

Back to the original discussion...and summary... Anyways, thanks to all for summing up the current state of the "Properties on properties" which is the 1st step for the Rules enforcement and that will offer similar capabilities that Freebase had with Incompatible Types. Also I feel more comfortab

Re: [Wikidata-l] Relating Wikidata entities to external URIs (was: Disambiguating property ...)

Thanks for explaining Markus. The advantage of avoiding "equivalentProperty" in favour of "subPropertyOfExternalProperty" > (and similarly for classes) is also that our definition can be more > specific than the one used for the external property/class. So we can > relate our data to multiple ext

Re: [Wikidata-l] Disambiguating property [was: Freebase like API with an OUTPUT feature}

https://www.wikidata.org/wiki/Property:P279 aka "the superclass" ... seems to have an equivalent property that refers to http://www.w3.org/2000/01/rdf-schema#subClassOf ??? dunno. Thad +ThadGuidry ___ Wikidata-l ma

Re: [Wikidata-l] [Mediawiki-api] Freebase like API with an OUTPUT feature ?

So Lydia, Your saying that if I see https://www.wikidata.org/wiki/Q18614948 as a property on another Property... then that is similar to the Freebase "disambiguating" flag ? In Freebase, we have just one flag but that is not the case here, correct ? Wikidata has (or might have) several such

Re: [Wikidata-l] Freebase's incompatible types and Property description permissions

Markus, Devils in the details. =) You used the English word "associated". That's great. Then I would propose to expand the definition of P17 just a bit to add that. P17 Country - sovereign state of this item ... to ... sovereign state ASSOCIATED with this item Then you save the world. =) Tho

Re: [Wikidata-l] Freebase's incompatible types and Property description permissions

Hi Marcus! Yes, you and I are on the same page. Yes, I know about the Property-first view of WIkidata. No quibbles. But there is still an issue with Assumptions for "Country" P17 being used for an instance of Band...so let's clarify this... So, I guess things are fuzzy, because I do not jump t

Re: [Wikidata-l] Freebase's incompatible types and Property description permissions

On Thu, Jan 8, 2015 at 12:17 PM, Federico Leva (Nemo) wrote: > Thad Guidry, 08/01/2015 18:58: > >> Unless the P17 Country property had an expanded definition of "sovereign >> state (or originating sovereign state) of this item" >> > > That's more l

[Wikidata-l] Freebase's incompatible types and Property description permissions

Freebase has mutexes that store incompatible type information. For instance, in Wikidata I noticed on the U2 band topic, that they have statements of: P17 Country - sovereign state of this item. P740 Location of formation - location where a group or organization was formed. In Freebase we have b

Re: [Wikidata-l] [Mediawiki-api] Freebase like API with an OUTPUT feature ?

Yes I did try wbsearchentities, and your right, it returns more via a search operator. The problem with wbsearchentities is that it is limited and cannot additionally pipe output for the claims information (ideally important claims only, disambiguating claims/properties) Thad +ThadGuidry

Re: [Wikidata-l] [Mediawiki-api] Freebase like API with an OUTPUT feature ?

Hi Lydia, It's more than that. I can get labels just fine with &props=labels Ideally there were be a Number 3 a reconcile service, or an API that can be USED as a reconcile service. Given a search string of "Paris", let's say... 1. Return some disambiguating properties and their labels and