- → Wikidata:WikiProject Ontology
- → Wikidata:Books and sources about Wikidata
- need to document best practices somewhere (separate namespace, per property?)
- unification vs. separation: do we prefer a few very expressive property or many simple ones; do we want to reuse the same property in different context or create separate ones? (e.g. Wikidata:Property proposal/Person#religious rank)
- how to properly represent and source birth/death dates/locations and multitudes of transliterations? (e.g. Al-Khwarizmi (Q9038))
- negative claims: "x was not born in y" (especially if they contradict another source)
- Wikidata_talk:WikiProject_Informatics#Algorithms:_Instance_of_or_Subclass_of.3F
- class vs instance; instance of vs subclass of vs subtype of vs is-a
- part of, has-a
- Property talk:P1641
- multi-dimensional properties: what is the preferred canonical form?
- collections vs alternatives
- {TCP 20, TCP 21} | {TCP 2220, TCP 2221}
- the current data model allows for different, but isomorphic encodings
- type theory to the rescue?
- in some situations a relational model seems more appropriate
- how to state that a certain list is (in)complete. e.g. tracks of an album.
- "named after" in case of multiple names
Other stuff to think about
edit
- how to deal with ontology mismatches between WP and WD
- or case where a WP wants a different property value
- sourcing
- how to deal with unreliably imported statements
- need to be flagged ("imported from" might be too much maintenance work)
- user interface/API could give a relative view, only displaying/returning reliable/all statements depending on choice of the user
- import/synchronization with external data sources
- best practices for imports done by bots
- conflicts between bot imports and manual curation
- keep imported statements, but mark deprecated?
- example scenario: record is imported from external database, statement gets manually approved on wikidata, record is deleted from external database; what to do on next synchronization pass (delete, keep, mark as deleted, flag as needing attention)?
- keep full provenance data (research on this has been done in the context of SQL)
- language agnostic titles and aliasses
Inherently unsolvable interwiki conflicts
edit