csarven on main
csarven on main
Remove uglify, configure Webpac… (compare)
csarven on main
Fix: include sourcemap link in … (compare)
Hey @dgarijo . Generally yes and it'd be no different than dokieli's CSS and JS being included in any HTML. There are of course some markup patterns that dokieli has in which you can get more out of the tool - what it can detect / display. The pattern is fairly straight forward to follow / generate IMO.
dokieli doesn't offer a transformation from anything to dokieli HTML. That's out of scope. So, you might want to find a tool that gives you a simple HTML. From what I've seen - and I can't say I have much experience with it - pandoc is pretty decent to get things going. You'll really have to massage whatever it generates if you really want to bring it closer to HTML like in articles listed in https://github.com/linkeddata/dokieli/wiki#examples-in-the-wild -- but don't take that as absolutes. Just in the right direction of things working properly.
See https://dokie.li/new as what the outer HTML should look like. Aside: see how the HTML patterns in https://dokie.li/ or https://dokie.li/acm-sigproc-sp or https://dokie.li/lncs-splnproc or https://csarven.ca/linked-research-decentralised-web .. essentially have no difference. It is just the CSS doing the work.
My suggestion is to take it step at a time. Unlikely that you'll get a perfect document coming out of LaTeX... but dig around for XSL-based approaches as well.
ld.store.serializers['text/turtle'].serialize(g._graph)where the return contains the accumulated prefixes. Not sure if there is something I can do before that (eg. some option to SimpleRDF.parse?) or as I call that.
You're already on the right track. dokieli's Web Extension will let you annotate any HTML document. dokieli's CSS/JS can also be included in an HTML document.
Perhaps the diagram in https://csarven.ca/linked-research-decentralised-web#examplar-information-space can help to clarify the connection between an article, inbox, notification, annotation, profile and so on. See also this diagram https://csarven.ca/dokieli-rww#figure-dokieli-architecture-relations
At the moment, the location of the annotation may be your personal storage root but that can be changed - without asking the user necessarily. (At the time we didn't have a specification / practice to do that). It can be any HTTP URL in fact that you have write access to. There is some relatively small work there - dokieli just needs to be able to discover the information that indicates user's preferred place or perhaps ask the user where to store it at each time. I initially decided to just store at storage root as that was simplest and also to not bother the user. There are a number of possibilities there and I don't think they're mutually exclusive either.
The "annotation service" is a bit like the location that the article suggests where annotations can go - similar to how public comments tend to work on the current Web but there is no constraint that it must be a public location. That too can be access controlled.
What dokieli decides is basically if you there are multiple places to store an annotation, it will prefer to use your personal location - because you ultimately control that - but it can still send copies to other locations - if selected on the UI - and refer back to the canonical one (on your storage).
Notification is used as a way to allow the discovery of annotations made on an article. To get there, dokieli checks what the article's inbox is and then finds its notifications, and the notifications will have a reference to an annotation URL.
@berezovskyi I've removed that rule and it seems to resolve the issue. (Shower CSS is typically on HTML pages that's only intended for presentations. dokieli's CSS includes Shower CSS and it can be on any page - as you've seen for the spec.) Shower CSS's page rule is not particularly required. User can select the landscape mode in a very specific case: HTML includes dokieli that's intended for slideshows using the Shower presentation engine.
Thanks for pointing out and let me know if that address it - you clear your crash and try again.