15,627
edits
Changes
Jump to navigation
Jump to search
Line 20:
Line 20: + + + + + + + + + + + + + + + + + + + + + + + +
→Lessons from "telephone number"
== Lessons from "telephone number" ==
== Lessons from "telephone number" ==
We implemented a quick system for storing {{Q|488}} locally and interfacing with the server.
The perspective/goal has been refined: smooth distribution of data and computation across server and client.
=== Computing ===
The server computing environment could be:
* gadgets;
* user scripts;
* other?
The client computing environment could be:
* the browser javascript environment,
* a browser extension (in [https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Anatomy_of_a_WebExtension background page or content scripts])
The client itself can distribute its data however it pleases, as well as the computations it needs to perform. The server serves code that has to be run.
=== Static data ===
For static data, we win the closest we are to storing RDF graphs. RDF graphs (i.e. collections of triples) have the advantage that they are directly interoperable at a technical level. Just append the two files. So when we store data, including in the browser, etc, we should be as close to that as possible.
=== Semantics ===
Beyond mere storage of data, the semantics matter as well. For interoperability reasons (multiple servers eventually), it makes sense to get as far away from possible from the intricacies of Wikibase, and refer to concepts using external tags, possibly coming from well-known ontologies. This is true on server side, as well as on client side.
=== Conclusions ===
*