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

RE: Possible problems with unsupported steps

From: <Toman_Vojtech@emc.com>
Date: Fri, 31 Oct 2008 10:02:49 -0400
Message-ID: <6E216CCE0679B5489A61125D0EFEC7870D405039@CORPUSMX10A.corp.emc.com>
To: <public-xml-processing-model-comments@w3.org>

> Hmm. I think perhaps the spec is unclear, but I believe the intent is
> that a declaration must always be present. If the processor encounters
> an element for which it doesn't have a declaration, then I think
> that's err:XS0044.

I had an interesting discussion about what XS0044 actually means some
days ago. My understanding is that it is about what content the XProc
schema permits inside the elements in the XProc namespace, in which case

   <p:pipeline xmlns:p="..." xmlns:foo="...">
     <foo:whatever/>
   </p:pipeline>

is perfectly fine, but:

   <p:pipeline xmlns:p="...">
     <whatever/>
   </p:pipeline>

is not.

If XS0044 is meant also for reporting missing step declarations, I think
the error description should be updated.

> 
> My implementation, for example, implicitly imports a set of
> declarations for its extension steps. I wonder if its allowed to do
> that, or if the author is required to explicitly import that
> library...

We do the same, we have a built-in extension library that is imported
implicitly, and you can also register your own libraries that you want
to be imported for you.  

Regards,
Vojtech
Received on Friday, 31 October 2008 14:03:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 31 October 2008 14:03:49 GMT