W3C home > Mailing lists > Public > www-html@w3.org > September 2003

granularity of XHTML modularization

From: Peter Saint-Andre <stpeter@jabber.org>
Date: Fri, 19 Sep 2003 17:11:29 -0500
To: www-html@w3.org
Message-ID: <20030919221129.GA15252@jabber.org>

How granular is XHTML modularization? I've looked over the relevant
documents and the schema module implementations, but I must be missing
something. I would like to define a subset (not sure if that is a loaded
word on this list) of XHTML for use in instant messaging, specifically
for use over Jabber/XMPP. The results of my work so far are here:

http://www.jabber.org/jeps/jep-0071.html

Please ignore the schema section of that document -- fixing it up is why 
I'm here. :)

As you can see from that document, the Jabber context is quite foreign
to traditional XHTML applications. We use an XML streaming technology to
send XML elements (not complete documents) between logical endpoints, so
parts of the Structure Module (<head/> and <title/) do not apply. Given
that XHTML-based formatting will be used to read and generate structured
content on the fly (this is instant messaging, not document publishing),
we feel we do not need some of the elements defined in the Text Module,
some of the elements in the List Module, some core attributes, etc. Is
this possible or allowable in XHTML modularization, or do we need to use 
entire modules without modification? If it's allowed, do you recommend
that I include the relevant bits from the W3 schemas in order to build
schemas for what I'm calling XHTML-IM? If it's not allowed, how shall I
proceed? We would dearly like to use open standards rather than RTF or
somesuch nonsense if at all possible.

Many thanks,

Peter

-- 
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.php
Received on Friday, 19 September 2003 18:11:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:58 GMT