Open rohitadeshmukh13 opened 3 months ago
From our discussion in the DRK IM UC3 meeting yesterday: For representing Genre ENUMs, we can investigate the use of the following by the Library of Congress:
Regarding the production type (and event type): Wikidata already has entries for pretty much all of the types we want to consider, for now. I'm not sure if Wikidata entries are enough for your purposes, but here is a list:
Some of these also have a GND ID, but not all of them, as far as I can tell.
The only difference to our current UC3 data model is that there is no single entry for a "first performance" (Erstaufführung), but three more specific ones:
Regarding a vocabulary for (theatric) genres: I had a look at the Library of Congress links you provided, and tried to find some of the terms/genre we picked for our list of enum values. Some of them I was able to find in the LoC vocabulary, but especially with some of the more specific terms, I was not. I also compared this to what is available in the GND and that seems to cover more of the terms we are interested in.
To show what I mean, I put together a list of genre terms that might be interesting for us and that have an entry in the GND but apparently NOT in the Library of Congress database. At least as far as I could find:
In some cases, this might also be related to translation issues, i.e. I might not know the equivalent english term for a genre that exists in German. Also note that I'm not saying that the GND includes all possible genre terms we might be interested in (it doesn't), but so far it seems a better source compared to the Library of Congress information.
@rohitadeshmukh13 To clarify, here are the values for eventType
vs productionType
:
eventType:
productionType:
For the Language Enumeration, we can use the following ontology:
# This ontology defines a Language enumeration for UC3.
# It uses ISO 639-1 language codes and currently supports English and German.
# The ontology is extensible and includes instructions for adding new languages.
:Language a owl:Class ;
owl:oneOf ( :en :de ) ;
rdfs:comment "Enumeration of supported languages in the system using ISO 639-1 language codes." ;
rdfs:seeAlso <https://www.loc.gov/standards/iso639-2/php/code_list.php> ;
dc:source "ISO 639-1" ;
skos:prefLabel "Language"@en, "Sprache"@de ;
skos:note """
This enumeration currently includes only English (en) and German (de).
When extending the system to support additional languages:
1. Add new language instances using their ISO 639-1 two-letter codes.
2. Update the owl:oneOf list to include the new language instances.
3. Ensure that all application logic and user interfaces support the newly added languages.
4. Consider implementing a more flexible language handling system if the number of supported languages grows significantly.
Example of adding French:
:fr a :Language ;
skos:prefLabel "French"@en, "Français"@fr ;
skos:notation "fr" .
Then update the oneOf list:
owl:oneOf ( :en :de :fr )
""" .
:en a :Language ;
skos:prefLabel "English"@en, "Englisch"@de ;
skos:notation "en" .
:de a :Language ;
skos:prefLabel "German"@en, "Deutsch"@de ;
skos:notation "de" .
Hi @peret, I've created RDF Turtle representations of controlled vocabularies for Theatrical Genres, Theatrical Production Types, and Theatrical Event Types. Since our starting point was only the term names, I've added translations and descriptions based on my understanding, referring to various online sources. Therefore, I would greatly appreciate it if you could review the values of the following properties:
rdfs:label
skos:altLabel
rdfs:comment
skos:exactMatch
: According to the SKOS documentation, this property is used to link two concepts with a high degree of confidence, indicating they can be used interchangeably across a wide range of information retrieval applications. If the match is not exact but still close, the skos:closeMatch
property should be used, which links two concepts that are sufficiently similar to be used interchangeably in some information retrieval contexts.rdfs:seeAlso
: To ensure that the linked resource provides additional relevant information about our resource.Please feel free to make any necessary changes directly in the files and push them to the uc3
branch, or provide the updates via comments—whichever you prefer. Thank you.
Thanks @rohitadeshmukh13. I had a look and created a PR with my changes, so y'all have a chance to double-check.
Two additional things I want to mention/ask:
Opera
, Operetta
, and Musical
are forms of Music Theater
. Would this vocabulary definition be the place to define these relationships? Are you already planning to add that? Would that be necessary or useful in the context of the Information Model?
Description
Example of how controlled vocabularies can be used to represent ENUMs
RESULTS: Identified controlled vocabularies for UC3