W3C home > Mailing lists > Public > public-multilingualweb-lt-comments@w3.org > July 2013

Re: Comments on section 6.2 of ITS 2.0

From: Sean Mooney <sean.mooney@ul.ie>
Date: Sun, 07 Jul 2013 01:53:56 +0100
Message-ID: <51D8BC24.9060604@ul.ie>
To: public-multilingualweb-lt-comments@w3.org
i am sorry to interject so late into this discussion but
from following the mail thread i feel i must raise one point for 

the current draft of the html 5 spec state the following in sect1.6 

"The second concrete syntax is the XHTML syntax, which is an application 
of XML. When a document is transmitted with an XML MIME type 
such as |application/xhtml+xml 
then it is treated as an XML document by Web browsers, to be parsed by 
an XML processor. Authors are reminded that the processing for XML and 
HTML differs; in particular, even minor syntax errors will prevent a 
document labeled as XML from being rendered fully, whereas they would be 
ignored in the HTML syntax. This specification defines version 5.1 of 
the XHTML syntax, known as "XHTML5.1"."

the html spec explicitly reminds authors that processing for  XML and 
HTML differ,
this is also true for ITS.
to be compatible with the xml processing requirement above should the 
ITS2.0 spec not require all XHTML document to be processed as xml.

as such if it is XHTML (which in turn is an xml dialect) then should not 
its:* be used only and if it is HTML then only its-* attibutes should be 


On 05/07/2013 17:04, Jirka Kosek wrote:
> On 5.7.2013 17:52, Daniel Glazman wrote:
>> Wait... That means that its:rules can happen anywhere inside XHTML
>> and not only inside a script element?!? Wow, to say the least.
> its:rules can be anywhere inside XML document.
> For XHTML it depends:
> You can either decide that your XHTML is really XML and then yes
> its:rules can be anywhere, you will use its:* attributes, you will not
> put its:rules inside script, ... This makes sense if you want to process
> XHTML with real XML toolchain.
> Or you can decide that you want your XHTML to be "web-friendly" and then
> you will try to make it as close to use HTML syntax as possible -- you
> will use its-* attributes, you will put its:rules inside <script>
> element, etc. This approach makes sense if you want to send your content
> into browser.
> Given the BlueGriffon is editor for Web content not generic XML editor I
> suppose it's enough if it will support later, HTML-like approach to ITS.
> 				Jirka
Received on Sunday, 7 July 2013 00:54:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:32:28 UTC