###### tags: `Monthly Community Meetings`

# 2021-11-11 Eiffel monthly community meeting

## Attendees

- Emil Bäckmark
- Magnus Bäck
- Mattias Linnér
- Sven Selberg

## Agenda
- [Better linking from ActT to SCC/SCS](https://github.com/eiffel-community/eiffel/issues/246)
- [Extract "meta" as a type](https://github.com/eiffel-community/eiffel/issues/256)

### Actions
- Emil: Ask JSON schema knowledgable person to review the meta extraction PR.
- Magnus: Continue examining consequences for JSON validation code.
- Magnus: Write script for creating single-file schema files.
- Mattias: Add comment to [github.com/eiffel-community/eiffel#246](https://github.com/eiffel-community/eiffel/issues/246) about potential new TRIGGERED_BY link type.

### Issues discussed

| Item | Action |
| ---- | ------ |
| [Better linking from ActT to SCC/SCS](https://github.com/eiffel-community/eiffel/issues/246) | We discussed whether CAUSE links should be "transitive", i.e. if a retriggered activity should include the CAUSE link of the original activity or if clients should have to follow links to reach the original activity and its CAUSE link. If so, which link types should be followed? A related discussion was the general meaning of a CAUSE link. Does that link necessarily describe the actual trigger of an activity or can it describe the underlying cause? For example, if an activity that failed is retriggered the immediate trigger reason might be the ActF signaling the failure but the cause could be the SCC/SCS that started the original activity. |
| [Extract "meta" as a type](https://github.com/eiffel-community/eiffel/issues/256) | Generally positive but we should check the PR against various JSON schema libraries to make sure we're doing things correctly. Mattias (?) also suggested that we could create additional self-contained single-file schemas that would be structurally compatible with the current files. This transform could be made with a script. |