- From: Alex Russell <slightlyoff@google.com>
- Date: Sun, 17 Feb 2013 10:50:57 +0000
- To: Mukul Gandhi <gandhi.mukul@gmail.com>
- Cc: Henri Sivonen <hsivonen@iki.fi>, Jirka Kosek <jirka@kosek.cz>, public-html WG <public-html@w3.org>, Paul Cotton <Paul.Cotton@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, "www-tag@w3.org List" <www-tag@w3.org>, Sam Ruby <rubys@intertwingly.net>, "Michael[tm] Smith" <mike@w3.org>, Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Message-ID: <CANr5HFWAPyvwZYEbNA+LTgHxWAnJLxBNg2sLJiCKHyw1odWSFw@mail.gmail.com>
On Feb 17, 2013 5:54 AM, "Mukul Gandhi" <gandhi.mukul@gmail.com> wrote: > > I had a use case very recently to process an HTML document, which was non well-formed in XHTML/XML sense so as to be processable with an XML too chain. It seems, that polyglot markup would have helped me write my application. How would it have helped? Did you control the source of the document? Could you in some way guarantee well-formedness from the publisher? Polyglot only helps those who know or control the parseability of the documents they process. > Further to this I feel, assuming an HTML markup (not polyglot markup) is sent to a browser agent for rendering, if the browser provides a functionality to convert this received markup to polyglot and allowing the user to save the converted polyglot markup, then the user can process the received HTML information with an XML tool chain. > > I also feel, that all different document formats (which have originated from HTML) which are currently supported by web (these formats include HTML, XHTML and XML for e.g), must have an integration glue so as to be able to design a union of all such web data formats. It seems to me, that polyglot markup is one such integration glue. > > > On Thu, Jan 31, 2013 at 3:48 AM, Jirka Kosek <jirka@kosek.cz> wrote: >> >> On 28.1.2013 5:43, Leif Halvard Silli wrote: >> >> > Mike: In trying to understand what Henri said about authors, I see that >> > he was afraid that A List Apart would write about polyglot. And clearly >> > many authors read ALA. But I find only 2 references to Appendix C at >> > ALA.[2] Henri seems to forget that it was XHTML 1.0 that spread the >> > message that XHTML syntax is OK in text/html. Hey, W3.org uses XHTML >> > syntax all over - to this day. >> >> Just to add 0.02 to this polyglot discussion. Czech Web developers >> magazine published my article about polyglot 1.5 year ago: >> >> http://www.zdrojak.cz/clanky/polyglot-aneb-webovym-koderem-pod-oboji/ >> >> The conclusion is simple -- except very narrow use-cases usage of >> polyglot doesn't make sense. Follow-up discussion hasn't indicated >> disagreement with this conclusion. >> >> Personally I don't have preference whether polyglot should or shouldn't >> be REC. >> >> Leif you seem to put a lot of energy to promoting polyglot. I have seen >> something similar 10 years ago -- a lot of energy was put into promoting >> XHTML -- unfortunately this created many false expectations on the web >> developers side. We shouldn't repeat this mistake again with polyglot. >> >> Jirka >> >> -- >> ------------------------------------------------------------------ >> Jirka Kosek e-mail: jirka@kosek.cz http://xmlguru.cz >> ------------------------------------------------------------------ >> Professional XML consulting and training services >> DocBook customization, custom XSLT/XSL-FO document processing >> ------------------------------------------------------------------ >> OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. >> ------------------------------------------------------------------ >> Bringing you XML Prague conference http://xmlprague.cz >> ------------------------------------------------------------------ > > > > > -- > Regards, > Mukul Gandhi
Received on Sunday, 17 February 2013 10:51:26 UTC