"All of that is true, particularly for XML users who come from the SGML
world, but since we're talking about practicalities, there are a large class
of XML documents in the real non-SGML world which have the following
characteristics:"
And the optional 'ignore external subset' flag that's already
From: Bil Mason [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 27, 2001 7:19 AM
To: [EMAIL PROTECTED]
Subject: RE: PLEASE HELP: SAX parser errors on validation when
ValScheme=V al_Never?
DTDs can indeed "cause a lot of other stuff to happen" but
non-validating parsers can only be relied
> "Peter A. Volchek" <[EMAIL PROTECTED]> writes:
>
> > But, why not provide the (let name it advanced api ) additional feature,
> > which allows to suppress it? (especially, when so many people require
it).
> > At least, it may be put in the protected area of a parser, so that it
might
> > be us
"Peter A. Volchek" <[EMAIL PROTECTED]> writes:
> But, why not provide the (let name it advanced api ) additional feature,
> which allows to suppress it? (especially, when so many people require it).
> At least, it may be put in the protected area of a parser, so that it might
> be used, only by t
Dean Roddey wrote:
>
> As a practical matter, DTDs are not just about validation. They cause a lot
> other stuff to happen. In most cases, people who are not validating still
> very much want it to be processed and want to know if anything goes wrong.
> So don't get too tied up on DTDs being just
> DTDs can indeed "cause a lot of other stuff to happen" but
> non-validating parsers can only be relied upon to make that
> stuff happen using the internal subset. Defaulting attributes,
> expanding entities, etc. are all vital things but if you are
> using a non-validating parser, your definiti
ril 27, 2001 7:35 AM
Subject: Re: PLEASE HELP: SAX parser errors on validation when ValScheme=V
al_Never?
> It seems that this discussion is one best addressed by the XML spec
> community and not here. The real question is should a non-validating
> parse raise a fatal error if
formed.
>
> -Original Message-
> From: Dean Roddey [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 26, 2001 10:17 PM
> To: [EMAIL PROTECTED]
> Subject: Re: PLEASE HELP: SAX parser errors on validation when
> ValScheme=V al_Never?
>
>
> As a practical matter
tions HAVE to be in
the internal subset or your document just might not end up
being well-formed.
-Original Message-
From: Dean Roddey [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 26, 2001 10:17 PM
To: [EMAIL PROTECTED]
Subject: Re: PLEASE HELP: SAX parser errors on validation when
V
Original Message-
From: Peter A. Volchek [mailto:[EMAIL PROTECTED]]
Sent: 27 April 2001 11:24
To: [EMAIL PROTECTED]
Subject: Re: PLEASE HELP: SAX parser errors on validation when
ValScheme=V al_Never?
If I know exactly, that referred DTD does not contain niether any entities
not default attribu
then and there and tell the
> parser whether to go on.
- Original Message -
From: "Dean Roddey" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 27, 2001 1:38 AM
Subject: RE: PLEASE HELP: SAX parser errors on validation when ValScheme=V
al_Never?
- Original Message -
From: "Bil Mason" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 26, 2001 11:39 AM
Subject: RE: PLEASE HELP: SAX parser errors on validation when ValScheme=V
al_Never?
> I think I see what you are saying but I thought
> t
ng
out that users who do this should be using
validating parsers.
Ok, maybe I'm getting too general here, I'll
stop. 8-)
-Original Message-
From: Dean Roddey [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 26, 2001 2:08 PM
To: '[EMAIL PROTECTED]'
Subject: RE: PLEAS
the
parser whether to go on.
--
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
-Original Message-
From: Bil Mason [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 26, 2001 7:22 AM
To: [EMAIL PROTECTED]
Subject: RE: PLEASE HELP: SAX parser errors on valid
ation.
-Original Message-
From: Peter A. Volchek [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 26, 2001 10:10 AM
To: [EMAIL PROTECTED]
Subject: Re: PLEASE HELP: SAX parser errors on validation when
ValScheme=Val_Never?
Absolutely agree
>but it MUST NOT be an error if the file is
&g
"A non-validating processor appears to be allowed to
read information from that file if it is there but
it is NOT an exception if it isn't since it
is ABSOLUTELY NOT allowed to use that information
to modify the internal subset in ANY way."
But that's not relevant to the point. Of course the exte
x27;[EMAIL PROTECTED]'
Subject: RE: PLEASE HELP: SAX parser errors on validation when
ValScheme=V al_Never?
> A non-validating processor is apparently
> allowed to attempt to read foo.dtd, but
> it MUST NOT be an error if the file is
> not found since a non-validating proce
> A non-validating processor is apparently
> allowed to attempt to read foo.dtd, but
> it MUST NOT be an error if the file is
> not found since a non-validating processor
> is NOT required to read the external sub-set.
Well, that logic isn't exactly ummm...logical :-) The fact that its not
*requ
>I'm asking why not to implement it by xerces team
Ignoring the DTD isn't a mode of operation defined as legal/meaningful by
the XML Recommendation.
It is a common request, but departing from standards is not something to
take lightly.
-
mes it is desirable to know that dtd is
missing.
- Original Message -
From:
Bil
Mason
To: [EMAIL PROTECTED]
Sent: Thursday, April 26, 2001 5:00
PM
Subject: RE: PLEASE HELP: SAX parser
errors on validation when ValScheme=Val_Never?
Actually, I don't th
quired
to read the external sub-set.
-Original Message-
From: Erik Rydgren [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 26, 2001 7:07 AM
To: [EMAIL PROTECTED]
Subject: RE: PLEASE HELP: SAX parser errors on validation when
ValScheme=Val_Never?
Yes that is the correct behaviour.
The DTD can conta
sking one thing)
this should be implemented.
(of course if this is reasonable)
- Original Message -
From:
Prior, Chris
To: '[EMAIL PROTECTED]'
; [EMAIL PROTECTED]
Sent: Thursday, April 26, 2001 4:17
PM
Subject: RE: PLEASE HELP: SAX parser
errors on
CTED]; [EMAIL PROTECTED]
Subject: Re: PLEASE HELP: SAX parser errors on validation when
ValScheme=Val_Never?
Asking again. Are you planning to provide a way not to throw an exception if
dtd does not exists ?
My application strictly requires this. In the previous version (xml4c 2.3.1)
I might
:08To: [EMAIL PROTECTED];
[EMAIL PROTECTED]Subject: Re: PLEASE HELP: SAX parser
errors on validation when ValScheme=Val_Never?
Asking again. Are you planning to provide a way not to throw
an exception if dtd does not exists ?
My application strictly requires this. In the previous
ve
-
From:
Erik Rydgren
To: [EMAIL PROTECTED]
Sent: Thursday, April 26, 2001 2:06
PM
Subject: RE: PLEASE HELP: SAX parser
errors on validation when ValScheme=Val_Never?
Yes that is the correct behaviour.The DTD can contain
definitions that are needed even when not
Yes that is the correct behaviour.
The DTD can contain definitions that are needed even when not validating.
/ Erik Rydgren
-Original Message-
From: Prior, Chris [mailto:[EMAIL PROTECTED]]
Sent: den 26 april 2001 13:00
To: '[EMAIL PROTECTED]'
Subject: PLEASE HELP: SAX parser
Hi all,
I am using the SAX parser and setting validation to Val_Never, yet when I
parse an xml doc that specifies a dtd the parser fails if it cannot find the
dtd!!!
Why is this the case when I am not interested in validating? Surely looking
for the dtd when no validation is required is not corr
Thanks,
I will kick myself in the ass now. When creating the MemInputSource I use
the correct string but the length of the old string.
Sorry
Glenn
[EMAIL PROTECTED] wrote:
> 5 < 7
>
> Certainly ought to work.
>
> I hate to ask the dumb question, but have you tried printing ou
5 < 7
Certainly ought to work.
I hate to ask the dumb question, but have you tried printing out the
contents of that buffer, to make absolutely sure you're parsing what you
think you're parsing? (Last time I had one of these "It can't possibly
fail" issues, it turned out that I hadn't successfu
Hi All,
I am using the xerces SAX parser. If I pass the parser the following
string in a MemInputBuffer:
5 < 7
I get an error, which I expect. The error is: expected on element name
when I pass the parser this string: 5 <
7
I strill get an error, which I don't expect: expected end of tag 'e
30 matches
Mail list logo
