Wikidata:Property proposal/WordLift ID

From Wikidata
Jump to navigation Jump to search

WordLift ID

[edit]

Originally proposed at Wikidata:Property proposal/Authority control

   Done: WordLift URL (P6363) (Talk and documentation)

Motivation

[edit]

WordLift ID refers to 5 stars linked data with permanent URIs publicly available online. WordLift's datasets are also published on the LOD Cloud and interlinked with other public datasets. Devbug (talk) 10:01, 6 December 2018 (UTC)[reply]

Discussion

[edit]
@ArthurPSmith: I do think, however, that we should consider striking the votes of the two people immediately above your initial comment and the three votes right below David's support vote for being socks. Mahir256 (talk) 16:31, 12 December 2018 (UTC)[reply]
@ArthurPSmith: WordLift (Q31998763) started in 2011 within the IKS project of the European Framework Program 7 (FP7). It officially opened to the public in 2017. WordLift is the only solution for WordPress (Q13166) (as far as I know) that fully complies with the Linked data principles and the 5 stars of Linked data. In fact datasets are listed in the LOD Cloud diagram. Entity management is decentralized and happens within WordPress (Q13166), structured data is pushed to Apache Marmotta. WordLift provides also interlinking with other datasets (including but not limited to Wikidata (Q2013), DBpedia (Q465), GeoNames (Q830106), ..., by means of owl:sameAs and schema:sameAs) which is the 5th rule of Linked data "Link your data to other people's data to provide context" (and a requirement to be listed among the 1,231 datasets of the LOD Cloud). --Devbug (talk) 17:12, 12 December 2018 (UTC)[reply]
@Devbug: Not sure what you mean by "deceentralized" here. There's one Marmotta installation that WordLift is using, right? So every valid URI must be listed in that central location? Anyway, it sounds like (given the "owl:sameAs" comment) you must allow multiple URI's for the same entity, so it's not really an ID either, is it? ArthurPSmith (talk) 20:07, 12 December 2018 (UTC)[reply]
@ArthurPSmith: By decentralized I mean that the actual content is managed and stored in various WordPress instances as semi-structured data (title, content, meta fields). Because WordPress is unable to provide a performant and effective triple store, we copy the contents in the form of triples to Marmotta (which may provide also additional features, e.g. SPARQL, ldpath). I am not sure I understand the question about the ID, I'll try to give an example: http://open.salzburgerland.com/de/entity/salzburgerland is the ID for Salzburgerland like Salzburg (Q43325) in Wikidata, 2766823 in GeoNames, http://dbpedia.org/resource/Salzburg_(state) in DBpedia. Wikidata uses GeoNames ID (P1566) to state GeoNames ID and GeoNames uses the pseudo language code "wkdt" to state Wikidata's QID. --Devbug (talk) 20:49, 12 December 2018 (UTC)[reply]
@Devbug: Sorry, "not an ID" is not the right way to express what I was thinking. But just to be clear, for your Salzburg (Q43325) example there would be at least 2 (salzburgland and dbpedia) and maybe 3 (including geonames) or more (?) correct values for this proposed "WordLift ID"? ArthurPSmith (talk) 20:55, 12 December 2018 (UTC)[reply]
@ArthurPSmith: Ah, no, the correct value for "WordLift ID" would be http://open.salzburgerland.com/de/entity/salzburgerland just like 2766823 is for GeoNames ID (P1566), Salzburg-state is for Quora topic ID (P3417), etc. --Devbug (talk) 21:03, 12 December 2018 (UTC)[reply]
And the central service is deciding what those special URI's are, ok. Is there any mechanism to confirm (a lookup service?) that somebody has set the right URI? We might want to treat this as an external ID with a formatter URL if there's something that works for that... ArthurPSmith (talk) 23:28, 12 December 2018 (UTC)[reply]
@ArthurPSmith: Currently there's no lookup service, but we could provide several, e.g. one that validates a URI, one that autocompletes a URI, ... can you point me to examples of other lookup services? Initially I looked at the formatter, I am not sure it's fit, because the hostname part of the URI may be variable, i.e. by default we use http://data.wordlift.io/datasetname as base URI, however publishers can provide their own custom domain, for instance http://open.salzburgerland.com, http://data.thenextweb.com, http://dati.greenpeace.it/ and so forth. We can also prepopulate and keep the ID in sync from WordLift's side using Wikidata API. --Devbug (talk) 07:20, 13 December 2018 (UTC)[reply]
@ArthurPSmith: On behalf of Wikidata:Property_proposal/Generic should I set status=ready on the proposal ? --Devbug (talk) 09:56, 13 December 2018 (UTC)[reply]
@ArthurPSmith: Can you please point me to an example lookup service (or another property which makes use of one), so that I can review and learn the API and the best practices? --Devbug (talk) 11:28, 28 December 2018 (UTC)[reply]
@Jura: Which property are you referring to? Can you make an example of data that would be duplicated? --Devbug (talk) 20:17, 13 December 2018 (UTC)[reply]
@Jura: For example Salzburger Bauernherbst provides a description, the list of performers, the start and end dates and the relations with other entities that aren't present in Wikidata. --Devbug (talk) 15:46, 15 December 2018 (UTC)[reply]

@ديفيد عادل وهبة خليل 2, Gencuo, Popper89, ArthurPSmith, Multichill, Jaijal: @Devbug, Domus.aurea999, Pigsonthewing, Mahir256, Jura1: ✓ Done: WordLift URL (P6363). − Pintoch (talk) 15:56, 14 January 2019 (UTC)[reply]