https://github.com/linkeddata/solid-dav
Allow solid clients to think of caldav as linked data, and maybe even sync
https://github.com/linkeddata/solid-dav
Last synced: 4 months ago
JSON representation
Allow solid clients to think of caldav as linked data, and maybe even sync
- Host: GitHub
- URL: https://github.com/linkeddata/solid-dav
- Owner: linkeddata
- Created: 2016-12-03T15:06:59.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2016-12-03T15:33:21.000Z (over 9 years ago)
- Last Synced: 2024-04-16T00:08:26.160Z (about 2 years ago)
- Size: 2.93 KB
- Stars: 2
- Watchers: 8
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# solid-dav
Allow solid clients to think of caldav as linked data, and maybe even sync
Given that we have a lot of solid, linked data, support libraries and also
a various \*dav (caldav, carddav, webdav) client libraries,
should it not be easy to
- allow a linked data system to look at a dav space as thogh it were linked data;
- sync between a solid store and a dav store with the same data; and
- develop calendar and contacts clients which operate as part of the leacy dav space but also the new interconnected solid space.
The DAV protocols in a way encapsulate the problem solid came to solve:
you have to design a new protocol and build a new server for each application,
wheras with solid, you design the footprint of each objects in the read-write-web, and standardize it between clients,
but you don't have to design or buld anything new on the backend.
Not sure I will have to actually write this, so very interested in any takers out there in the interwebs.
\#help_wanted
timbl
2016-12-03
See eg https://www.npmjs.com/package/dav