Geoff S. (firstname.lastname@example.org)
Tue, 18 May 1999 18:09:48 +1000 (EST)
Yes, I'm referrring to NON HTML tags, such as extending the index list in
the database to inherently include some extra info, as opposed to anything
embedded with the file itself (which may be a binary). The idea is that
each file name stored by htDig would also have a 2k record associated with
the file that the user could put user defined info into. Call me a fuddy
duddy, but I think HTML metatags is NOT the elegant way to do this, nor is
calling an external database via a CGI when a fairly simple extension of
the htDig database would be a far more integrated and elegant solution.
Keep in mind the external database (just suppose this was the path we
adopt) would then need to be possibly resynched against htDIG, which is a
whole new can of worms.
C,mon - if Maggot$oft can maintain file info databases (or at least may
one day do so, after service packs 1-237, sub-patch 823, interim release
#6) then surely we can do something to hold revision control, author(s),
concept tags and so on.
On Mon, 17 May 1999, Geoff Hutchison wrote:
> >manually add a concept to a text file (the concept being a word not
> >contained in the text). I would humbly suggest an incorporation into the
> >current database of say 2048 bytes of user defined data against each file
> You mean beyond the user-defined META keywords and description data? Yes,
> for HTML files they're picked from the file itself, but this is not a
> -Geoff Hutchison
> Williams Students Online
To unsubscribe from the htdig mailing list, send a message to
email@example.com containing the single word "unsubscribe" in
the SUBJECT of the message.
This archive was generated by hypermail 2.0b3 on Tue May 18 1999 - 01:25:42 PDT