A browser for the linked data web.
Connect it to your SOLID pod, view dbpedia articles in the style of wikipedia, and install new applications.
This browser uses link-redux to build its views, check it out for further details on the internals of application development.
Why Mash? An alternative name for link was mesh, but for the initial demonstration as a tongue-in-cheek
wink to mashlib I replaced the e
. Depending
on how things work out, we will rename this project to be more distinguished from that library, but
hopefully what won't be necessary.
Create an self-executing UMD package;
// index.js
export default ((lrs) => {
lrs.registerModule({
iri: "https://example.com/application/MyClass",
middlewares: [
// If you have an interactive application
],
ontologyStatements: [
// If you want to say things about your ontology
],
version: 1,
views: [],
});
})(window.LRS);
The IRI (URL) of your package, generally the entry class, aka the one a user will bump into first.
Example; For a TODO application it would be the TODOList.
Currently this URL must resolve to a file which describes your package;
@prefixes
<>
a rdfs:Class, ll:InstallableComponent;
schema:name "Demo TODO app";
ll:npmLabel "link-redux-todomvc";
ll:npmVersion "2.12.0".
Pass an array of link middlewares to be added on top of the current stack.
Here you can instruct link to take some ontological information into account when rendering your views. It's generally good practice to subclass rdfs:Resource and optionally a more specific class which fits your classes (eg schema:person and foaf:Person).
Include all your link views in the bundle.
These shouldn't be the raw views, but the result of LinkRedux's register
call.
A flat array of RegistrableComponent
to be precise.