[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Article: "The horror of XML"

• To: "Seairth Jacobs" <seairth@s...>,<xml-dev@l...>
• Subject: Re: Article: "The horror of XML"
• From: "Alaric B. Snell" <alaric@a...>
• Date: Wed, 30 Oct 2002 15:36:38 +0000
• In-reply-to: <002601c28028$c029b080$a800a8c0@SeairthA31>
• References: <4c.14269086.2af14649@a...> <002601c28028$c029b080$a800a8c0@SeairthA31>

On Wednesday 30 October 2002 15:26, Seairth Jacobs wrote:
> Hmm...  I have several problems with this article:
>
> 1) Not require end tags?  I don't see how a generic parser could possibly
> process XML that was missing end tags.  The only reason that HTML browsers
> can do it (sort of) is because they also have intimate understanding of the
> semantics of HTML (e.g. can distinguish block-level presentation elements
> from in-line presentation elements, etc).  Maybe if the parser hinted at in
> this article were designed for a very specific use of XML, I might
> understand this statement.  Otherwise, I think the statement is bunk.

Given a DTD you should be able to do that - it's just recovery rules.

I mean at any point in parsing you have a stack of elements the current 
context is enclosed by. You find something invalid in the current context, so 
loop around popping stuff of the stack until it's valid.

But for the record, I wouldn't condone such activity in anything claiming to 
be an XML parser...

> Seairth Jacobs
> seairth@s...

ABS

-- 
A city is like a large, complex, rabbit
 - ARP

• References:
  • Article: "The horror of XML". :)
    • From: AndrewWatt2000@a...
  • Re: Article: "The horror of XML"
    • From: "Seairth Jacobs" <seairth@s...>

• Prev by Date: Re: Article: "The horror of XML"
• Next by Date: Re: Article: "The horror of XML"
• Previous by thread: Re: Article: "The horror of XML"
• Next by thread: Re: Article: "The horror of XML"
• Index(es):
  • Date
  • Thread