From: Al Gilman <email@example.com> Message-Id: <199710291954.OAA25260@access4.digex.net> Subject: development track for "where-it-says" To: firstname.lastname@example.org (Larry Masinter), email@example.com Date: Wed, 29 Oct 1997 14:54:04 -0500 (EST) Cc: firstname.lastname@example.org, email@example.com In-Reply-To: <34555B44.47DDD707@parc.xerox.com> from Larry Masinter at "Oct 27, 97 07:25:57 pm" To do a little forward thinking, and follow up on what Larry Masinter said: > The "#fragment" notation is only used for named components. > Makes a lot of sense to me. My initial stab at syntax for "where-it-says" was a searchpart along the lines of ...?find="string-to-match" . What I have learned from this discussion is that I need to start with the HTML community. If I can interest HTMLx development in exporting a reliable (i.e. consistent across browsers) string-matching search/location method for HTML, I hope that the URL specs won't have narrowed to the point where there is no reasonable syntax by which to ask for it. I believe that the XML project is already working on intra-document locators in XLL although I am not sure that they provide any sort of a pattern match yet. -- Al Gilman PS: I know that searchparts are presently server-side functions but I don't immediately see that extending them to be sometimes done client-side poses any real conflict.