31 Oct
2009
31 Oct
'09
9:54 p.m.
On Oct 31, 2009, at 9:21 PM, Sergiu Dumitriu wrote:
The problem with a context is that you must make it long enough to
properly determine the right position, and short enough not to require
too much storage space.
How about XPath expressions for the start and end positions on the
XDOM?
This could fail for dynamic queries, where the number and position of
entries would change. But do we want to annotate this kind of elements
anyway? Like, why would somebody make annotations on the results of a
search?
I don't think the XPath is going to work.
Imagine that your XPath targets a node that is a "script". Then you
need an offset for identifying the annotated content span. But the
content of this node could be anything once expanded : it depends, in
fact, on the outcome of the script (I am not talking about result
queries). So you end up with the original "offset" problem you have
with dynamic content. Before you had this at the page level, now you
have it at the node level.
Unless I misunderstood your solution.
Anyway, is this context storage issue a real problem? I mean, even
putting 1K text into each annotation is it really something that we
should avoid at all costs? (I agree, though, that it could be
redundant and inefficient)
-Fabio