- From: Roland Merrick <roland_merrick@uk.ibm.com>
- Date: Wed, 21 Jan 2009 13:53:24 +0000
- To: Shane McCarron <shane@aptest.com>
- Cc: XHTML WG <public-xhtml2@w3.org>, public-xhtml2-request@w3.org
- Message-ID: <OF61168785.54BA4409-ON80257545.004B1C26-80257545.004C5076@uk.ibm.com>
Greetings Shane, fair question. During the October face to face we
discussed this [1] and made a resolution:
RESOLUTION: keep everything from XHTML 1.0 definition of script
So the question in my mind is why change from @charset to @encoding in
XHTML2?
" SM: changed for XHTML2 in response to comment from i18n "
but what was their rationale? People have now become familiar with
@charset and even our description of @encoding feels it necessary to
mention how it relates to accept-chaset in http. Perhaps someone can
articulate the benefit of changing and how it outweighs the disadvantages
of change.
[1] http://www.w3.org/2008/10/24-xhtml-minutes.html#item03
Regards, Roland
From:
Shane McCarron <shane@aptest.com>
To:
XHTML WG <public-xhtml2@w3.org>
Date:
20/01/2009 19:55
Subject:
Issue with @charset vs. @encoding in XML Scripting Module
XML Events 2 defines the XML Scripting Module [1] - this module defines
the script element and its required attributes. While working with this
module and its Schema and RelaxNG implementations, Markus and I ran into
a quandary that I do not know how to address.
XML Events 2 has two different audiences. There is the "today" audience
that might need the XML Scripting Module, and the "tomorrow" audience
that will use all the modules in languages like XHTML 2 and XForms 1.2.
Right now, the script element uses the @charset attribute as defined in
XHTML Modularization 1.1 [2]. And that's fine. It makes sense in a
pre-XHTML 2 world. However, if we are going to include XML Scripting in
XHTML 2, we really don't want @charset. @charset has been superseded by
@encoding.
Anyway - in implementing the script element for XHTML 2 I decided that
we really meant @encoding. This is in conflict with the draft XML
Events 2 spec though.
Question: Do we change XML Events 2 to use @encoding as defined in XHTML
2, change XHTML 2 to use @charset for this one element, or develop a new
version of the XML Scripting module in XHTML 2 that overrides the one in
XML Events 2?
[1] http://www.w3.org/MarkUp/2008/ED-xml-events-20081223/#s_script_module
[2]
http://www.w3.org/MarkUp/2009/ED-xhtml2-20090109/mod-scripting.html#s_scriptingmodule
--
Shane P. McCarron Phone: +1 763 786-8160 x120
Managing Director Fax: +1 763 786-8180
ApTest Minnesota Inet: shane@aptest.com
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Received on Wednesday, 21 January 2009 13:54:17 UTC