Talk:LinkedOpenData/Strategy2021

From Meta, a Wikimedia project coordination wiki
This is an archived version of this page, as edited by GreenReaper (talk | contribs) at 13:48, 3 November 2021 (→‎Wikibase Ecosystem: Clarify why it might be necessary for Wikidata to have the property - an observer may not be able to grasp in an automated way that we are talking about the Wikidata Lexeme that is the derivative of this Lexeme unless either a) there is a Wikidata property for "Wikidata Lexeme of X" to combine with; or b) direct references to Lexemes in other wikibases are available.). It may differ significantly from the current version.

Discussing Linked Open Data Strategy 2021

We welcome your considered comments on our strategy statements. (Please sign your comments with ~~~~.)

General

Thank you for creating such a thoughtful and well-organized strategy document! This was a pleasure to read, not just because of the exciting content, but also because of the formatting and sections of the pages themselves. As someone unfamiliar with the overall strategy around Wikidata and Wikibase projects, this gave me a clear understanding of the challenges, goals, and stakeholders. TBurmeister (WMF) (talk) 15:13, 29 October 2021 (UTC)[reply]

Joint Vision

Wikidata

Wikibase Ecosystem

The shared ontologies bit should benefit from forthcoming second-gen federation, because then you can actually say in a schema "I mean this property/item on Wikidata that everyone understands", not "this local thing that is meant to be the same". Though, I'm not entirely sure that referring to foreign items is on the schedule? If not, it should be, otherwise it may be hard to assert that a shared schema refers to the same thing. The same applies to lexemes, as I found when I tried to replicate an at-risk Wiktionary entry with the lexicographical data extension, hoping to reference existing lexemes. This might have benefitted from sitelink parsing in the description, but it'd be better to represent the term's derivation from two Wikidata lexemes with first-class statements (never mind that the Esperanto lexemes in question do not yet exist here - though the ones they probably derive from, Fell and ānus, do). Having a shared ontology/understanding for this may require Wikidata itself to host a property along the lines of "Wikidata lexeme for this item", even though it would not be suitable to use directly in Wikidata, unless that can be understood implicitly because the Lexeme is a first-class reference to a Wikidata Lexeme. A similar issue came up in the WBStack chat when someone asked

Will Wikidata accept a new property called "equivalent Wikidata item"?

in the context of using Wikidata's properties - I suggested P973, but this encodes the intent in the URL; P1709 and P1629 also came up, but are not as useful for items. GreenReaper (talk) 13:21, 3 November 2021 (UTC)[reply]