I am still quite noob with these modern JS tools
I started with that for now. It's out of the box more dev friendly. After I have some usefull base we can think how to migrate that with electron. What I am doing isn't communicating to out world so migration shouldn't be any harder to do afterwards.
but that's popular with regular web apps, so works with electron just the same
(from my side)
Plans will be tested
that's very similar to what I had in mind when I made that gif at the footnotes of the foolproof article
Btw I think that if we build something like that invidual frame is single microeditor instance
I misunderstood that json-ld contexes are more like types but seems that these are two separated things there. So we don't have schema/meta model tech right now.
So just for reminder what options we have:
A: Json-schema: simple schema model
B: RDF based schemas
C: Invent our own
D: ???
So A is simplest but too simple. Also I think we should minimize reinventing wheel so I don't prefer C. So this B... Problem is that there are now JS based implementations available.
I think what I start doing next is create html metamodel based on RDFS.
JSON-LD stays still around but its primary usage is to be just standard format
While backend requires understanding about metamodel I craft incrementally minimal JS implementation for RDFS
Goal is not to create full RDFS support but just very minimal set that enables to move forward.
So that we can reuse standard and maybe later if required switch to some more advanced (java based?) library...
So basicly own metamodel / schema libary is because there really seems not to be any (for any good enought mode) in JS world. Also many schema libraries are able to just able to answer for question: does object A match to schema Y? And answer can be just yes/no + human readable error which may not enought for us.
About schedule: This weekend is very reserved but I try to craft RDFS based metamodel due midweek.
I'd love to see some broad terms explanation of what the schema would define and how we'll use it
I managed to code a little bit of interactions in the proto this week
After 18 maybe?
sadly it's not open source
Many thanks to Holger Knublauch and TopQuadrant. SHACL JS validator is now open source.
https://github.com/TopQuadrant/shacl/tree/master/src/main/resources/etc
https://github.com/TopQuadrant/shacl/tree/master/src/main/resources/etc