SolidOS for devs: https://github.com/solidos/solidos SolidOS Pod: https://solidos.solidcommunity.net/
Not sure if this affects us in any way, https://twitter.com/lrvick/status/1523787247706951680?ref_src=twsrc%5Etfw. Apparently someone purchased "foreach" domain.
1 reply
if I have
some var <= this.some_other_var in javascript is then 1 assigned to 2 or 2 assigned to one ? guess some_other_var in this case is assigned to some_var ? other way around ? a digital world ?
guess one named_node and two string ? 1a forrest gump question but my mind is slow
in that snippet the group of urls is filter such that each url is not a container
it returns a list of only the urls that match the condition, in this case the condition is a ! not
This
console.log( [1,2,3].filter($_ => $_ < 3) ); // prints [1,2]
yep, I began to change the type systematically. could you (time plays no role) fix that first error in SolidOS/solid-logic#38 so that I have a working example ? for sure I have to dig through the code and look for the Definition of the questionable variables
2 replies
The interface above created a job that looks like
:id1629189983448
a solid:CurrentRole;
schema:description "I work on SolidOS";
schema:startDate "2021-08-02"^^xsd:date;
vcard:role "Software Engineer";
org:member :me;
org:organization :id1629189994814 .
:id1629189994814 a schema:Corporation; schema:name "Inrupt".
and
:id1629189983448is not under :me (it is not linked with any prediacate)
so... is this a problem?
Its a graph not a tree .. links either way are just as valid
So no it is not a problem
If you like at fr example
store.connectedStatements(me) you will get it
(In N3 you can also write
:me is org:member of [ a solid:CurrentRole;
schema:description "I work on SolidOS";
schema:startDate "2021-08-02"^^xsd:date;
vcard:role "Software Engineer";
org:organization [ a schema:Corporation; schema:name "Inrupt”]].
This is a good example where you have to be equally happy to follow links in either direction.
This included the form system where there is a flag to make a form element so a reverse link.
7 replies
@timbl @bourgeoa @jeff-zucker @timea-solid we have this turtle file about providers https://ewingson.solidcommunity.net/public/ttl/pod-provider.ttl . the subject URIs don't really exist. shall we (together with help) make a real existing rdf/turtle file of it and use it as data source for https://solidproject.org/users/get-a-pod ?
@ewingson - Timea and I are working on how to use RDF as a source for solidproject.org pages. If you can develop an ontology to express the pod-provider information, we can certainly use that. You might look at DOAP and other existing ontologies of software. As I've mentioned before, there are issues about what it means to officially list services on solidproject.org and the final decision about which providers are listed will be up to the Solid Team. But we would need a standard set of ontology terms in either case.
@timbl and @timea-solid - great work on the new discovery stuff, how hard would it be to a) make the discovery bits into separately callable apps b) add those apps as addenda to the webid-profile spec that apps can reuse so we don't have everyone and their uncle writing profile-munging code?
5 replies
Or separately callable would work too, an app could import solid-ui and call the ensurePreferencesFile method.
Or there could be one validate-and-fix method/app which ensures a valid profile. Apps could run it on startup so they'd always know they are dealing with a valid profile.
SolidOS/solid-logic#39 has got the functionality for readding type ndexes and making new ones and registering things
And tests for all non-error paths as far as I can see
5 replies