# forge-fed-poc

[<img src="https://domaindrivenarchitecture.org/img/delta-chat.svg" width=20 alt="DeltaChat"> chat over e-mail](mailto:buero@meissa-gmbh.de?subject=community-chat) | [<img src="https://meissa-gmbh.de/img/community/Mastodon_Logotype.svg" width=20 alt="team@social.meissa-gmbh.de"> team@social.meissa-gmbh.de](https://social.meissa-gmbh.de/@team) | [Website & Blog](https://domaindrivenarchitecture.org)

## Purpose

In order to contribute to forge federation we do here some experiments how to model the vocabulary. We choose clojure for the implementation because

1. concepts of clojures spec & dataomic are quite close to linked data.
2. spec notation is realy compact
3. spec allows validation of models in unitest
4. spec is ways more readable compared to ttls reverse relation 'owl:domain'
5. we know clojure :-)

## Cool ideas

We got feedback from cool people and have collected the ideas around:

* https://github.com/ont-app/vocabulary - a cool way to map clojure namespaces to linked data cotexts.
* https://github.com/lambdaisland/souk - a poc reading jsonld from mastodon & provides a small webserver having the webfinger-protocol
* https://www.youtube.com/watch?v=cru7E96pLAM - youtube series for implementing the souk poc
* [doc/ideaForParsing.md](doc/ideaForParsing.md) - ideas for parsing with jena from a nice conversation with Eric Scott

## Development & mirrors

Development happens at: https://repo.prod.meissa.de/meissa/activity-pub-poc.git

Mirrors are:

* https://codeberg.org/meissa331/forge-fed-poc.git (issues and PR)

For more details about our repository model see: https://repo.prod.meissa.de/meissa/federate-your-repos

## License

Copyright © 2022 meissa GmbH
Licensed under the [Apache License, Version 2.0](LICENSE) (the "License")