W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > April 2007

Option or parameter?

From: Alessandro Vernet <avernet@orbeon.com>
Date: Tue, 24 Apr 2007 17:59:18 -0700
Message-ID: <4828ceec0704241759l2a8e5610o7c31b5c305b09370@mail.gmail.com>
To: public-xml-processing-model-wg <public-xml-processing-model-wg@w3.org>

When should a component designer use an option vs. a parameter?

The spec reads (2.3): "The distinction between options and parameters
is simply that options are used by the XProc processor to configure
the step; the step never sees them. Parameters are passed to the step
for its use, the XProc processor does not use them."

What does "passed to the step" mean here? If the value of an option
wasn't passed to the corresponding step, it wouldn't be of much use,
would it?

Orbeon Forms - Web 2.0 Forms for the Enterprise
Received on Wednesday, 25 April 2007 00:59:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:42 UTC