Declaring a "Show"/«Spectacle» class in Artsdata #133
Replies: 3 comments 1 reply
-
Candidate classes for integrationThere are relatively few specialized classes matching the "Show" concept in RDF ontologies. Mid-Level Ontology for the Performing Artsmilopa:PERFORMANCE_WORK This class is a close (if not exact) match to the concepts used in Canadian industry platforms. However, I can think of several reasons that make it an ill-suited candidate for integration into Artsdata:
Functional Requirements for Bibliographic Records object oriented (FRBRoo) / Library Reference Material (LRMoo)FRBRoo is an extension of FRBR and is built on the same core Work-Expression-Manifestation-Item (WEMI) stack. FRBRoo was notably designed to represent endeavours of the performing arts and included three specialized classes. However, two classes that could have otherwise been useful to Artsdata have been deprecated by LRMoo, the latest harmonization effort led by IFLA.
One of FRBRoo's valuable contribution is the description of the relationships between performing arts works and other works that are 'incorporated' in them (see this paper), which is particularly relevant in the performing arts (any new performance work of Michel Tremblay's Les belles soeurs The deprecation of these class is both a challenge and an opportunity: we have the leisure of defining our own class subsuming F20 Performance Work and F25 Performance Plan, while representing this new class formally in relationship to FRBRoo and CIDOC-CRM classes and properties (in a similar fashion as the DOREMUS ontology). Wikidatawd:Q43099500 (performing arts production / production des arts de la scène) wd:Q17538722 (performance work / œuvre scénique) wd:Q43099500 was initially declared in the Swiss Model for the Performing Arts (SPA-E9 Performing Arts Production) and later implemented in Wikidata. This concept is ideally suited at describing works in the context of archives. However, since it conflates aspects of performances, we could run into issues if we integrated it into Artsdata. wd:Q17538722 was created as an exact match to F20 Performance Work. It could be a good short term solution, while a more formal representation is defined. There are no equivalent Wikidata classes to F25 Performance Plan or F2 Expression. Music Ontologymo:Show While the label suggests a "Show" concept, the class is defined and modeled as an event series: it is a subclass of event:Event, not a subclass of a work-related concept. |
Beta Was this translation helpful? Give feedback.
-
Attributes of the "Show" class"Show" attributes in Arts Touring Connector
"Show" attribute-value pairs that could be inherited to Event entitiesOne of the anticipated benefits of integrating Show data into Artsdata is ability to infer a lot of triples to Event entities. Here are common attributes of the "Show" class along with a proposed inheritance schema in Schema:
Other key attributesHere are some other fundamental attributes of the "Show" class in different data models (along with notes and sources):
|
Beta Was this translation helpful? Give feedback.
-
|
L'Association québécoise des marionnettistes (Quebec's Puppetry Association) is the province's section of
Here are the attributes for our œuvre-spectacle concept (in french)
|
Beta Was this translation helpful? Give feedback.
-
|
Merci beaucoup ! |
Beta Was this translation helpful? Give feedback.
-
Background
CAPACOA commissioned a report Enhancing and Connecting Performing Arts Information Systems. This report found that four Canadian industry platforms have a similar concept designating "works intended to be performed on stage". This concept (or "class" in ontology terminology) is commonly named "show" in the industry. In the performing arts value chain, there is a "touring market", in which instances of shows are offered by creators/producers (or their representative) to presenting organizations who purchase the right of presenting one or several performances of the show. This business process is supported in various ways in each of these industry platforms:
Similar classes also exists in two conceptual models developed in Canada.
Datascene – Référentiel des métadonnées descriptives du spectacle:
Mid-Level Ontology for the Performing Arts:
Authors of the report Enhancing and Connecting Performing Arts Information Systems performed an ontology alignment exercise and concluded that the above classes (except MiLOPA:Performance_Work, which was out of scope for the project) were exact matches. Authors however found a relatively small number of common attributes for the class:
Specific use case
The Arts Touring Connector (ATC) is a platform designed to facilitate the planning of Show tours. This process, known as "block programming", is carried out by presenting organizations and the networks that support them. Two key classes closely associated with the Tour concept in the ATC data model are: Artist and Show. ATC would like their users to be able to autocomplete Artist and Show names against Artsdata entities and, when a match is found by the user, to import the matching data record.
Artsdata does currently not have a dedicated class for the Show concept. The closest class in Artsdata is schema:CreativeWork, which could be deemed superclass to the Show concept.
Solution
Artsdata should either integrate an existing class or else declare a new class. Then, this class should be tested with entities from Wikidata or from one of the industry platforms.
Beta Was this translation helpful? Give feedback.
All reactions