Bug 468 – investigate using XSLT key() mechanism for improving assertions.sch

NOTE: The current preferred location for bug reports is the GitHub issue tracker.

Bug 468 - investigate using XSLT key() mechanism for improving assertions.sch


Summary:	investigate using XSLT key() mechanism for improving assertions.sch

Status:	RESOLVED FIXED

Product:	Validator.nu
Classification:	Unclassified
Component:	HTML5 schema
Version:	HEAD
Hardware:	All All

Importance:	P2 enhancement
Assigned To:	Nobody

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-04-03 03:37 CEST by Michael[tm] Smith
Modified:	2010-12-17 12:38 CET (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michael[tm] Smith 2009-04-03 03:37:16 CEST

In learning more about Schematron, I discovered that schematron supports the the XSLT key mechanism:

http://www.w3.org/TR/xslt#key

The XSLT key mechanism is essentially a way to generate cached hash tables for enabling very quick lookup (tens of times faster than just using XPath) of keys and values. Unsurpisingly, the most common use case is for ID/IDREF checking.

So, anyway, switching to using the key mechanism in assertions.sch could make its performance much faster. Whether it would ever make it fast enough for consideration in real production use again for validator.nu, I don't know. But seems worth giving it a try.

Comment 1 Michael[tm] Smith 2009-06-26 08:12:12 CEST

moving this to resolution=later for now, as it's a very low priority to begin with

Comment 2 Henri Sivonen 2010-11-22 11:51:47 CET

Getting rid of LATER.

Comment 3 Michael[tm] Smith 2010-12-17 12:37:06 CET

not fixed… but not worth keeping open