Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Dmitri Zagidulin
@dmitrizagidulin
thanks! :)
Amy Guy
@rhiaro
@dmitrizagidulin Who's your friend?
Any link to work?
Dmitri Zagidulin
@dmitrizagidulin
guy named Michael Broughton, working at university of Koln in germany. I'll see if I can get a link, but I think he's just starting his thesis
something about trying to convince a part of the scholarly editor community to move away from Text Encoding Initiative flavored XML markup and more towards something more rdf/linked data like
"Scholarly editors are transcribing and marking up old texts using Text Encoding Initiative flavored XML. The two biggest problems they run into is that A) they keep having tag overlap because they want to say things about these texts that are from different value hierarchies (most notably, talking about the text encoded in the document and the realities of the text-bearing artifact (aka document) itself. And B) when one editor marks up a text, it is practically IMPOSSIBLE for another editor to use it."
^ etc.
Amy Guy
@rhiaro
ohh, interesting. Transcribing is like an orthogonal problem I hadn't even thought about... but yeah, related I guess. Awesome if dokieli could cover that use case!
Dmitri Zagidulin
@dmitrizagidulin
yeah, definitely gonna steer him towards it
Amy Guy
@rhiaro
'editor' in the context of that paragraph is a human being, right?
Not a tool/system?
Dmitri Zagidulin
@dmitrizagidulin
yeah, I think so
definitely the first usage of it, and probably that last one too
Amy Guy
@rhiaro
This sounds like a humanities thing
Dmitri Zagidulin
@dmitrizagidulin
it is, yeah
but he was looking at the Open Annotation spec, which is why I asked here
Amy Guy
@rhiaro
great
Sarven Capadisli
@csarven
@dmitrizagidulin @rhiaro dokieli sort of covers some TEI-like UCs in which you can embed arbitrary descriptions (in Turtle, JSON-LD, TriG) into the document (see the menu -> Embed Data). So for instance, if you want to say something more about a heading (which wouldn't normally go into the body text of the article), you can do it from there. The UI needs to improve on that front.
Dmitri Zagidulin
@dmitrizagidulin
nice, ok.
how is Pundit (http://labs.europeana.eu/apps/pundit) related?
Sarven Capadisli
@csarven
I haven't reviewed Pundit yet.. but it looks along the lines of hypothes.is
As for annotations, we're quite current with the Web Annotation data model. Open Annotation was precursor to the current W3C Web Annotation WG.
Dmitri Zagidulin
@dmitrizagidulin
makes sense.
Sarven Capadisli
@csarven
In case you haven't tried it yet, if you sign-in and leave an annotation (the last button in the toolbar after highlighting), it will write the annotation to your storage using the text quote selector approach i.e., it captures the exact selected text, 32 chars prefix, and 32 chars suffix. It stores that information in the annotation (at your storage), and then two things happen: 1) the current document fetches that annotation and inserts it into the document (visible on the side of the document), 2) leaves a notification for it on the document's inbox so that when that document is loaded again, it will go through step 1.
If you experience issues, please file them :)
Dmitri Zagidulin
@dmitrizagidulin
thanks!
Sarven Capadisli
@csarven
Oh.. 2 is not completely finished. It is leaving the notification at the inbox, however it is not loading the notifications from the inbox. Should be done by the end of day :P
Tim Berners-Lee
@timbl
@csarven? do you know when when I saved a dokeili document to timbl.com I couldn’t edit it?>
Sarven Capadisli
@csarven
@timbl I replied to your email.. And that's fixed now. Default document mode is 'read', so changed it to 'edit' when the user does a 'save as' (the URL for it includes ?edit=true).. which goes away on load (rewrites the URL history).
We are already doing ?edit=true for 'new' documents, and doing it for save as makes sense.
I don't know at the moment if there will be document modes other than 'edit' (besides 'read') but for now I prefer not to persist ?edit=true in the URL. It will minimize the number of different URLs being bookmarked/copy-pasted...
Sarven Capadisli
@csarven
@sandhawke re: issue #100 , Thanks! That's a great set of features to have documented.
Tim Berners-Lee
@timbl
Agreed that the ?edit=true is good to phase out. The URI should be for the thing not the view
You could store things about the particulat view I have n the document but also in my dokeili prefernces
(like #100)
It is reasonable to disable editing I suppose if you know that the user does not have write access,
Melvin Carvalho
@melvincarvalho
@timbl so what should the URI be of a single page app with more than one view?
Tim Berners-Lee
@timbl
or if you know that the user is not the author and the author wants to be theonly editor, I suppose, whatever the ACLs. But if you disable editing explain why
Tim Berners-Lee
@timbl
Ok, now I am happily entering text
I don’t see controls for styling, headings, etc
Sarven Capadisli
@csarven
re: storing user preferences, we have an issue for it.
Editing and saving (which may or may not require "write access") are different procedures. I think dokieli should provide the ability to "edit" any document anywhere (on/offline). Whether the user wants to save that somewhere, that's entirely up to them. If for instance, they have nowhere to write, they can still "export" (see the menu) the document and store locally.
I mean to export the file and save to disk (sort of like brower's File->Save As).
Sarven Capadisli
@csarven
There is also the local storage option.. you can get stuff done that way as well. If the user gets back online, they can pretty much just click 'save'.
The controls for formatting, annotating etc are visible (they pop up) when you select/highlight some text.
There is a todo item which will customize the UI/editor based on the ACLs. For instance, by default anyone can annotate and notify the resource's inboxes. But, those are all annotations stored in the contributors pod. A user with an editor role however, more or less go through the same procedure with the difference that the annotation-like thing is like a footnote/citation - that is however stored with the document itself.
Sarven Capadisli
@csarven
@dmitrizagidulin [✓] Display notifications from inboxes.
Dmitri Zagidulin
@dmitrizagidulin
nicely done :)
Tim Berners-Lee
@timbl
Still having trouble do.js:675 XHR finished loading: HEAD "https://timbl.com/timbl/2016/01/18/dokeili-test/dokeili-test.html".(anonymous function) @ do.js:675DO.U.getResourceHead @ do.js:663(anonymous function) @ do.js:510promise @ do.js:509DO.U.getInbox @ do.js:521DO.U.showInboxNotifications @ do.js:622(anonymous function) @ do.js:3797j @ jquery-2.1.4.min.js:2k.fireWith @ jquery-2.1.4.min.js:2n.extend.ready @ jquery-2.1.4.min.js:2I @ jquery-2.1.4.min.js:2
simplerdf.js:24185 XHR finished loading: GET "https://timbl.com/timbl/2016/01/18/dokeili-test/dokeili-test.html".(anonymous function) @ simplerdf.js:24185utils.defaultRequest @ simplerdf.js:24151(anonymous function) @ simplerdf.js:29272LdpStore.graph @ simplerdf.js:29268SimpleRDF.get @ simplerdf.js:23850(anonymous function) @ do.js:547DO.U.getInboxFromRDF @ do.js:544(anonymous function) @ do.js:523
do.js:558 TypeError: Cannot read property 'indexOf' of null(…)
do.js:629 TypeError: Cannot read property 'indexOf' of null(…)
RDFaProcessor.min.1.4.0.js:33 Uncaught (in promise) TypeError: Cannot read property 'indexOf' of null(…)e @ RDFaProcessor.min.1.4.0.js:33RDFaProcessor.process @ RDFaProcessor.min.1.4.0.js:33(anonymous function) @ simplerdf.js:26018RdfaParser.process @ simplerdf.js:25952(anonymous function) @ simplerdf.js:26199AbstractParser.parse @ simplerdf.js:26198ParserUtil.parse @ simplerdf.js:29398(anonymous function) @ simplerdf.js:29293