Hi Robert,
Thanks for your analysis - I hope others are going to answer as well,
but here are at least my comments:
I've created several types and other proposed 'well-defined' bits
of
metadata to assist the publishing of these documents into a nice
format and easing the pain of parsing
Bertrand Delacretaz wrote:
Thanks for your analysis - I hope others are going to answer as well,
I've forwarded Roberts original message to the Forrest list since we
will, no doubt, be using the output of this project. I've asked Forrest
devs to reply on our own list, but I will provide a
ok - my view was a more high-level one than classes and methods, which
are adequately covered by the javadocs. These are certainly useful
though, but see the proposed use-cases below for a more
component-oriented view.
Okay, this was something I wasn't sure about, but I thought it might
be
Robert Graham wrote:
Note that these assume a dynamic search of the refdoc index - I think
the full power of the refdoc will be available only when querying the
Lucene index directly, as is done in some of these use-cases, but the
document-oriented version (that will probably be published as
Le 1 août 05, à 15:29, Ross Gardler a écrit :
...The dynamic searching capability can be got for free by integrating
your work into Forrest ...
...Of course, Bertrand may have something else in mind as well.
I was thinking about searching on any metadata field provided by refodc
snippets.
Hi Robert,
...Maybe introducing an
order number metadata attribute would help and not be too hard to
manage? We could then rearrange the snippets be changing their order
numbers, while keeping the overall order based on the snippet types.
Perhaps. I think some sort of weight might give the
Hello All,
I'd like any and all input on this as it would make it much better
than I will alone. However, I've sketched out something to start from.
First I'll give a brief description of what I'm talking about for
those that haen't kept up with RefDoc, then I'll present my ideas, and
finally
