Re: Document Indexing -- How to index Dynamic Content?

  From: ianweb@smaug.java.utoronto.ca (Ian Graham)
| Essentially, the content design and layout can done perfectly well 
| using HTML 3.2 , without any frame, java or javascript extensions. Why
| should authors be forced to use all these complicated extensions, when
| a simple HTML feature could resolve the problem?
| 
| THe question to my mind is -- is this a sufficiently common issue that
| warrants an HTML-based solution?
---

I think the whole indexing issue needs a lot more thought than it
appears to have gotten in writing the specs.  It is important to be able
to indicate that certain information is not to be indexed.  I would be
inclined to add a common attribute NOINDEX (applicable to all elements).
There might be some elements for which NOINDEX would default to being
present (in SGML-ish, I think that means its value would default, for
some elements, to being NOINDEX).

As I've mentioned elsewhere, I think there should also be a mechanism
for indicating that certain elements should be indexed against a foreign
resource, rather than against the one they occur in.  In particular, I
would like to be able to wrap a description of a resource with markup
that indicated I was describing some other resource (for which the
indexing would be appropriate).  Searches for the keywords in the
description should probably not retrieve my document (but might should
retrieve the referenced resource).

[The "probably" is because a search engine capable of doing co-citation
searches would want to have access to the fact that I pointed to
the resource, and others, and make connections between the referenced
resources on the basis that they were referred to from the same place.]

scott

--
scott preece
motorola/mcg urbana design center	1101 e. university, urbana, il   61801
phone:	217-384-8589			  fax:	217-384-8550
internet mail:	preece@urbana.mcd.mot.com

Received on Thursday, 7 November 1996 13:18:17 UTC