W3C home > Mailing lists > Public > public-xhtml2@w3.org > August 2008

Re: XML Events 2 Scripting Module in XHTML 2

From: Shane McCarron <shane@aptest.com>
Date: Thu, 07 Aug 2008 09:56:13 -0500
Message-ID: <489B0D0D.3080601@aptest.com>
To: Roland Merrick <roland_merrick@uk.ibm.com>
CC: XHTML WG <public-xhtml2@w3.org>, public-xhtml2-request@w3.org



Roland Merrick wrote:
>
> Greetings Shane, I think that we are moving in the direction of a 
> consensus on having both handler and script elements and that the 
> script element should be backwards-compatible. This implies that the 
> script element should have an @type attribute. 
That makes sense to me.
>
>
> If the script element has @type, I would expect handler to also have 
> @type. I also wonder why we cannot use @type rather than @srctype in 
> XHTML 2.
Well - because it is inconsistent with @hreftype... we allow two methods 
of connecting to external resources, and those methods need attributes 
that support them.  @hreflang, @srclang... etc.  I don't really mind if 
we change @srctype back to @type in XHTML 2 - but you would need to get 
buy in from the whole group.
>
> Regards, Roland
>
>
>
> From: 	Shane McCarron <shane@aptest.com>
> To: 	XHTML WG <public-xhtml2@w3.org>
> Date: 	21/07/2008 02:49
> Subject: 	XML Events 2 Scripting Module in XHTML 2
>
>
> ------------------------------------------------------------------------
>
>
>
>
> While editing XHTML 2 tonight, attempting to make all of the external
> references hang together, I noticed something that I don't know the
> solution for:
>
> If we are integrating XML Scripting into the XHTML namespace (as we have
> planned to do) then the script element will bring with it the attributes
> "encoding", "implements", "src", and "type".  Naturally, we also want
> the "script" element to take the Common attributes, which perforce
> include the Metainformation attributes (RDFa), the embedding attributes
> from XHTML 2, etc...  Now @src and @encoding from the Embedding module
> are probably consistent with what we meant for the script element.   So
> that's fine.  I think.  Correct me if I am wrong.
>
> @implements is a new thing, and there is no conflict.
>
> @type...   XML Events 2 goes to great pains to explain what @type
> means.... and I think it is exactly what is meant by @srctype in XHTML
> 2.  So... I am not sure what to do here.  We can change @type to
> @srctype in XML Events 2.  We can bring in @type on the script element,
> also bring in @src, and just have the script element reference the
> Common attributes collection (use a subset that makes sense, but does
> not include the embedding attributes).... or maybe something else.
>
> Help?
>
> -- 
> 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/
>
>
>
>
>
>

-- 
Shane P. McCarron                          Phone: +1 763 786-8160 x120
Managing Director                            Fax: +1 763 786-8180
ApTest Minnesota                            Inet: shane@aptest.com
Received on Thursday, 7 August 2008 14:58:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 23 February 2010 18:12:49 GMT