Have you made any progress on this? I'm also need xml parser that wold play 
nicely with pipes and don't want to reinvent the wheel.  

On Wednesday, November 6, 2013 10:47:30 AM UTC+2, Jack Henahan wrote:
>
> I had had the same thought, actually. A more opinionated port of 
> `xml-conduit` would be just the ticket. 
>
> On Nov 6, 2013, at 3:43 AM, Dag Odenhall <[email protected]<javascript:>> 
> wrote: 
>
> > Maybe porting xml-conduit wouldn’t be much work. I particularly like 
> that it uses xml-types, although I’m not sure what I think about the ways 
> it deviates from it with the entity resolution. 
> > 
> > 
> > 
> > On Wed, Nov 6, 2013 at 7:58 AM, Jack Henahan <[email protected]<javascript:>> 
> wrote: 
> > Hi all, 
> > 
> > I'm starting my first sort of nontrivial public project, and I'd like to 
> use `pipes` (and probably `lens`, honestly) 
> > in the process. I've been subbed to the mailing list for a while, so 
> I've seen lots of good discussion about 
> > `pipes-parse` and `pipes-attoparsec` and so on. I've noticed that 
> there's a hole in the ecosystem w.r.t. XML, 
> > and I wanted to know if that's because that effort is more or less 
> subsumed by just using `pipes-attoparsec` 
> > where we need to deal with it, or just that people are otherwise 
> preoccupied. 
> > 
> > My project is essentially just bindings for the API of a game I play, 
> but it's all XML that I'll be dealing with 
> > so I'll probably end up with most of a hypothetical `pipes-xml` library 
> in the process. If that's already in the 
> > works, I'm happy to contribute to existing code, and if it's not I'll be 
> even happier to publish my work for 
> > the benefit of the ecosystem. 
> > 
> > If there's already prior art for using `pipes` in this way, by the way, 
> I'd be very happy to see some examples 
> > of how regular users handle it, or even take suggestions for must-have 
> features of a `pipes-xml` library. I 
> > imagine I would start with the data types from `xml` and build from 
> there. 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "Haskell Pipes" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to [email protected] <javascript:>. 
> > To post to this group, send email to 
> > [email protected]<javascript:>. 
>
> > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "Haskell Pipes" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to [email protected] <javascript:>. 
> > To post to this group, send email to 
> > [email protected]<javascript:>. 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Haskell Pipes" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].

Reply via email to