[standards-jig] UPDATED: JEP-0071 (XHTML-IM)

Peter Saint-Andre stpeter at jabber.org
Wed Sep 24 23:03:17 UTC 2003

OK, I've looked into this and it's not as straightforward as you might
hope. Modularization of XHTML in XML Schema [1] specifies how to modify
and extend XHTML in a way that conforms to Modularization of XHTML [2]
using W3 XML Schema. XHTML *requires* certain modules and these must not
be changed without using schema redefinition or substitution groups (if
you understand these, you're a better man than I). Among the required 
modules are the following:

1. structure (includes <head/> and <title/>, which are out of scope for

2. block phrasal (fine except for <address/>)

3. block structural (<div/> and <p/>, that's okay)

4. inline phrasal (including <abbr/>, <acronym/>, <dfn/>, <kdb/>,
<samp/>, and <var/>, none of which we want)

5. inline structural (<br/> and <span/>, that's okay)

6. hypertext (i.e., <a/> and all its attributes, of which we only want

7. lists (includes <dd>, <dl>, and <dt>, which we don't want)

8. common attributes (none of which we want to support) 

I've posted a message to the www-html mailing list about this but have 
as yet received no reply:


I will continue to investigate this matter and will report to the list 
regarding any further findings.


[1] http://www.w3.org/TR/xhtml-m12n-schema/
[2] http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/

On Wed, Sep 17, 2003 at 09:21:13AM +0200, Jacek Konieczny wrote:
> On Tue, Sep 16, 2003 at 02:43:52PM -0500, Peter Saint-Andre wrote:
> > Version 0.8 of JEP-0071 (XHTML-IM) is now available. The changelog is as
> > follows:
> > 
> >    Changed MUST to SHOULD for support of the Style Attribute Module;
> >    clarified relationship of XHTML-IM schema to XHTML schema; slight
> >    text cleanup. (psa) 
> > 
> > http://www.jabber.org/jeps/jep-0071.html
> I still don't like it. This JEP has XHTML in it which suggest it is
> XHTML based - and this is good. I understand it is a subset of XHTML,
> but the schema should still be based on XHTML.
> Now XHTML-IM includes eg. H1 and SPAN elements - just like XHTML - but
> they cannot be used like in XHTML - like this: 
>         <h1><span style='font: bold'>Valid</span>XHTML header.</h1>
> Probably there are much more such differencies, as it seems the JEP
> author "invented" the schema instead of perparing XHTML-based schema
> for XHTML subset. It is just as we say, that in XHTML-IM link is done
> with <b/> not <a/>
> I am _not_ saying we should use XHTML schema to validate XHTML-IM,
> but those schemas should be as compatible as it is possible. IMHO the
> best way to make XHTML-IM schema is to take XHTML schema and remove all
> references to unsupported elements and attributes.
> Greets,
>         Jacek

More information about the Standards mailing list