Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement an XML parser #3319

Closed
Manishearth opened this issue Sep 13, 2014 · 14 comments
Closed

Implement an XML parser #3319

Manishearth opened this issue Sep 13, 2014 · 14 comments

Comments

@Manishearth
Copy link
Member

@Manishearth Manishearth commented Sep 13, 2014

Stuff like parsing fetched XMLDocuments and SVG/MathML need an XML parser.

You may be able to be able to re-use some of the stuff from our HTML parser (incomplete).

@Manishearth
Copy link
Member Author

@Manishearth Manishearth commented Sep 13, 2014

@jdm Might want to add this to the list of projects for NCSU :)

@jdm
Copy link
Member

@jdm jdm commented Sep 13, 2014

This is already on the list for the students (project page). Please talk to me before commencing any work.

@Ms2ger
Copy link
Contributor

@Ms2ger Ms2ger commented Sep 13, 2014

Question is if we should implement XML1.0 4th ed (as other browsers currently do), or XML5. (cc @annevk)

@SimonSapin
Copy link
Member

@SimonSapin SimonSapin commented Sep 14, 2014

+1 to experimenting with XML5. @annevk, what’s the spec’s status?

@annevk
Copy link

@annevk annevk commented Sep 15, 2014

https://code.google.com/p/xml5/ is the latest. The whole thing is pretty straightforward, although the tokenizer is large due to doctypes. I guess you could attempt something simpler for doctypes as an initial take. Perhaps ask @hsivonen whether he still thinks this is the right way forward. And maybe @tabatkins. I believe Google had some other ideas for the future of XML. On the other hand, I guess it can't hurt to experiment.

@hsivonen
Copy link
Contributor

@hsivonen hsivonen commented Sep 15, 2014

I think it makes sense for Servo to implement XML5/XML-ER. It would be sad to add another Draconian XML parser to the world. OTOH, I think people who suggest removing XML from the Web Platform are way overoptimistic about the prospect. It's not just XHTML, but SVG and the XML part of XHR, too.

@tabatkins
Copy link

@tabatkins tabatkins commented Sep 15, 2014

SVG is very receptive to moving to non-draconian XML; we're still trying to just merge into HTML parsing. Definitely go forward on this.

@Ygg01
Copy link

@Ygg01 Ygg01 commented Oct 17, 2014

Hi, I'm interested in helping with adding XML5 to html5ever. Are there any guidelines for contributors?

@Manishearth
Copy link
Member Author

@Manishearth Manishearth commented Oct 17, 2014

@kmcallister
Copy link
Contributor

@kmcallister kmcallister commented Oct 17, 2014

@Ygg01: Not much in the way of formal guidelines yet but I'd love to have your help! You can find me anytime as kmc on Mozilla IRC.

@kmcallister
Copy link
Contributor

@kmcallister kmcallister commented Dec 27, 2014

I believe @Ygg01 has most of the XML5 tokenizer implemented, which is most of the work to support XML5 overall.

@jdm
Copy link
Member

@jdm jdm commented Jan 16, 2015

With regards to existing non-XML5 parsers, the ones for consideration are xml-rs, RustyXML, and Rust bindings to libxml2 (which are quite out of date).

@hsivonen
Copy link
Contributor

@hsivonen hsivonen commented Jan 19, 2015

Using Rust bindings for a parser implemented in a memory-unsafe language, e.g. libxml2, seems contrary to the safety goals related to using Rust in the first place.

@Ms2ger
Copy link
Contributor

@Ms2ger Ms2ger commented Mar 25, 2016

@Ms2ger Ms2ger closed this Mar 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
9 participants
You can’t perform that action at this time.