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

exclude-inline-prefixes - what does it actually do?

From: <Toman_Vojtech@emc.com>
Date: Wed, 26 Nov 2008 10:40:03 -0500
Message-ID: <6E216CCE0679B5489A61125D0EFEC7870D8FEC55@CORPUSMX10A.corp.emc.com>
To: <public-xml-processing-model-comments@w3.org>

Hi all,

I think I am just confused about what exclude-inline-prefixes actually
does. I see two possible answers.

1. For all excluded namespace URIs (represented by the prefixes in the
list), remove all bindings to these namespace URIs. In other words,
bindings for *all* prefixes that are bound to these namespace URIs will
be removed.

2. For all prefixes specified in exclude-inline-prefixes, remove their
bindings. That means that other prefixes that are bound to the same
namespace URIs may be preserved.

I have implemented option 2, but now it seems to me that 1 is the
supposed behavior.

--

Also for the '#default' prefix, what is the behavior in the following
example:

<p:declare-step xmlns:p="http://www.w3.org/ns/xproc"
exclude-inline-prefixes="#default" xmlns="http://foo.com">
  <p:output port="result"/>
  
  <p:identity xmlns="http://bar.com">
    <p:input port="source">
      <p:inline><doc/></p:inline>
    </p:input>
  </p:identity>
</p:declare-step>

1. http://foo.com will be excluded (so that the result will be <doc
xmlns="http://bar.com"/>)
2. http://bar.com will be excluded (so that the result will be <doc
xmlns="http://foo.com"/>)

I think that 1 is correct, but I am not sure.

--

And finally, is it correct that exclude-inline-prefixes="pfx #default
#all" is the same as exclude-inline-prefixes="#all"?


Regards,
Vojtech
Received on Wednesday, 26 November 2008 15:42:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 26 November 2008 15:42:02 GMT