Lists Home |
Date Index |
- From: Peter@ursus.demon.co.uk (Peter Murray-Rust)
- To: firstname.lastname@example.org
- Date: Sat, 15 Mar 1997 17:44:06 GMT
In message <9703150224.AA05729@sqrex.sq.com> email@example.com writes:
> > When we need to resolve a TEI pointer like (id a23) we may have to scan
> > the whole document.
> This all depends on who "we" is taken to be.
> A web indexing robot doesn't need to resolve tei pointers at all,
> except to identify the remote document -- it then indexes the whole thing.
I am guilty of imprecision ( sorry :-) I meant an internal indexing of the
document tree, not an index to locate the document.
> > In general we will wish to cache (index) IDs since
> > we don't wish to rescan for another search.
> I don't follow this. Under what circumstances is searching a document for
> an ID much more painful than using a cache? Is this for 100 MByte documents?
> (which do exist, by the way, droves. No, like elephants, in herds)
Yes - I was thinking of exactly that. Particularly if the document contains
thousands of elements (e.g. large chunks of HTML-like material).
> > When validating a document the IDs, GIs and ATTNAMEs all have to be scanned
> > since they occur in VC's.
> Not sure what a VC is (validatable context??) but yes, they all have to
> be validated.
VC = 'validity constraint' - see XML-draft 1.4 and abbreviated as this in
later places. The point is that (say) in production 52 all IDs have to be
scanned for uniqueness. Therefore at this stage it could be useful to
hash them so that they could be extracted rapidly if they form part of a
later search, rather than going through the whole doc again.
It's no big deal - but since I found myself doing it for various
searches, it seemed worth thinking about in the API.
Peter Murray-Rust, domestic net connection
Virtual School of Molecular Sciences
xml-dev: A list for W3C XML Developers
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To unsubscribe, send to firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (email@example.com)