| Version 1 (modified by , 11 years ago) (diff) |
|---|
Contents
PundIt?
The tool's web-page: http://thepund.it/.
PundIt? workshop, den Haag 23/05/2013
This is a short summary about the things discussed at the PundIt? workshop on 23/05. Some more dedailed and additiona information will be available once I recieve the slides of Simone Fonda (the tool developer).
Users of PundIt?. "Europeana cloud" can be one of them. Currently they consider if the tool suits their aims.
License: open source since 1 month.
OA-compatibility: not 100%, but in the ToDo? list of the developers.
An RDF-triple: is the only schema of any PundIt? annotation, which must have the form "subject-predicate-object". The workshop audience was rather critical about it since you really need to get used to the way the things are annotated. While simple annotations like| "text A"-"created by"-"author B" can be created and saved quickly, a more involved relation needs a specific workaround.
In the future, the developers plan "to hide the triples" behind user friendly composite (modular) predicates. In particular they consider adding variables to be able to express something similar to search queries, e.g. text X created by Marx where the creation date of X is between 1830 and 1840 (not sure about exact formulation).
Vocabularies for predicates: are provided or can be configured by the administrator. PundIt? requests vocabularies e.g. via KORBO api.
Administrator. Both, the client and the server, parts of PundIt? need administrating. The administrator needs to configure and update vocabularies for the client and the servers where annotations are saved.
Server. At the moment PundIt? is well-thought as a one-server system. Connecting multiple servers is in the future plans. One of the forseen problems is export/import of notebooks, with annotators registered on one server and not registered on another.
Notebooks. At the moment you cannot copy an annotation from one notebook to another.
Authentication/sharing. An authentication can be done via an openID, a google or yahoo account, or credentials are created by a PundIt? server. A user can create either fully personal or fully public notebook. No group notebooks are possible at the moment. The workshop audience was not happy with that. A workaround: to fake a group you make a single account for a group of people. In this case, however, it would not | be clear who is annotating what, unless the participants make an agreement how each individual marks his/her annotations.
Named-content methodology. You may annotate not only a web-document but its content, if its web-publishers agrees to provide a content vocabulary. For instance, let there be 2 images of the same person in a document. If the publisher allows to mark them by the same content (the name of the person) then any annotation on one image is an annotation the other one and vice versa. Entities with the same content does not need to belong to the same document (???). Moreover, in the same way you create linkig between a high- and a low-resolution versions of the same image.
Another situation where content annotating can be used is resolving an annotation with dynamically updated document (in some cases). For instance, if an image or a text fragment are annootated as conent then when they are moved from one place to another their annotations will be still resolvable.
Annotating image. You can annotate an image part as well, by surrounding it by the coresponding polygon.
Visualisation. In principle it is possible to connect PundIt? to some fancy visaulising tool. There a demo example where the participants of the workshop create each two annotationsof the form: "text A is created by a phylosopher B", and "text A cites a philosopher C". A third-part aggregator collect all such annotations and make a time-line in which "B is influcenced by C" connections can be seen for all B and C used by the participants of the workshop to create their triples. Technically, connecting to a visualisation tool needs an intermediate layer which will send the necessary requests to the annotation server and transforms the returned values to the data for the visualisation tool.
UI. Can be better. The PundIt? developers wants to make it user-friendlier, e.g. by adding help, etc.
