Arquisoft / dechat_en2a

Dechat EN2A
https://arquisoft.github.io/dechat_en2a
MIT License
8 stars 7 forks source link

Usage of Turtle #20

Closed AlvasanG closed 5 years ago

AlvasanG commented 5 years ago

In order to store the data of the messages within a users pod we will use turtle rdf format.

The basics of the format are specified on its w3c standard webpage Turtle. In order to use turtle rdf within our project we should be using rdflib.js https://github.com/solid/solid-tutorial-rdflib.js, which contains simple tutorials about the usage of the library.

What we need to do is store:

Every message shall be parsed as a tuple with the aforementioned schema.

AlvasanG commented 5 years ago

Here are some tutorials / examples that might be useful in understanding how turtle is defined and how rdflib works:

Turtle tutorial -> https://www.youtube.com/watch?v=AXN9gszoti4 Rdflib.js examples -> https://github.com/linkeddata/rdflib.js/issues/43

AlvasanG commented 5 years ago

Also the way of managing files is done with SolidFileClient but I forgot to place the reference link in the other messages. Here it is https://www.npmjs.com/package/solid-file-client

AlvasanG commented 5 years ago

As of now we are able to store the information into a the graph localy and then push it into the file in the users POD. It has some major drawbacks thay I will specify later:

After this 2 major issues are fixed, or at least 1 of those, I will update again this issue and commit the changes into the branch.

Useful links:

AlvasanG commented 5 years ago

As I am unable to correctly create a tuple everytime a message is sent, and rather it just adds the information into the already existing tuple I have created a discussion in the solid forum.

Will try to work further on my own while I wait for some feedback on the solid forum.

AlvasanG commented 5 years ago

As indicated on the solid forum, the usage of a ontology or vocabulary to represent the messages is needed. After some digging I found this ontology, whose SMS section fits our needs greately.

I will need to change how the message is being sent to adapt to this new ontology in the following days, here is the documentation of the aforementioned ontology.

josecurioso commented 5 years ago

Based on the information compiled in this issue, a bunch of helper methods for reading and writing messages to the POD's native chat format have been implemented on [joseDev]() branch but as stated in #19 it is no ready for a pull request yet.

AlvasanG commented 5 years ago

As we already have a base using ttl I will proceed to close this issue. If further assistance is needed with ttl we can open new issues regarding those specific problems, or reopen this same issue.