On Wed, Jun 30, 2004, Alexander R. Pruss wrote:
Bookmarks select a point in the text while annotations select a range of
text. Thus, a bookmark can be thought of as an annotation with
triggerStop == triggerStart.
If an option was added to include an annotation for the whole page,
i.e. not a
Michael Nordstrom wrote:
On Wed, Jun 30, 2004, Alexander R. Pruss wrote:
Bookmarks select a point in the text while annotations select a range of
text. Thus, a bookmark can be thought of as an annotation with
triggerStop == triggerStart.
If an option was added to include an annotation for the
Jewett, Jim J wrote:
Will there be only one annotation/bookmark db per text db?
Alexander R. Pruss:
Yes. I don't think the renderer should be scanning several.
I agree with this, in principle; the question is what sort
of tradeoffs that will require.
For example, if I were reading something
For example, if I were reading something by Plato, I might want
to see translation notes, commentaries from Augustus, class
notes from a professor, notes from a modern scholar relevant
to my own paper, and my own comments.
This looks more like a task for lots of hyperlinks, and it looks like
For example, if I were reading something by Plato, I might
want to see translation notes, commentaries from Augustus,
class notes from a professor, notes from a modern scholar
relevant to my own paper, and my own comments.
This looks more like a task for lots of hyperlinks, and it
looks
Jewett, Jim J wrote:
For example, if I were reading something by Plato, I might
want to see translation notes, commentaries from Augustus,
class notes from a professor, notes from a modern scholar
relevant to my own paper, and my own comments.
This looks more like a task for lots of
Alexander R. Pruss:
... how annotations should be stored. The consensus is that
they're being moved out of metadata, and into a separate db.
Will there be only one annotation/bookmark db per text db?
I know that one of the earlier goals was to distribute
commentaries, and there will probably
Jewett, Jim J wrote:
Will there be only one annotation/bookmark db per text db?
Yes. I don't think the renderer should be scanning several.
I know that one of the earlier goals was to distribute
commentaries, and there will probably be some texts that
have more than one relevant commentary.
On Sat, Jun 19, 2004, Alexander R. Pruss wrote:
headerLength is used so we can extend this later to include other data,
such as RGB value of highlight, and anything else one might fancy.
[..]
dataLength is also nice for the same reason. For all we know, there might
be reason to store other
Michael Nordstrom wrote:
I wouldn't worry about the 6 bytes per entry very much myself.
Using separate records are not so much for saving space, but to be
able to identify them. How do you know if a record contains a bookmark
or an annotation for the whole page?
Bookmarks select a point in the
[ This is a discussion being transfered from plucker-team. We're
discussing how annotations should be stored. The consensus is that
they're being moved out of metadata, and into a separate db. The question
is to finalize the format of the annotations db record, and to decide how
to harmonize
11 matches
Mail list logo
