OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: Frontline report from the Desperate Fgrep Hacker

[ Lists Home | Date Index | Thread Index ]
  • From: Stefan Haustein <haustein@kimo.cs.uni-dortmund.de>
  • To: Sean McGrath <digitome@iol.ie>, xml-dev@xml.org
  • Date: Fri, 11 Feb 2000 20:38:19 +0100

Sean McGrath wrote:
> [John Cowan]
> >I happened to know that the element always appeared on a single
> >line of the file: the start tag, the character data, the end tag.

> SML-DEV. Bottom line: simple grepping of XML 1.0
> can get you burnt because of all the things that
> can occur in cosher XML 1.0 documents that
> a straight lexical analysis will misconstrue unless
> prefixed by an XML parser.

Made me thinking what an "xmlgrep" would need to do, and which 
additional parameters it would need: Even for SML, grep seems
dangerous, consider

<tag>I want the complete line</tag> 


want the

"xmlgrep" could search in a given set of elements for a 
regular expression. But how would the list of elements
be specified (xpath? 2nd regexp?)? Which child elements are returned? 
All? None? configurable? Or could the problem be solved by 
preformatting XML/SML to a form where all elements get an extra line,
whereas line breaks inside text content are replaced by a space?

Best regards


Stefan Haustein
University of Dortmund
Computer Science VIII


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS