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

Importing/executing atomic steps directly

From: <Toman_Vojtech@emc.com>
Date: Mon, 19 May 2008 06:15:19 -0400
Message-ID: <6E216CCE0679B5489A61125D0EFEC7870B13C968@CORPUSMX10A.corp.emc.com>
To: <public-xml-processing-model-wg@w3.org>

Hi all,

Section 5.10 (p:import) says:

"An p:import loads a pipeline or pipeline library, making it available
in the pipeline or library which contains the p:import."


"It is a static error (err:XS0052) if the URI of a p:import cannot be
retrieved or if, once retrieved, it does not point to a p:library,
p:declare-step, or p:pipeline."

So, if p:declare-step can be imported, what about atomic steps? Should
p:import fail if the imported p:declare-step is an atomic step?

Consider this example:

<?xml version="1.0" encoding="UTF-8"?>
<p:declare-step type="x:my-step" xmlns:p="http://www.w3.org/ns/xproc"
  <p:input port="source"/>
  <p:output port="result"/>

<?xml version="1.0" encoding="UTF-8"?>
<p:pipeline xmlns:p="http://www.w3.org/ns/xproc"
  <p:import href="step.xpl"/>

Is this allowed?

I think the same applies to executing p:declare-step directly - should
it be possible to execute atomic steps?

Received on Monday, 19 May 2008 10:16:10 UTC

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