Return-Path: Delivered-To: apmail-xml-general-archive@xml.apache.org Received: (qmail 72277 invoked by uid 500); 2 Jul 2001 18:45:53 -0000 Mailing-List: contact general-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: general@xml.apache.org Delivered-To: mailing list general@xml.apache.org Received: (qmail 72227 invoked from network); 2 Jul 2001 18:45:49 -0000 Subject: RE: Capturing relevant source document during XSLT processing To: general@xml.apache.org X-Mailer: Lotus Notes Release 5.0.6a January 17, 2001 Message-ID: From: David_N_Bertoni@lotus.com Date: Mon, 2 Jul 2001 11:45:09 -0700 X-MIMETrack: Serialize by Router on CAMMAIL01/CAM/M/Lotus(Release 5.0.8 |June 18, 2001) at 07/02/2001 02:45:12 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hi Brian, You might want to take a look at the trace facilities in Xalan. For example, you can be notified when a node is selected for transformation, or you can be notified of events that generate the result tree. Other events include tracing templates as they are matched, and tracing template children as they are processed. These interfaces are proprietary, so your code would be Xalan-specific. See the class TraceListener for more details. Dave "Brian Tol" group.com> cc: (bcc: David N Bertoni/CAM/Lotus) Subject: RE: Capturing relevant source document 07/02/2001 during XSLT processing 09:59 AM Please respond to general > > Brian Tol writes: > > >For an upcoming project I'll need to be capturing the relevant part of > > >a source document during XSLT processing. For example: > > >[Example doesn't explain WHY the element in question is relevant.] > > > > If you are looking for an introductory book which explains how each part > of > XSLT and XPath is interpreted by the processor in non-programmer and > programmer terms, try the following: > > http://www.amazon.com/exec/obidos/ASIN/0130404462/o/qid=994089696/sr=2- > 1/ref=aps_sr_b_1_1/104-1224542-6158306 > Thanks for the lead. I've actually done quite a bit with XSLT through Xalan and Saxon and own several XSLT books. What I'm looking for is a method of modifying the XSLT processor to record and output which nodes were used in a transformation to be used with a searching system that returns transformed documents based on relevant source documents (e.i., search the source documents and return the relevant documents based on the source documents). I thought maybe other XML tools might have similar functionality of recording such sets of nodes, so I started with the general list. Sorry if my first post was ambiguous: I'll look harder at XSLT-specific lists. Thanks, Brian --------------------------------------------------------------------- In case of troubles, e-mail: webmaster@xml.apache.org To unsubscribe, e-mail: general-unsubscribe@xml.apache.org For additional commands, e-mail: general-help@xml.apache.org --------------------------------------------------------------------- In case of troubles, e-mail: webmaster@xml.apache.org To unsubscribe, e-mail: general-unsubscribe@xml.apache.org For additional commands, e-mail: general-help@xml.apache.org