Gather data models from existing federated platforms

[elf-pavlik]

Preferably schema definitions from code bases and UML diagrams

• [x] Diaspora https://github.com/diaspora/diaspora/blob/develop/db/schema.rb
• [x] Friendica https://github.com/friendica/friendica/blob/master/database.sql
• [x] remoteStorage https://remotestorage.io/modules/code/index/Schemas.html
• [ ] CozyCloud
• [ ] ownCloud
• [ ] Open App (Enspiral)
• [x] PLP (Portable Linked Profiles) https://w3id.org/plp/v1
• [ ] Movim | XMPP Roster, Microblogging over XMPP

[elf-pavlik]

@annando @jaywink, could you help us with collecting detailed information about data modeling your code bases currently use? @skddc @silverbucket let's discuss during IWC Düsseldorf status of https://github.com/elf-pavlik/remotestorage-jsonld-contexts

[annando]

I don't understand. That can either be a language problem or is based upon the fact that I'm a programmer who never look at any theoretical stuff.

[elf-pavlik]

@annando Friendica uses some database, I guess SQL or some document based NoSQL. We would find it useful in our vocabulary work to understand how you currently model your data. Link to schema definition somewhere in your code base could help with that, even better additional UML diagram explaining data types and properties. Something similar to one present in Hydra Core

[annando]

Friendica uses SQL. Here you can see our database structure: https://github.com/friendica/friendica/blob/master/database.sql

Problem is that we don't have any documentation about the relations between the tables. Additionally there is plenty room for improvements to the structure.

[jaywink]

Here is the diaspora schema: https://github.com/diaspora/diaspora/blob/develop/db/schema.rb

I could try rip it out into a pic if I can find a tool to do that, if that helps :P

[elf-pavlik]

thank you @annando & @jaywink :exclamation:

[raucao]

@skddc @silverbucket let's discuss during IWC Düsseldorf status of https://github.com/elf-pavlik/remotestorage-jsonld-contexts

Sure, looking forward to it!

[paultranvan]

@elf-pavlik Cozy uses CouchDB as a document-based NoSQL database. Basically, a document is composed of an id, a revision (both handled by CouchDB) ,a doctype (eg agenda, file, photo...), and some key-value pairs. The apps developers can create their own data models by defining a new doctype or just use an existing one. There is some documentation here : http://cozy.io/en/hack/getting-started/architecture-overview.html

[elf-pavlik]

@Gara64 we need more those scope specific data models e.g. iCal, vCard etc.