Re: Emacsconf 2021 presentations in Wikidata

[Rodrigo Morales]

I've been thinking about this and I think we shouldn't use neither no. 1
nor no. 2. This because if our goal is to make the recordings more
discoverable by Wikimedia Commons users, we need to add structured data
in a way that other similar items (conference presentations) have
them. This implies not using complex schemas (no. 2) just because it
looks more organized.

A simpler schema would be
<https://commons.wikimedia.org/wiki/File:Wikidata_properties_for_an_EmacsConf_presentation.png>

In Commons, there are no guidelines for adding structured data to
conference presentations, but I've started one
<https://commons.wikimedia.org/wiki/Commons:Structured_data/Modeling/Conference_talks>
. I've added the diagram shown above in that page as an example. You can
also contribute by editing the page to propose ideas, ask questions,
etc.

On Thu, 16 Dec 2021 at 17:26, Rodrigo Morales <moralesrodrigo1100@gmail.com> wrote:

Table of Contents
_________________

1. Introduction
2. Ontology no. 1
3. Ontology no. 2
4. Personal thoughts


1 Introduction
==============

  Hello everyone, I'm planning to add the presentations of EmacsConf
  2021 to Wikidata in order for them to be more discoverable by people.

  I've thought of two [ontologies]. They are presented below.


[ontologies]
<https://en.wikipedia.org/wiki/Ontology_(information_science)>


2 Ontology no. 1
================

<https://upload.wikimedia.org/wikipedia/commons/3/3e/Ontology_for_presentations_at_EmacsConf_2021.png>

  Advantages

  + The only items that need to be created are the presentations. In
    ontology no. 2, additional items need to be created. As you can see
    in the image of ontology no. 2, these are the additional items:
    "EmacsConf 2021 presentation", "Presentation at day one of EmacsConf
    2021" and "Presentation at day two of EmacsConf 2021".

  Disadvantages

  + There's no concept of day one and day two. If someone wants to get
    all the presentatinos of day one, he would need to get all the
    presentations whose "point in time" is that of day one.
  + If, for some reason, the date of a given conference day is wrongly
    inserted, the date needs to be changed in all those presentations
    with the wrong date.


3 Ontology no. 2
================

<https://upload.wikimedia.org/wikipedia/commons/3/32/Ontology_for_presentations_at_EmacsConf_2021_with_level_of_hierarchies.png>

  Advantages

  + If, for some reason, the date of a given conference day is wrongly
    inserted, the date needs to be changed in a single place.
  + The level of abstraction allow simple queries to retrieve
    information. For example, if someone wants to get all the
    presentations in day two, he only needs to get the instances of the
    class "Presentation at day two of EmacsConf 2021" while in the other
    approach, he would need to find the date of day two and query items
    that are "instance of" presentations and that are "part of"
    "EmacsConf 2021" and whose "point in time" is that of day two.

  Disadvantages

  + The level of granularity implies that more items than ontology no. 1
    need to be created.


4 Personal thoughts
===================

  Personally, I prefer ontology no. 2.

  If any of you have suggestions/comments for improving this, please let
  me know since I'll start adding this to Wikidata this weekend.