Talk:Annotation: Difference between revisions
No edit summary |
|||
| Line 8: | Line 8: | ||
I haven't looked at those closely, though I need to do so. I believe Joshua Gay had some experience with Marginalia. I've yet to see an actual ''documented'' use of Atom for annotation, as Atom does not address the particular needs of annotation directly. It has to be extended or its conventions repurposed in some way. So several systems use Atom, but frustratingly none of them say how. -- [[User:Ian Bicking|Ian Bicking]] 17:21, 24 July 2007 (EDT) |
I haven't looked at those closely, though I need to do so. I believe Joshua Gay had some experience with Marginalia. I've yet to see an actual ''documented'' use of Atom for annotation, as Atom does not address the particular needs of annotation directly. It has to be extended or its conventions repurposed in some way. So several systems use Atom, but frustratingly none of them say how. -- [[User:Ian Bicking|Ian Bicking]] 17:21, 24 July 2007 (EDT) |
||
---- |
|||
I'm the author of Marginalia. I just threw together a [http://www.geof.net/code/annotation/technical/atom page] with a minimal explanation of how I'm using Atom. -- Geof Glass |
|||
== A bit confusing... == |
== A bit confusing... == |
||
Revision as of 02:05, 11 August 2007
More specifics on where javascript comes in would be useful. Sj talk 16:37, 2 June 2007 (EDT)
Comment: I don't know whether you have seen marginalia which already uses an Atom based format? I used this when building annotater -- a python wsgi application for doing annotation. You can see this in action on this page on Open Shakespeare. Some of further discussion of the issues can be found in: this thread and this post --RufusPollock Open Knowledge Foundation
I haven't looked at those closely, though I need to do so. I believe Joshua Gay had some experience with Marginalia. I've yet to see an actual documented use of Atom for annotation, as Atom does not address the particular needs of annotation directly. It has to be extended or its conventions repurposed in some way. So several systems use Atom, but frustratingly none of them say how. -- Ian Bicking 17:21, 24 July 2007 (EDT)
I'm the author of Marginalia. I just threw together a page with a minimal explanation of how I'm using Atom. -- Geof Glass
A bit confusing...
Sharing activities. Sharing files, with automatic shared version control. Sharing clipboards / scrapbooks / bulletin boards / whatever you call them. Sharing annotations. Each time, with a totally new model, designed from scratch, using a separate communication paradigm and a different user interface; with the possibility of working on three "layers" of shared content concurrently (document, annotation, and bulletin board). Oh, and we start shipping five million units in under 6 months.
It's not that I think thorough redesigns aren't good, or that these aren't good ideas. But I think it would be better to do one of them right, first. Then, if you still need the others, you have the user experience to integrate them well into what you have.
Just sayin'.
Homunq 02:00, 3 August 2007 (EDT)
- Sorry, that came out really negative. On a more positive note: I think that this could be thought of as "persistent items in the bulletin board" for a given document in a given activity. If you integrate it well, it's not just more features. Homunq 02:14, 3 August 2007 (EDT)