- From: Norman Walsh <ndw@nwalsh.com>
- Date: Fri, 31 Oct 2008 10:17:31 -0400
- To: public-xml-processing-model-comments@w3.org
- Message-ID: <m263n8hmro.fsf@nwalsh.com>
Toman_Vojtech@emc.com writes:
>> 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.
I'm happy to try to clarify the situation, but I think XS0044 covers
both cases. If there's no declaration for foo:whatever, then it's an element
child not allowed by this specification.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | Time wounds all heels.
http://nwalsh.com/ |
Received on Friday, 31 October 2008 14:18:14 UTC