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

Hackmd link: https://hackmd.io/lZ_ptRW6QLC8qjQ_qVEAbA

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=20230405T1600) in your time zone

## Previous meeting
* [April 12] (no minutes)

## Participants
* Karen, Sean

## Agenda

* Questions on interative-ness of entities [issue 23](https://github.com/dcmi/openwemi/issues/23)
* Think through examples - what works?
* Structure vs semantics - can we have both?
* [Ballads](https://github.com/dcmi/openwemi/tree/main/examples/Bodleian%20Ballads)
* [Comics](https://github.com/dcmi/openwemi/tree/main/examples/comics)
* [Comics using classes](https://github.com/dcmi/openwemi/tree/main/examples/usingClasses)

## Minutes
Lots of talk about w/w etc. relationships. kc added them to the diagram

Sean: Mainly we don't want to exclude them; do we need an explicit relationship?

kc: will need to add ranges? but we have no predicate for Work. And FRBR does not provide one.

kc: FRBR has many other relationships between entities, like "translation of" or "based on". Where would those fit in our diagram?

kc: CommonWork is not the same as "related work" - in latter they are not the same work

kc: Do we want a very general "related" over all of the relationships? But "related" is too general.

Sean: inverse properties?

**Examples**
kc's comics: change "comics:" to "cvo:"

sean: in comics translations can be their own works because they can be "interpretive". In cvo no expression attributes but expressions come through the manifestations. Things like artwork can be expressions or works on their own. Provide alignment to schema.org in vocabulary.

kc: using subclasses and domains, you don't need to think in terms of WEMI - you can just think in terms of the properties that make sense. RDA requires catalogers to decide which entity they are describing.