You probably already know this, but this is basically a case of parallel evolution. The sxml tools come ultimately from Oleg Kiselyov, and I believe he’s the one who formulated the data definition. Many people have worked with him on this, including many people on this mailing list. I think it’s fair to say that xexprs come originally from Paul Graunke and Matthias, although many many many people here have worked on infrastructure related to xexprs.
Fundamentally, I think that what you’re proposing is sensible … and probably a lot of work that’s not currently at the top of anyone’s list. :) John > On Jan 30, 2019, at 10:27 AM, Christopher Lemmer Webber > <cweb...@dustycloud.org> wrote: > > One very frustrating thing for me is the inconsistency between which > sexp xml representation is the "right" one, sxml or xexpr. Different > tools support different things, and thus don't interoperate when they > easily could have. I wish the Racket community could collectively make > a decision and "deprecate" one of them. > > IMO, it makes more sense to have sxml be the "right" one, since it has > wider user outside of just Racket, and there are some much nicer tools > available for it: > > https://docs.racket-lang.org/sxml-intro/index.html#%28part._.Tools%29 > > (That, and I find the @ property syntax a bit easier to follow, but that > barely matters.) > > Possibly opening a can of bikeshed, > - Chris > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
