Lists Home |
Date Index |
- From: Bryan Cooper <firstname.lastname@example.org>
- To: james anderson <James.Anderson@mecomnet.de>
- Date: Tue, 01 Dec 1998 11:05:35 -0800
One problem with PI is that there is no encapsulation, so the parser wouldn't
know when to pop the namespace stack. If PI were expanded to include
any kind of PI encapsulation, then we'd still need some clear syntax
directly to XML
to support the push of the default namespace, yes?
That is, can we declare an ENTITY that contains a PI? That would
allow encapsulation, but I don't think this is supported currently.
My reading of PI is that it is an alternative syntax around ENTITY
and directly to an application. I don't see how to include PI within an
In any case, the ENTITY would need to have a pop default namespace stack
PI at the end or you would need a second PI at the end, which defeats
the purpose of working with the parser.
Is there a way to do that currently? I don't think so. Anyone else?
I think we need to look at enhancing PI syntax into the DTD if we
don't want a <EVENT> or other new DTD syntax.
Or am I just rambling here?
At 02:22 PM 12/1/98 +0100, you wrote:
>why doesn't one just use a processing instruction for this?
>Bryan Cooper wrote:
>> In the DTD, I'd like to see this type of syntax:
>> < !EVENT push_new_context_for_namespace_example xnmls="different_ns"
>xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
>Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
>To (un)subscribe, mailto:firstname.lastname@example.org the following message;
>To subscribe to the digests, mailto:email@example.com the following message;
>List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)
F. Bryan Cooper 707 823 7324
VERITAS Software 707 321 3301 mobile
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)