Article:		Non-Extractive Parsing for XML
Subject:		BEWARE: DANGEROUS ERRORS IN ARTICLE!
Date:		2004-06-01 14:07:00
From:		Michael Maron
Response to: BEWARE: DANGEROUS ERRORS IN ARTICLE!
Normally, a token is defined something like a sequence of symbols from the certain symbol range, for example, a-zA-Z0-9. All other symbols are considered as token separators. This is exactly how regexps work. So, I really don't know what is the point of using partial rather than complete comparisons. What is also highly strange is that the article considers an HTTP header, not an XML document as an example: Consider the following snippet of an HTTP header as an example. Accept: */* Accept-Language: en-us Connection: Keep-Alive Host: localhost Referer: http://localhost/links.asp <question remark="shrugging shoulders"> What all this has to do with XML? </question>

Previous Message

Up

Next Message

• BEWARE: DANGEROUS ERRORS IN ARTICLE!
  2004-06-01 14:12:16 jimmy_z [Reply]
  
  The reason I used the example of HTTP is because the representation of token is one layer below XML parsing; in other words, it applies to many types of text processing.

  
  Thanks,
  Jimmy
  
  

  • BEWARE: DANGEROUS ERRORS IN ARTICLE!
    2004-06-01 16:45:12 Michael Maron [Reply]
    
    Well, it would sound reasonable to talk about XML processing using XML documents as examples. As for HTTP headers, working with them is a completely different task from XML document processing.

    
    Best,
    Michael