A uDoc document or map can run a query against a data source. This feature exists as a direct result of Mark Baker's “SPFE”. The queries are run at build time, not run time, so they reflect the state at the time of document processing.
For <dirref>, the @query is a wildcard applied to the directory in @src (or referenced via @key), and the results are sorted by filename. For <dbref>, the @query may be SQL or any other query language and is applied to the database specified in @src or @key. For <webref>, the @query is sent to the Web search engine specified in @src or @key. While uDoc2Go™ handles <dirref> itself, <dbref> and <webref> by their nature require additional application-specific processing.
The usage of the results of the query depends on @results; if the attribute is not present, the results are presented as items in an <sl> list. In a <map>, the results could be <docref>s or <codedocref>s. In a <doc>, they could be items in a <ul> or <ol> as well as an <sl>. Here is an example of a <dirref>:
<dirref src="C:\omsys\x2g\system\config" query="*.ini" />
Here are the results of the <dirref>, in the default simple list:
C:\omsys\x2g\system\config\x2dita_config.ini
C:\omsys\x2g\system\config\x2docbook_config.ini
C:\omsys\x2g\system\config\x2eclipse31_config.ini
C:\omsys\x2g\system\config\x2eclipse33_config.ini
C:\omsys\x2g\system\config\x2g_config.ini
C:\omsys\x2g\system\config\x2help_config.ini
C:\omsys\x2g\system\config\x2htmlhelp_config.ini
C:\omsys\x2g\system\config\x2htm_config.ini
C:\omsys\x2g\system\config\x2javahelp_config.ini
C:\omsys\x2g\system\config\x2omnihelp_config.ini
C:\omsys\x2g\system\config\x2oraclehelp_config.ini
C:\omsys\x2g\system\config\x2rtf_config.ini
C:\omsys\x2g\system\config\x2winhelp_config.ini