- From: Norman Walsh <Norman.Walsh@Sun.COM>
- Date: Fri, 13 Oct 2006 15:10:03 -0400
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <871wpcm3qs.fsf@nwalsh.com>
/ Alessandro Vernet <avernet@orbeon.com> was heard to say: | On 10/12/06, Norman Walsh <Norman.Walsh@sun.com> wrote: |> On balance, I'm strongly in favor of the former. | | One downside of mandating that URI must be cached is that it will make | the execution of some pipelines inefficient or even impossible. For It was clear on the call yesterday that my opinion on this issue is distinctly in the minority. Richard pointed out that any pipeline that needs to make sure that the result of reading a URI doesn't change can do so by using a load component and referring to the output of that component. (How that can be made to work with other components that take the URI as a parameter, or have the URI embedded within their inputs, and not as an input is unclear to me.) In any event, I concede that we will not be imposing any such requirement on implementations. Be seeing you, norm -- Norman Walsh XML Standards Architect Sun Microsystems, Inc.
Received on Friday, 13 October 2006 19:10:27 UTC