Related Work: Monetising Resources on a SoLiD Pod Using Blockchain Transactions (ESWC Demo)

[uvdsl]

Hi,

I wanted to share our work on monetising web resources using SoLiD Pods and an Ethereum Blockchain.
It is the result of a student seminar on the topic of Semantic Web and Linked Data.
We presented the prototype as a demo at ESWC.

I don't know if you would like to include it on the list of recent work or not.
In any case, we appreciate any discussion, comments or remarks. :-)

Cheers
Christoph

---

Abstract.
Our demo showcases a system that allows users to provide access to web resources in exchange for payments via the blockchain. The system enables users to create offers for their resources or buy access rights for resources belonging to other users. Access rights can be granted only for a limited amount of time. We built our system as SoLiD Pods and Apps: We developed two server modules for SoLiD Pods that automatically (1) grant access for valid payments via the blockchain and (2) remove expired access rights. On top, we developed a SoLiD App that allows to offer resources, browse and request offered resources, and make payments via the blockchain.

Resource	URI
Teaser (1 min)	https://www.youtube.com/watch?v=sqIeYRTrkEg
Demo Website (inkl. 3 min video)	http://people.aifb.kit.edu/co1683/2021/eswc-demo-solibra/
Code	https://github.com/bright-fox/SolidBlockchain
Paper	http://people.aifb.kit.edu/co1683/2021/eswc-demo-solibra/solibra.pdf

[michielbdejong]

Wow, great! Yes, please create a PR to add yourself to the list!

On page 3 of http://people.aifb.kit.edu/co1683/2021/eswc-demo-solibra/solibra.pdf you say "Our approach uses Web Access Control (WAC)" - are you also specifically using the acl:agentClass acl:PayingAgent predicate proposed in #7?

[uvdsl]

Will do!

Oh cool, I did not know that there was a consensus on the 402 and acl:PayingAgent. Is that already implement in NSS?

The student seminar took place in the winter semester and ended in February. Back then, very limited information on how things should work were available, so we implemented a workaround without fiddeling with NSS too much. You opened #7 in March, so no, in the demo, we do not use 402. We just used the standard NSS (at that time).

To advertise any payables (purchasable resources), we defined a folder where the corresponding offers are accessible.
I think, one could link to those offers in a 402 response without any issues. With that, all the corresponding payment information are discoverable from the resource itself (without any additional knowledge about folder structure...)