DFDL "the standard" says nothing about how to do this today. The way an implementation applies value bindings to external variables is not defined by the standard. Basically, nothing about APIs for driving a DFDL processor is mentioned in the standard.

What you suggest is an interesting mechanism especially for when there are many such variables and calling an API function to set them each is burdensome.

...mike

On Wed, Jul 17, 2013 at 2:59 PM, Garriss Jr., James P. <jgarriss@mitre.org> wrote:

Suppose you have an XSLT stylesheet with a bunch of global variables.  Suppose that the value of those variables must be determined outside of the XSLT.  How do you get the values into it?  You might use parameters, and pass in the values when you call the transform() function in your code.  But you could also use the document() function from within XSLT, read in an XML “policy” file that has all the values, then store the values in the variables.  You might call this approach policy driven XSLT.

 

Can we do policy driven DFDL?  Yes, I know that we have parameters, but is there a way to read in a “policy” file (whether XML or not), read the values, then set the variables to those values?

 

TIA


--
  dfdl-wg mailing list
  dfdl-wg@ogf.org
  https://www.ogf.org/mailman/listinfo/dfdl-wg



--
Mike Beckerle | OGF DFDL Workgroup Co-Chair | Tresys Technology | www.tresys.com