---
# System prepended metadata

title: 'openWEMI meeting April 26, 2023'
tags: [openwemi]

---

# openWEMI meeting April 26, 2023
###### tags: `openwemi`

Hackmd link: https://hackmd.io/4XuVrW4lQ7uQHz1hLBYw3g

Join Zoom Meeting: 
https://us02web.zoom.us/j/89101555665?pwd=QW83cDFpQ1pETjB6YUNQOTFiQmZjUT09

## Times:
* San Francisco (USA – California)	 9:00:00	PDT	UTC-7 hours
* New York (USA – New York)	 12:00:00	EDT	UTC-4 hours
* London (United Kingdom – England)	17:00:00	GMT	UTC
* Berlin (Germany – Berlin)	18:00:00	CET	UTC+1 hour
* Corresponding UTC (GMT)	 16:00:00

[Check time](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20230426T1600) in your time zone

## Participants
* Karen, Sean, Ross, Daniel

## Agenda

* Document started: https://hackmd.io/JNqY7NDzTCCHfQ21pz5d3g?view 
* expresses or expressionOf? https://github.com/dcmi/openwemi/issues/25
* relatedEndeavor https://github.com/dcmi/openwemi/issues/26
* defining Endeavor https://github.com/dcmi/openwemi/issues/27
*  Transitivity https://github.com/dcmi/openwemi/issues/24

### Defining Endeavor

Daniel: some ambiguity between work and endeavor
kc: mainly a structural function
Endeavor is not a superWork, but is a superclass to all of WEMI entities

AGREED: "A creation"

ACTION: kc will redo diagram including Endeavor

### relatedEndeavor

kc: we allow a work of work (etc.) but we don't go further than that
If we add these to all entities that fills out the general relationships
Without these, there would be a gap as people define entity/same-entity relationships

Ross: could commonX help us out here? 2 expressions of the same work would have a common work
It all gets more complex when you think about serials - because of the whole/part relationships. Part of a manifestation is still a manifestation? And parts could have their own Endeavor

Daniel: there is a work relationship in special issues because there is a creative element to the selection by the editor

kc: some descriptions will be more complex graphs than simply WEMI - Also, people can add other high-level entities, not just limited to WEMI

Ross: are the current relationships (.e.g expresses) also "relatedX"? 
(Aside: begs the question of defining a general "Related", but that might be going too far.)

ACTION: kc will start a diagram on draw.io, trying out a journal + journal article

ACTION: Ross will add "relatedX" to ttl file

### Noun or verb?

AGREED: verb

Ross: because predicate is a verb

Daniel: with noun you need to add something, like "is"

Sean: if you want the inverse you can have "expressedBy" "instantiatedBy"

kc: we can discuss inverse next week; having both properties means you have to know which one to search; a query can look at the reverse

Ross: higher order classes shouldn't have to have knowledge of the lower - a Work shouldn't have to know what Expressions express it. It doesn't make sense that an Expression would know its manifestations, but a manifestation is derived from an expression, so it has that knowledge.

kc: your graph does not have to be complete. You can create a manifestation without anything else, whether or not you add more information later. FRBR required completeness
