Cart
[Home] [By Thread] [By Date] [Recent Entries]
>
> why limit this to locating a validation schema? why not follow it to
> the logical conclusion: a general processing model?
Actually, it is so already. The readme file, http://ftp.davidashen.net/PreTI/CImpl/readme.txt,
says
: ARX can also be used to link documents to any type of information or
: processing.
There is a command-line flag, -n, which stops treating the chosen string as a
possibly relative path and outputs it as it is.
> if one generalizes schema-match to
But this should not be embedded into ARX, since, in fact, it restricts and not
generalizes. ARX can output a unique URI based on validation assertions with
respect to a document's URI (filename) and contents.
It is the business of another application to perform processing according to
the result of ARX. For example, to automatically choose a Relax NG schema for
validation, one invokes
rnv `arx $1 schemas/arx.conf` $1
or
xmllint --relaxng --noout `arx $1 schemas/arx.conf` $1
or
jing -c `arx $1 schemas/arx.conf` $1
That is, printing a unique string for each case is the only thing that has to
(and should) be done inside ARX.
David Tolpin
http://davidashen.net/
|
