The VIVO Artistic Works ontology extensions were implemented to be compatible with VIVO v1.5 while using some design patterns from the VIVO-ISF v1.6 ontology, notably the vivo:Relationship. See the specifics of the extensions on this wiki or download from GitHub.
The figure below puts the Duke Artistic Works ontology classes (in light blue) in the context of the FaBio, BIBFRAME, Bibontology, and VIVO-ISF ontologies, focusing on classes most likely to be considered for representing artistic works but including most of the additional document types found in each ontology.
Issues to discuss:
- Some of the Artistic Works classes are performances (currently considered a subclass of Event in VIVO-ISF) while others are more traditional artistic media, designs for performances, or musical scores – some of which might be subsumed under information content entities or the more specific document class, and some perhaps not.
- It's not clear whether the duke:RepertoirePortfolio class is a singular thing or a collection
- There could easily be more types of artistic works – Novel, Play, Poem, and ShortStory come to mind from FaBio.
- The distinctions among the Functional Requirements for Bibliographic Records (FRBR) Works vs. Expresssions vs. Manifestations vs. Items vs. the simpler Instance and Work in BIBFRAME are the subject of many active discussions in the library community now. FaBio is an ontology designed to encompass the FRBR distinctions while focusing many of its types at the Expression level, leaving the notion of Work as the more abstract intellectual core than BIBFRAME does, but offering Expression classes that align fairly well with Bibo, VIVO-ISF, and the Duke extensions.
- Early versions of the Duke humanities work referenced a long list of roles as well – were these phased out in favor of an Artistic Relationship (not shown here)?
See also a blog post on Comparison of BIBO and Fabio.
Download the .vue file or get the free Vue software
