OntologyDesign sprint: iteration 1 (places)

[jonnybluesman]

As @enridaga suggested, at the current iteration we are focusing on basic concepts + those related to places. Together with @andreamust and @valecarriero, we have filtered the place-related "fields" (from our list [1]) and tried to contextualise them with the current (and the potential) design of the ontology modules.

In sum, these are the data types related to places, with the corresponding entries in [1]:

1. Place mentioned / subject of the composition, e.g. "Penny Lane, Liverpool, UK" in "Penny Lane" by The Beatles (10);
2. Facts / curiosities related to the latter, e.g. "In Penny Lane, there is a barber showing photographs..." (11);
3. Country of each of the artists of a composition, e.g. "GB" (45);
4. Geographical area where each artist (of a composition) has started their career (46);
5. Recording place (studio, live venue) of the recording, e.g. "Abbey Road Studios: Studio 2" (65);
6. Address of the recording place (related to the latter), e.g. "3 Abbey Road, St John's Wood, London" (66);
7. Places where the release (album) was "made official", e.g. US, EU (75).

Please note that this is more complex from a technical point of view, as MusicBrainz is very granular and provides information at different levels. Indeed, a musical work (the composition) can have N recordings, each of which can be present in M releases. For data collection, we tried to simplify this step, so we can assume a 1:1:1 relationship for the moment.

Anyways, and more importantly, we were wondering if all these data types should be modelled in our ontology modules.

[1] https://liveunibo.sharepoint.com/:x:/r/sites/polifonia/Shared%20Documents/WP6/AI%26Music@Sonar2021/datasets/overview.xlsx?d=w352ea4d8aefe40cbb080d1c291c52998&csf=1&web=1&e=V2BAIm

[enridaga]

Anyways, and more importantly, we were wondering if all these data types should be modelled in our ontology modules.
I think they all should be modelled, not sure if the modelling should be done with typing, probably not. But this is a question for the ontology engineering team.

An important question is which ones of these can be added to the datasets for the demo ASAP. (See also #10)

[jonnybluesman]

The datasets where all these fields come from are already in the datasets branch, but we can re-organise the structure of the repository to make it more readable and easy to navigate. From an analysis of the current data, we can conclude that:

• Places 1 and 2 are only available for 5 tracks from The Beatles and just 1 from Queen.
• Places 3 and 4 are available for every single artist that contributed to the composition (generally available).
• Places 5 and 6 are related to the recording and are given for "mixed at" and "recording at" (generally available).
• Place 7 is not very informative apparently (e.g. EU, XE are too general) and is associated to all the possible releases (albums) where the recording appears.

In sum, we have all the data but we can rely mostly on 3, 4, 5, 6. As for the ontology modules, we are constantly in contact with @valecarriero, so our concern in this issue was actually shared.

[jonnybluesman]

Some modelling progress from the OD team curating the musical performance module (@valecarriero, @jonnybluesman, @andreamust). This partial model generalises some key parts of MusicBrainz (where we get most of the data), is still aligned with our competency questions, and addresses Places 5, and 6 (see list above).

[valecarriero]

Draft addressing Place 4 (see list above)

[valecarriero]

Draft addressing Place 3 (see list above)

[valecarriero]

Please note: all object properties in these diagrams will have their inverse.

[valecarriero]

Draft addressing Place 4 (see list above)

[update after 23/09/2021 WP2 meeting]
Considering that the field we are modelling (artist_start) is ambiguous and not very specific (e.g. London for Queen as the place where the band was formed, Pinner for Elton John as the place where he was born and started to play/its musical activity), we will model this as a binary relation, and then we will have a more complex model if we will have more data e.g. about the timeline (start, end, steps, etc.)

[valecarriero]

Some modelling progress from the OD team curating the musical performance module (@valecarriero, @jonnybluesman, @andreamust). This partial model generalises some key parts of MusicBrainz (where we get most of the data), is still aligned with our competency questions, and addresses Places 5, and 6 (see list above).

[update]

[valecarriero]

model for the coordinates (basically, based on https://w3id.org/italia/onto/CLV/)

[ccolonna]

As suggested by @vpresutti I'm gonna add to the KG production rules some binary relations for places from the song to the place, see this related issue:

• Add binary relations to places KG_data_transformation#24

We need to simplify query to select important examples for the demo!
The model/ontology shall be reviewed then