W3C home > Mailing lists > Public > public-xml-processing-model-comments@w3.org > July 2009

Re: Handling Circular and Re-entrant Library Imports

From: Henry S. Thompson <ht@inf.ed.ac.uk>
Date: Fri, 31 Jul 2009 16:07:18 +0100
To: <Toman_Vojtech@emc.com>
Cc: <public-xml-processing-model-comments@w3.org>
Message-ID: <f5bvdl8evrt.fsf@hildegard.inf.ed.ac.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[anon] writes:

>> I _think_ we said that import processing could be lazy, didn't we?
>> That is, only top-level imports get followed automatically -- nested
>> ones only get called if their embedding pipeline gets used.
>
> Hmm, really? I hope you mean lazy in the sense that all import-related
> errors can still be detected during the static pipeline processing phase
> (all p:import related errors are static).

No, I meant that the following is OK:

<p:pipeline>
 <p:import href="foo"/>
 <p:declare-step type="step2">...</p:declare-step>
 <step1>
  ....
 </step1>
 <step2>
  ....
 </step2>
</p:pipeline>

foo:
<p:library>
 <p:declare-step type="step0">
  <p:declare-step type="step2">...</p:declare-step>
  . . .
 </p:declare-step>
 <p:declare-step type="step1">
  . . .
 </p:declare-step>
</p:library>

But maybe I made that up. . .

>> Furthermore, and arguably more important, nested imports are scoped to
>> the pipeline which embeds them:
>> 
>>   "An import statement loads the specified IRI and makes any pipelines
>>    declared within it available to the current pipeline."
>
> Yes, I agree with that. I just wanted to say that the algorithm should
> also work in the case when it starts from within a nested pipeline.

Agreed.  And that's why the algorithm in Appendix G needs to be rewritten.

ht
- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
                         Half-time member of W3C Team
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFKcwimkjnJixAXWBoRAmjkAJ9b4Lfaw5J6lPTiD7Il+Iw/RudV4QCfYHxe
vpC95SI/1aROaU7VqL+ccPk=
=AeBI
-----END PGP SIGNATURE-----
Received on Friday, 31 July 2009 15:07:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 31 July 2009 15:07:56 GMT